Domain Migration/Change

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.
LVL 11
knoxzooAsked:
Who is Participating?
 
cj_1969Connect With a Mentor Commented:
This might save you some work ...
Why not integrate the 2 and have a mixed domain ... this will get all your account information over.
Then you can remove the 2000 DCs and upgrade to a pure 2003 domain.
Once upgraded you can then rename the domain to the new one that you want.

Take a look at these links and see if this seems like a viable option for you ....
http://technet.microsoft.com/en-us/windowsserver/bb405948.aspx
http://www.msexchange.org/tutorials/Domain-Rename.html

P.S.  Make sure you plan well for those roaming profiles ... if not impimented well, they can kill your network performance during logon/off.
0
 
knoxzooAuthor Commented:
Oops!  I knew I was forgetting to mention something.  Current plans are for the Exchange server to go the way of the dodo bird.  It may make a return at some point in the future, but we're already using a hosted e-mail server and Google calendar, so adding Exchange back into the mix seems a bit pointless.

Thanks for the comments, folks.  The browser windows are open and waiting for me to finish typing this.
0
Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
Jay_Jay70Connect With a Mentor Commented:
unfortunalely nothing is going to join those machines to your domain except yourself :)

ADMT is the best for a simple migration of user accounts and groups....You are going to need the new domain up and running with a trust between the two

My advice, try and keep everything as new as possible so its nice and clean
0
 
knoxzooAuthor Commented:
Good links and good advice.  The advice was pretty much common sense and what I'd planned, but it was good anyway.   Thanks, folks.
0
 
knoxzooAuthor Commented:
Appreciate the help and comments folks.  

I've upgraded countless domains and networks, but, for whatever reason, the notion of using the same tools and techniques to transfer things between different domains didn't even occur to me.  Too close to the problem, I guess.

Come to think of it, that's how I got some of the points I have - people being too close to the problem.
0
 
Jay_Jay70Commented:
**grin** welcome to my world
0
All Courses

From novice to tech pro — start learning today.