Run "testparm -v" - you will probably want to copy over the /var/samba/locks directory
lock directory = /var/samba/locks state directory = /var/samba/locks cache directory = /var/samba/locks pid directory = /var/samba/locks You also want to make sure your netlogon and profile directories are replicated. I ran into some issues migrating from 3.0.x to 3.4.x. I am not sure if these changes are already in placed in 3.2.x. In 3.4.x. I needed to explicitly defined a unix "nobody" user. guest account = smb_nobody I also had to explicitly grant admin perms to the domain admins group so that they had sufficient privileges on local PC's. But I think I had made some error somewhere else, so I don't think you will encounter this. I have an ldap backend, and I found with 3.4.x or 3.5.x. that joining the machine to the domain had some issues relating to ldap attributes being created or set properly. On 06/04/12 09:30, Robert Adkins II wrote: > I'm looking for confirmation that what I am about to do will work. > > My intent is to decommission the existing Samba PDC hardware and put in its > place the new hardware. I intend on having the users see no difference, in > terms of what they have/had and will continue to have available. > > Right now I will be copying everything from the /etc/samba directory into > the same on the new server, moving from Samba 3.2x to Samba 3.6x > > I also intend on copying over the passwd, shadow and group files. > > Am I missing anything? > > Thanks. > > -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba