Domain migration options

[iad]

Hi all,

Implementing a W2K8 domain that replaces an older W2K3 domain. Domain name is being changed and the new setup is basically a complete, all-new hardware and software drop-in replacement for the old one. I am exploring options for transferring a portion of the AD database (user accounts), files (w/ ACLs intact), etc from the old system to the new one. Group Policy does not need to be migrated and there is no real need to duplicate anything else from the old system - just don't want to have to re-do all of the AD user objects and file permissions. Exchange will also need to be migrated from the old Exchange server (2003) to a new 64-bit server with 2007. SQL 2005 Std is another migration task between the old and new systems.

I'm guessing that there are several options for doing this - one thought that I had was building the new system and then doing a cross-forest trust between the old and new but I haven't finished my research yet and am not sure if this will actually enable me to do what I want to do. The old system needs to stay up until the new one is ready to service clients but once it is ready the old one is going away. Is this the best way to do this migration or are there other methods that would be a better idea?

Thanx...

 

[pagy]

Well you could set up a new forest and use ADMT to transfer user accounts across;

http://www.microsoft.com/downloads/...01-7dca-413c-a9d2-b42dfb746059&displaylang=en

Why don't you just add a W2K8DC to your existing environment and save yourself a lot of hassle though? Is there some business requirement that requires a new domain name? If so you could always rename your existing domain if needed.

Paul
MCSE 2003
MCSA 2003
MCITP Enterprise Administrator

If there are no stupid questions, then what kind of questions do stupid people ask? Do they get smart just in time to ask questions?
Scott Adams

 

[iad]

Hi pagy,

Thanks for your reply - without boring you with too many details, there are politics at my company that require the domain name change. As far as joining to the existing domain and then renaming, I was trying for a "clean slate" approach with the new system being truly a "new" system and not part of the old one. I've used the ADMT before and that might be the best option based on what I want to do here.

Thanks again...iad

 

[58sniper]

Not using the ADMT means touching every workstation and server to remove it from the existing domain and adding it to the new domain. Then you have to move profiles, etc. ADMT automates that.

Rename the domain first, then add the new 2008 DC.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/