Re: [Samba] Moving Samba PDC from one server to another...
Robert Adkins wrote: ...along with upgrading from the Samba 2.2.x line to the 3.x line. I have been reading through the Samba documentation and haven't found anything regarding moving a Samba PDC from one server to another server and also upgrade the Samba version. Am I looking at a lengthy removing and rejoining of all PCs from the "old" domain to the "new" domain and copying over the application data from their roaming profiles off the old server to the new server? It seems like there should be an "easy" way to handle this. Thanks for any pointers to documentation covering this. -Rob I am interested in the same. I am moving from 3.0.22 to 3.0.23b and my first attempt was a total disaster. I simply added the "domain master = yes" to the new PDC and set it to no on the old PDC, keeping the same domain name. Things didn't work as expected. Login scripts didn't run. And I had some issues with Netbios aliases, but I may do something different with that anyway. Is there something that needs migrated, like a .tdb file, that needs moved from the old PDC to the new one? I'm using LDAP as the backend so I would imagine all the info the domain needs would be in there. I also had another issue that may not have been related, but I'll ask. It seems like every time I used the new PDC (3.0.23b) and tried to log on to a Windows 2003 server as administrator, I would get an "lssass.dll" error and the server would reboot on it's own. I have not seen that happen on the old PDC using 3.0.22. Thanks! Mark -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Removing Samba+LDAP, replacing W2k3+AD
Collins, Kevin wrote: Four years ago, I migrated our network from Windows NT based servers to Linux, Samba+LDAP based setups. This setup has worked fine. Last year, we replaced our Exchange 5.5 server - the last "real" Windows server - with Scalix. This last decision has come back to bite me. Several new "thingys" that the boss wants, among other things, are forcing me to implement Exchange 2003. Because I know that Exchange 2003 requires AD and my company has three offices separated by a WAN, I'm going to be forced to rip out my Samba underpinnings. The fact is, I don't know the best way to accomplish this. I know the one way that this will work is to bring up an AD domain beside the Samba domain and move things around by hand - but that is going to cause a unbelievable nightmare with user profiles, and machine accounts, and all the other crap that goes along with being part of a domain. So my question is this: Can I bring up a Windows 2k3 machine as a member server in the Samba domain. Promote it to become an AD Domain Controller in mixed mode - retaining the domain SID, user and machine accounts and such so that I do not have to touch my workstations? I really curious what features of Exchange 2003 you have to have. We started with Exchange 5.5, migrated to Oracle Collaboration Suite. Threw that out and now use E-Groupware for collaboration with LDAP and Samba for the rest. We also use open source for our phone system so integrating it all together hasn't been bad. Hate to see someone go the other direction :) Mark -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] User Manager
Gerald (Jerry) Carter wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Volker Lendecke wrote: On Fri, May 26, 2006 at 11:44:12AM -0400, Mark Johnson wrote: I've used User Manager with no issues from the prereleases of 3.0 through 3.0.6. I have a need to upgrade samba so I installed 3.0.22. Now, User Manager complains that the "stub received bad data". Not much in the logs indicate an issue. Any ideas as to what's wrong or how to debug it? I use LDAP as the backend. Please open a bug report at https://bugzilla.samba.org and upload debug level 10 smbd logs and a network trace of usrmgr.exe operation up to the failure. But please retest against 3.0.23rc1 first. I think something is broken in 23rc1 with LDAP as the backend. "testparm" did not reveal any issues with my config file, but all I get is hundreds of messages in the smbd.log file that it couldn't connect to the LDAP servers. If I roll it back to 3.0.22, LDAP works fine. Did something drastically change in 23rc1 for LDAP? I noticed the configure option changed and I tried it with auto and specifying --with-ldap, but with the same results. Mark -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] User Manager
I've used User Manager with no issues from the prereleases of 3.0 through 3.0.6. I have a need to upgrade samba so I installed 3.0.22. Now, User Manager complains that the "stub received bad data". Not much in the logs indicate an issue. Any ideas as to what's wrong or how to debug it? I use LDAP as the backend. Thanks! Mark -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] : Win XP Client does not remove directories
Jeremy Allison wrote: What does this error mean ? "Datei oder Verzeichnis nicht gefunden". That's the strerror output string when the remove_directory call fails. Jeremy. I had a problem very similiar to this with roaming profiles. The cause came down to the client and the servers time was not sync'd up. I never figured out how far off it needed to be before it broke it, but once I sync'd the time, I've never had a problem with the directories since. Mark -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
