How to migrate the SYSVOL replication system from FRS to DFS-R

Since Windows Server 2008,  DFS-R can be used for SYSVOL replication instead of FRS.

A domain controller on Windows Server 2019 is no longer compatible  with FRS for SYSVOL replication.

If you still use FRS for SYSVOL replication, you have to migrate to DFS-R to be able to add an additional domain controller on Windows Server 2019.

If the first domain controller is promoted on Windows 2008 or higher and the Domain functional level is Windows 2008 or higher  , DFS-R will be automatically used for SYSVOL replication.

In this article, I will show you how to migrate SYSVOL replication system from FRS to DFS.

Prepare prerequisites:

• All domain controller running on Windows Server 2003 must be demoted 
• The Domain Functional Level must be 2008 or higher :
  
  
  
  
  
  
• Check the replication status and domain controllers health:
  
      
  
  
• Check the DFSR migration status, you can use the following command:

  dfsrmig /getglobalstate

  
  
  

Before starting the migration, you can check the current sysvol path by running the  command net share on each domain controller:

You can also check the SYSVOL path from registry key:

How to migrate SYSVOL replication system to DFS-R:

• Run the following command to start the migration:

dfsrmig /setglobalstate 0

• Run the following command to change the migration state from "Started" to "Prepared" on all domain controller:

dfsrmig /setglobalstate 1

During in this step a new folder named SYSVOL_DFSR will be created on all domain controllers:

Run the following command to check if all domain controllers are migrated to "Prepared" state before performing the next step:

dfsrmig /getglobalstate

• Run the following command to change the migration state from "Prepared" to "Redirected":

dfsrmig /setglobalstate 2

During in this step, it is recommended to avoid any modification on sysvol share ( GPO,script..ect) because the SYSVOL folder will be moved to  SYSVOL_DFSR.We can check it from the registry key value once the domain controller status become "Redirected":

We can also use net share to check the new path of sysvol share:

Run the following command to check if all domain controllers are migrated to "Redirected" state before performing the next step:

dfsrmig /getglobalstate

• Run the followings command to change migration state from "Redirected" to "Eliminated":

dfsrmig /setglobalstate 3

 

In this step , the old folder sysvol will be deleted:

The Ntfrs service will be also disabled  on all domain controllers:

Run the following command to check if all domain controller are migrated to "Eliminated" state:

dfsrmig /Getglobalstate