VISIT THE NEWEST TUTORIAL
How to Migrate Active Directory and DNS from Microsoft Server 2012 to 2019
Introduction..
This article will give you the guidance to perform server migration from Windows server 2003 to Windows Server 2016. To make things easier entire tutorial is divided into 5 steps.
- Prepare Server 2003 for Migration
- Install Active Directory and promote (Server 2016)
- Confirm Replication & DNS in Server 2003 and 2016
- Transfer FSMO roles to the new server (Server 2016)
- Uninstall Old DC (Server 2003)
01. Prepare Server 2003 for Migration
In the Server 2003, Raise domain and forest functional levels to Windows Server 2003
02. Install Active Directory and promote (Server 2016)
Configure appropriate network settings. (Keep in mind that after server migration DNS server will be changed)
Join Server 2016 to the existing domain
Install Active Directory
Select Active Directory Domain Services and DNS server
After Installation completes Select Promote This Server to a Domain Controller
Keep the default Selection Add a domain controller to existing domain..
Type DSRM password
Click Install and Wait for a bit until installation completes and restarts
03. Confirm Replication & DNS in Server 2003 and 2016
Replicate using Active Directory Sites and Services
Check DNS
04. Transfer FSMO roles to the new server (Server 2016)
There are 5 FSMO roles which you have to Transfer From server 2003 to the new server 2016. You can do that either using powershell commands or GUI.
- Schema master
- Domain naming master
- RID master
- PDC emulator
- Infrastructure master
Type Netdom Query FSMO powershell command in the new server 2016 to check the current FSMO roles and their owner
Transfer the RID master, PDC emulator and Infrastructure Master Roles
Server Manager > Tools > Active Directory Users and Computers
In the MMC right click on the domain name and select operations masters
Change all three of them
Transfer domain naming master role
Server Manager > Tools > Active Directory Domains and Trusts
In the MMC, right click on Active Directory Domains and Trusts > Operations Master…
Transfer schema master role
Type run command regsvr32 schmmgmt.dll and Press OK in the next window
Type run command mmc
File > Add/Remove Snap-in…
Add Active Directory Schema and Press OK
Right click Active Directory Schema and click Change Active Directory Domain Controller
Select New Server 2016 from the list and Press OK
Right click Active Directory Schema > Operation Master and Press Change
Confirm that all the 5 FSMO roles have been moved to the new 2016 DC using Netdom Query FSMO command
05. Uninstall Old DC (Server 2003)
Now it is time to get rid of the old DC.
Type DCPromo in the RUN
Keep the default (do not tick Delete the domain because this server is the last domain controller in the domain)
Type Password
Click Next..
Click Finish to End the Removal process
Restart the Server
Notice that In the Server 2016, old Server is moved From Domain Controllers to Computers
Tech Encyclopedia 
Will the 2003 Server need a schema update to 2016 before promoting the 2016 server
LikeLike
No. just Raise the domain and forest functional levels to Server 2003.
LikeLike
We need to prepare the forestprep and Domain prep before start
LikeLike
what about IP means User & server
LikeLike
i didnt understand the question
LikeLike
Is there a back out way if something didn’t proceed properly? Thanks.
LikeLike
Firstly, you have to take the backup of the old server and restore it in a test server to make sure it works. If something goes wrong you can restore the backup so no problem.
LikeLike
Check your post doesnt work for 2003 server, it’s incompatible.
2016 only admits 2008
LikeLike
Actually it works
LikeLike
All steps are well but when running dcpromo I get the error
“The operation failed because:
A domain controller could not be contacted for the domain domain.local that contained an account for this computer.
Make the computer a member of a workgroup then rejoin the domain before retrying the promotion.
“The specified domain either does not exist or could not be contacted.”
Thank you for your guide!
LikeLike
Techencyclopedia is correct. As long as the forest level is up to 2003, you can go all the way up to 2016 for your server. You must have a forest level of 2008 or higher to go to 2019. I read an article that server 2019 highest forest level is 2016 though. I am in the process of going from 2012 to 2019 myself.
LikeLike
This is wrong function level must be 2008
LikeLike
Hello this is kind of of off topic but I was wondering if blogs use WYSIWYG editors or if you
have to manually code with HTML. I’m starting a blog soon but have no
coding expertise so I wanted to get advice from
someone with experience. Any help would be enormously appreciated!
LikeLike
I do not know whether it’s just me or if everyone else encountering issues with your site.
It looks like some of the text on your posts are running off the screen.
Can someone else please provide feedback and let
me know if this is happening to them as well? This could
be a issue with my browser because I’ve had this happen previously.
Kudos
LikeLike
FYI – you cannot promote Windows Server 2016 DC in 2003 domain environment. it’s not supported. You need to first promote to Windows 2008R2 or 2012 and then do a 2nd step to upgrade to 2016 once 2003 is completely removed in your
organization.
LikeLike
Not quit true. As long as Server 2016 is lower than version 1709 it will work due to FRS still being active.
Check this out
https://docs.microsoft.com/en-us/troubleshoot/windows-server/networking/windows-server-version-1709-no-longer-supports-frs
LikeLike
Thank you for this guide, I was able to migrate from 2003 straight to 2016 at a primary school that was badly in need of updating their server. The procedure went without a hitch, one of my smoother operations I’m glad to say.
LikeLike