It is also possible to check the overall status of the migration with the following command: dfsrmig /getglobalstateĪt this point, the new SYSVOL_DFSR folder is created. On the screenshot below we can see that it has not yet reached a consistent state on all controllers.Ĭheck the status periodically by re-entering the command to get a message that All Domain Controllers have been migrated to Global (“state x”). The command should give the following result:Ĭheck the status of the migration by entering the following command: dfsrmig /getmigrationstate On a domain controller, open a command prompt in Administrator mode and enter the following command: dfsrmig /setglobalstate 1

Delete the old SYSVOL folder and stop the FRS service.ĭuring migration, a new SYSVOL_DFSR folder will be created next to the existing SYSVOL folder.

Changing the SYSVOL share pointing to the SYSVOL_DFSR folder.

Preparing the environment by creating a new SYSVOL_DFSR folder that will be replicated with DFSR.

Migration takes more or less time depending on the number of DCs and the quality of the link between them. When increasing the domain functional level, the FRS to DFSR migration is not automatic, Microsoft provides a migration tool (dfsrmig.exe) on the domain controllers. To migrate to DFSR, the domain functional level must be in 2008, the AD environment must be in good health (dcdiag). Since Windows Server 2016 ( build 1709), it is no longer possible to install a domain controller in an environment using FRS. If your domain controllers are running Windows 2012R2, it is advisable to use DFSR for the SYSVOL folder.

Since Windows Server 2008 and its 2008 domain functional level, replication of the SYSVOL folder is supported by DFSR, before it was done by FRS.

Dossier sysvol active directory