Link to home
Create AccountLog in
Avatar of K_Wilke
K_Wilke

asked on

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

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.
ASKER CERTIFIED SOLUTION
Avatar of Shaun Vermaak
Shaun Vermaak
Flag of Australia image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of K_Wilke
K_Wilke

ASKER

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.
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
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.).
Avatar of K_Wilke

ASKER

Thank you very much