Hello da3rd,
Thank you for posting here.
Here are the answers for your reference.
Q1: What should be the Forest and Domain Exchange Schema version to prepare for Windows Server 2019 Domain Controller migration?
A1:
1.Before we add 2019 DC into existing domain, we should ensure: The minimum requirement to add a Windows Server 2019 Domain Controller is a Windows Server 2008 functional level. The domain also has to use DFS-R as the engine to replicate SYSVOL.
2.Before we do any change in existing AD domain environment, we had better do:
1)Check if AD environment is healthy. Check all DCs in this domain is working fine by running
Dcdiag /v. Check if AD replication works properly by running
repadmin /showrepl and
repadmin /replsum.
2)Back up all domain controllers.
3.For migrating DC from lower version to Windows server 2019, the steps below are for your reference:
1)Add the new Window server 2019 to this existing domain.
2)Add AD DS and DNS roles and promote this Windows server 2019 as a DC (also as a GC).
3)Check if AD environment is healthy again.
4)If AD environment is running fine, we can transfer FSMO roles to new 2019 DC if needed.
5)Demote old DC if needed after transferring FSMO roles. Before we demote 2012 R2 DC, we should also check:
If the removed DC was a DNS server, update the DNS client configuration on all member workstations, member servers, and other DCs that might have used this DNS server for name resolution. If it is required, modify the DHCP scope to reflect the removal of the
DNS server.
If the removed DC was a DNS server, update the Forwarder settings and the Delegation settings on any other DNS servers that might have pointed to the removed DC for name resolution.
Meanwhile, for forest and domain functional level and Exchange version, we can refer to the link “Exchange Server supportability matrix” Dave provided.
Q2: What would be the ideal method in using the same Server Name for a domain controller that you are replacing?
A2: Usually, if we have more than two DCs in our domain, if we want to use same hostname and IP for new 2019 DC , as the old DC that we need migrate (such as DC1) during DC migration.
1) Check AD health and transfer fsmo roles from one DC that we need migrate (such as DC1) to another DC.
2) Demote DC1 and shutdown.
3) Delete the computer object from AD.
4) Change the hostname and IP address of 2019 , same as DC1 and join to domain.
5) Promote the win2019 server as DC (DNS server and GC server) and monitor health status.
6) Transfer fsmo roles to new win2019 DC if needed.
Q3: What is the ideal method to do this and yet use the same server name without having to demote the new one, change the name, and re-promote it again?
A3: We can rename domain controller, we must use this renaming method (
Netdom command) only if the Domain Controller that you want to rename is your only Domain Controller. If you have multiple domain controllers in your network
you should introduce a new Domain Controller, demote the old domain controller and rename it and promote another new domain controller with the old hostname. It is the better way to demote and promote in a more complex situation. Though we can perform a rename
of a domain controller (in the situation where there are more than one domain controllers), but it is not recommend.
We suggest we have at least two DCs in one domain.
After we rename domain controller, we should update the FRS or DFS replication member object manually.
For renaming domain controller, we can refer to the following link.
Rename a Domain Controller Using Netdom
https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc816601(v=ws.10)?redirectedfrom=MSDN
For update the FRS or DFS replication member object, we can refer to link below.
Update the FRS or DFS Replication Member Object
https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc794759%28v%3dws.10%29
If we must rename domain controller, we must have a full backup of our domain controller before you perform this procedure and you must know how to perform a disaster recovery if things fail.
Hope the information above is helpful. If anything is unclear, please feel free to let us know.
This "Migration" Forum will be migrating to a new home on Microsoft Q&A, please refer to this
sticky
post for more details.
Best Regards,
Daisy Zhou
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact
tnmff@microsoft.com.
"Migration" forum will be migrating to a new home on
Microsoft Q&A!
We invite you to post new questions in the "Migration" forum's new home on
Microsoft Q&A!
For more information, please refer to the
sticky post.
