Blog Post

ITOps Talk Blog
5 MIN READ

How to Migrate Windows Server 2008 R2 FSMO roles to Windows Server 2019

Rick Claus's avatar
Rick Claus
Icon for Microsoft rankMicrosoft
May 07, 2019
With the "end of support" on the horizon for Windows Server 2008 R2 coming January 2020, folks are looking around for resources to help them check off some high ticket items from their "to do" list. ...
Updated May 13, 2019
Version 2.0
powershell
Windows Server
Rick Claus's avatar
Rick Claus
Icon for Microsoft rankMicrosoft
Nov 25, 2019

Hey Bijay_George 

Regarding your questions: New IP address and computer name for the role holder should have NO impact on your environment - unless you have clients or applications who have hard coded the IP address or computer name into their authentication mechanisms. I.E. Say a user went and mapped a shared drive to the DC for some reason - that machine name (or IP address) would be different now and it would not work.  

 

All replication needs to propagate across all your DCs using your site replication process and schedule. Once that takes place - you could take over the original IP address, restart the server so that it registers all appropriate services with the new IP, and allow for replication to once again propagate. I am PERSONALLY not a big fan of changing the computer name - but that could also be done.  Because this is a NEW domain controller built from a clean member server - you are not going to be introducing DUPLICATE SIDs. 

 

As for your 2nd question - i was making the lab assumption that these additional services ARE NOT on the domain controller and are on different member servers. if that is not the case - you would have to migrate those services OFF to a different system. I have details on how to migrate DHCP, DNS is included as part of AD.