Error while promoting new Windows Domain Controller

While trying to add a new Windows 2019 server to a Microsoft Windows Domain and then dcpromo it to a domain controller I was presented with the following error. “Verification of replica failed. The specified domain [DomainName] is still using the File Replication Service (FRS) to replicate the SYSVOL share. FRS is deprecated. “ “You must migrate the specified domain to DFS Replication using the DFSRMIG command before continuing”

DCPROMO Error - Verification of replica failed
Verification of replica failed.

This prevented me from adding a new domain controller and removing a server that was to be decommissioned. Below are the steps that Fixed IT for me. These steps use an elevated command prompt and are run from an existing domain controller. As always take full backups of all servers and Active Directory data in case there are any issues.

Check the current status of Active Directory

Run the below command from an elevated prompt on a current Domain Controller in the domain. This command should return some data similar to the below screen shot.

dcdiag /e /test:sysvolcheck /test:advertising

dcdiag command
dcdiag command to check status

Windows Domain Migration DFSRMIG -Step 1

The next command may take a while to run depending on the size of your domain so be patient. This is also run from an existing domain controller.

dfsrmig /setglobalstate 1

dfsrmig /setglobalstate 1
dfsrmig /setglobalstate 1

To check the progress of the last command there is another that can be run.

dfsrmig /getmigrationstate

This will show which domain controllers have not sync’d yet. In a small domain with only two domain controllers this took about 5-10 minutes. When complete it should show the status as seen in the screen shot below.

dfsrmig /getmigrationstate
dfsrmig /getmigrationstate

Windows Domain Migration DFSRMIG – Step 2

This next command sets the domain to a state of “redirected”. This may take a few minutes as well so be patient and use the same command as above to check the progress.

dfsrmig /setglobalstate 2

dfsrmig /setglobalstate 2
dfsrmig /setglobalstate 2

Check the progress using the command

dfsrmig /getmigrationstate

When done the result should look like:

Windows Domain Migration DFSRMIG – Step 3

The last command needed is

dfsrmig /setglobalstate 3

This last step sets the domain to DFSR global state to “Eliminated”. Note that this can not be undone. Again check progress after the command is run to confirm it completed successfully.

 dfsrmig /setglobalstate 3
dfsrmig /setglobalstate 3

Give the above step a few minutes to complete then check the progress using

dfsrmig /getmigrationstate

When completed successfully, the results should look like the below screen shot.

dfsrmig /getmigrationstate
dfsrmig /getmigrationstate

Once Successful the Windows 2019 server should now be able to be promoted to a DC in the Windows Domain.

How long does it take to Migrate FRS to DFSR?

For the Windows domain above that had two domain controllers, one being a Windows 2008 R2 server and the other being a Windows 2012 server this whole process took about 30 minutes. I have read that much larger domains can take upward of hours to even a day or more.

Summary

The above process to migrate the domain from FRS to DFSR went smoothly for me but I cannot guaranty it will for all domains. After these steps I was able to cleanly add a new Windows 2019 server as a domain controller in this clients domain. If you have any comments or was able to get this to work for you please post in the comments.