Discussion Locked

Move 2000 clients to new 2003 domain

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a small home network running Windows 2000 Server on a DSL connection with the local AD/domain name 'lair.org', NetBIOS name "LAIR". Do to poor understanding on my part, the 'lair.org' name conflicts with the 'public' DNS domain of the same name. But, through some cludgy workarounds, things are working okay.

I want to get rid of the 400Mhz PII server running Windows 2000 SP4 and migrate my user machines into a brand new Windows 2003 Native mode domain (on completely different, faster/better hardware), most likely called 'lair.local' ("lair"). Problem is, I'd very much prefer to NOT loose/disassociate all existing user profile data on the existing client machines.

In other words, I have my login 'bear' and it's associated registry hive and profile data/directory. I want to associate that login and it's data, now known as 'lair/bear' or 'bear@lair.org', with the new login.

Can I somehow 'migrate' this profile into the new domain? I'm concerned about SIDs and machine accounts and all of that.

Thanks!
Don 'Bear' Wilkinson (bear@lair.org)

5 replies

by cg it

not a problem since DCs within the root are peers with each other. Just install your server as a member server, dcpromo promote to a DC AD intergrated, replicate, dcpromo demote the old one out. If your not using W98 clients which require NetBIOS over TCP/IP dump it.

I think first and foremost is plan what your network is e.g. public domain name. If you own Lair.org, then your internal private network name can be anything you want and it's best to have some extension thats not public like .local or .loco or .whosits and use private IP addressing.

by drwilkinson

Thanks for your input.
I originally neglected to describe the history here. I have had the 'new' server as a member of the existing domain, dcpromo'ed it to DC (peer), etc. But, in doing so I would have been inheriting some quirks of the existing AD structure. Being my my first-ever deployment of AD, it's a bit of an amateurish mess. :)

by drwilkinson

Clarification: I want to 'abandon' the old domain and it's AD structure. So, adding the new server into the old forest/domain is not the method I'm planning.

by cg it

your requirements were to maintain all existing user profile data on the existing client machines. Since you currently have a AD domian and wanted to replace the aging machine with a new one, the process of adding a DC peer and removing the aging machine is pretty straight foward and painless.

If your creating an entirely new domain you can use the ADMT to migrate over. Further if you migrate over to Windows Server 2003 you can actually change the name of the domain [but not with W2K]. Domains are security boundries. That is by design. SIDs, ACL, user accounts machine accounts are for the domain in which they were created in.

here's a link to a Microsoft Web cast on chaning domain names in Windows Server 2003. I believe that if you have your new server running on your W2K AD network as a DC, you can change your domain name provided that the Windows Server 2003 is the root server with the global catalog and Schema master roles. Watch the web cast.

http://support.microsoft.com/kb/819145

by dc1

Use ADMT from Microsoft (use 2nd version that comes with W2003 so passwords are migrated as well). This will do exactly what you are looking for. If you are willing to spend some money to do this look at products from Quest Software of NetIQ as they have some nice features but may be overkill for what you are trying to accomplish.

This discussion is closed to new replies.