If the install's are not too old just update you git tree with "git pull". Then do this from your root tree, you can no longer build from the source4 directory:
make clean ./configure.developer --disable-s3build make Then make a backup copy of /usr/local/samba remove the following directiries rm -Rf /usr/local/samba/bin rm -Rf /usr/local/samba/sbin rm -Rf /usr/local/samba/include rm -Rf /usr/local/samba/modules rm -Rf /usr/local/samba/lib rm -Rf /usr/local/samba/share make install start samba If your installation is too old then you will need to use the upgradeprovision script, but I have never got it work. Jonn On 05/09/2011 10:52 AM, de...@podoll.com wrote: > I have a install of samba4 that I have been using on my home network > for testing with one PDC and BDC on the local network and a 3rd BDC > located on another network with IPSEC tunnel between the two > networks. The problem I have is all 3 servers are running different > versions on the samba4 code I would like to get all the system on the > same code level. Do any of you know an easy way to do this so I do > not loose all the account and policy information in the PDC when I > update it? either that or is there a backup method anyone would > recommend before trying it preform any updates. > > > System info below > > OS Centos 5.5 on all systems with bind installed to support dynamic > updates > Hardware local PDC and BDC run off of XENSERVER virtual machines from > two different xenserver platforms > Hardware offsite HP server > Network connection between servers IPV6 with IPSEC tunnel running over > internet using IPV6 > > > Thank you for any help -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
