Migrate Master Domain Controller from 2012R2 to 2016 (both Standard)

K_Wilke
K_Wilke used Ask the Experts™
on
Hello all,
I am having to migrate a master domain controller from a Windows 2012 R2 server to a Windows 2016 server (both are standard OS) due to a failure on that 2012 R2 and the age of the server.  This server is running AD, DNS, DHCP, and WSUS
When I did a 2008 to 2012 R2 migration I did the following steps:
1)  dcdiag /v /c /e on old server
2)  Fix issue on above.
3)  Ensure AS integrated zones on DNS
4)  Bring new server (with temporary name and IP address) into AD
5)  Copy all folders and files necessary to new server.
6)  Transfer Global Catalog
7)  Transfer FSMO Roles
8)  Transfer DNS
9)  Transfer DHCP
10)  dcpromo (demote) old server
11)  Run metadata cleanup
12)  Change IP address and name of new server
13)  Deal with all shares, etc. on new server.

Are these steps all the same or are there extra steps that I am missing?
Also I have never had to transfer WSUS.  When do I do this in these steps and what are the steps to do this?

Thanks,
Kelly W.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Technical Specialist
Awarded 2017
Distinguished Expert 2018
Commented:
4)  Bring new server (with temporary name and IP address) into AD
I assume this step is the promotion?

The steps are basically the same but I would not put WSUS and file shares on a DC
Distinguished Expert 2018
Commented:
I also don't recommend renaming a machine AFTER promoting it.  Personally nalkybi don't recommend renaming a machine at all. AD is multi-master and renaming isn't necessary. For file shares, DFS eliminates machine name dependencies and as previously mentioned, file shares on a DC is generally frowned upon anyways. But if you are small and need to colocate file shares, take the time to set up DFS for easier management on the future.

Author

Commented:
Okay so how do you replace a server within AD that has the same name IF you cannot rename the machine after promoting it?
And yes this is a small client.
Expert Spotlight: Joe Anderson (DatabaseMX)

We’ve posted a new Expert Spotlight!  Joe Anderson (DatabaseMX) has been on Experts Exchange since 2006. Learn more about this database architect, guitar aficionado, and Microsoft MVP.

Shaun VermaakTechnical Specialist
Awarded 2017
Distinguished Expert 2018

Commented:
You can rename the DC without any issue. I do however agree that you shouldn't if you can change your process to prevent a DC rename
Distinguished Expert 2018

Commented:
The answer is don't replace the server with the same name.  Replace the server with a new different name. Eliminate dependencies on server names in the environment (which for a DC should be trivial or non-existent.).

Author

Commented:
Thank you very much

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial