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.
LVL 6
K_WilkeAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Shaun VermaakTechnical SpecialistCommented:
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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Cliff GaliherCommented:
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.
K_WilkeAuthor 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.
5 Ways Acronis Skyrockets Your Data Protection

Risks to data security are risks to business continuity. Businesses need to know what these risks look like – and where they can turn for help.
Check our newest E-Book and learn how you can differentiate your data protection business with advanced cloud solutions Acronis delivers

Shaun VermaakTechnical SpecialistCommented:
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
Cliff GaliherCommented:
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.).
K_WilkeAuthor Commented:
Thank you very much
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2016

From novice to tech pro — start learning today.