Migrating existing domain to a new domain controller and keeping the server name

active-directorydomain-controllermigrationwindows-server-2008-r2

My current problem is the following migration scenario:

Existing domain:

Domain-Controller (Windows Server 2003 x86) named "W2003SRV" with domain DOMAIN.LOCAL
Terminal-Server 1 (Windows Server 2008 R2 x64)
Terminal-Server 2 (Windows Server 2008 R2 x64)
Client computers

Now we need to replace the Domain Controller with a new machine which will run Windows Server 2008 R2 x64 as well. Normally I would add the new DC to the domain, promote it to new DC, transfer Active Directory FSMO roles, demote the old one and be done with it.

However, the proprietory software that we use prohibits any change of the computer name. Adding the new DC to the domain first would mean that I have to give it another name, as the old one is still in use by the existing DC.

If I don't migrate the domain at all and create a new domain DOMAIN.LOCAL with the new server only (named W2003SRV like the old one) I would fullfil the criteria of keeping the name. As I would left with a completely new domain all my User SIDs would change, though, and even after recreating the Users and Computers in the Active Directory, a new profile would be forced on every user (with its new SID) and I would spend at least a day setting the new profiles up.

What other possibility do I have?

I thought about doing it that way and – after the new server has been promoted to DC – changing the name of the new DC to the one of the old DC. However changing the name of the (only) Domain-Controller in the domain doesn't seem that wise… Or am I worrying to much here?

I am grateful for every piece of advice!

Update:

ADMT (Active Directory Migration Tool) from Microsoft (as suggested by TheCleaner) seems to be the way to do it. It keeps the old SIDs in the SID history and thus the profiles would be reusable. I've looked into it and have downloaded the documentation. My only problem with that would be that it transfer AD objects from one Domain to another. I do have 2 domains but as both the server name as well as the domain name would be the same I think that is going to be a problem. Has anybody experiences with ADMT in such a case?

Best Answer

I would consider two approaches here, with #2 being my first choice. You could always get the domain and forest level up to 2008 R2 and then look at renaming the domain at that point if needed. I would also recommend that if possible you go with a 2012 server, but that might not be possible in your environment.

  1. If you think there is good reason to create a new domain, then I would consider going that route and using something like Forensit Profile Wizard to move the profiles over from the old domain to the new one on the computers/TS. Look at using ADMT as well to swing the users over from the old domain.
  2. Keep the existing domain and use the advice I was given when I had to do something very similar. See here: Windows 2003 DC to Windows 2008 R2 DC with same name and same IP This worked well for me, and allowed me to keep the name and IP without any issues.
Related Topic