Posted on 2007-11-20
In my ongoing quest to correct the mistakes of the ghosts of IT past, I will soon be changing our internal domain - new server, new domain. Previous admin(s), not thinking things through, chose to name our internal, NAT'd domain the same as our hosted, external (internet) domain. This has caused no end of problems, particularly with the Exchange server, which someone, as some point, decided to "upgrade" to the 2000 version from the 2003 version, seriously breaking the whole mess. As if it wasn't already hosed.
Anyway, since this particular operation is a new venture, I figured I'd get some tips and give away a few points. So, here's what I need to know:
On a Windows 2000 domain, moving to a Windows 2003 domain with a new name...
1 - Is there any way to move the users, and their respective systems, to the domain without going machine to machine, joining them to the domain, copying all their stuff in Doc's n Settings, etc...? Like some sys admin program or script that sucks them all onto the new domain, complete with all their personal stuff?
2 - Is there a way to migrate their accounts from the old domain to the new one, including permissions and settings?
It shouldn't make a difference, but the old domain does not use roaming profiles, and the new one will.