This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(73.60000000000001, 59%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPC%3C/text%3E%3C/svg%3E)
I am migrating old DC (VM) with windows 2012 R2 to new DC (VM) with windows 2019. Old DC also has DNS, DHCP, FS, PS and IIS roles in it. I want to keep the same name and ip address and i.e. why I would like to show the steps I am planning to do so that if I am missing something important I can work on that before doing the final migration. Please let me know if something is missing or some order needs to be change.
1 Create new VM in HyperV and Install 2019. Add it to domain and set TCP/IP etc.
2 Export Certificates, firewall, IIS, DHCP and PS settings from existing 2012R2 DC and copy it into new 2019 server.
3 Using Robocopy transfer all data w/o deletion (FS related) to new server (I are planning SharePoint online later this year, therefore, not creating a separate FS).
4 Prepare existing 2012 R2 server AD forest for 2019 DC
5 Transfer all 5 FSMO roles to the new server
6 Only Install DHCP, FS, PS and IIS one by one without setting it configurations
7 Promote the new server to a domain controller using ADDS config wizard and replicate the DNS from old DC
8 Import DHCP, DNS, IIS, PS files
9 Demote the old DC and configure the IP address and name of the new server to match the old server and turn off the old server. Reboot the new DC.
10 Raise the domain and forest functional levels
11 Verify the migration. If needed (Import firewall, certificate settings) and run flushdns, registerdns, dcdiag/fix to fix any record and reboot the DC.
Thanks Daisy
Hi Daisy, why did you remove your answer. I was thinking on working on some recommendations today.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(96, 62%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDZ%3C/text%3E%3C/svg%3E)
Hello Puneet Chauhan,
I am sorry I did not remove it （I do not know why someone deleted my answer）. Now I have “undeleted” it. You can refer to read it.
Best Regards,
Daisy Zhou
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
1 deleted commentComments have been turned off. Learn more
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(137.6, 98%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAS%3C/text%3E%3C/svg%3E)
You can do the extra step of renaming and re-addressing the new DCs, but I wouldn't recommend it. Are you doing this because you have other functions you put on your domain controllers?
Yes Amit, I have DHCP, DNS, FS, IIS and PS installed in the current DC. Also, I have already upgraded all the other servers to 2019 in the last 3 month i.e. NPS, CA, WSUS, AD connect etc. and they all including different group policies are linked to the current DC. I find it better to work on the DC only instead of changing all other servers settings. So that my focus will be on one subject only if there's an error.