Some of the problems that you can have while doing FRS to DFSR Migration

  • Article

This is the official guide for FRS to DFS Replication Migration https://www.microsoft.com/downloads/details.aspx?familyid=A27008A8-4B28-49CC-80B5-05B867440AF9&displaylang=en

 

Some of the problems that you might have (for Windows 2008):

 

https://support.microsoft.com/kb/972105

This problem occurs because the Robocopy process that is used during the SYSVOL migration from the Prepared state to the Redirected state incorrectly sets a NULL System Access Control List (SACL) that propagates to all files. This changes the SHA-1 file hash that is used by DFSR for file comparison between servers and leads to the conflicts.

Typically, the conflict events occur when you run the DFSRMIG.EXE /SETGLOBALSTATE 2 command without first running the DFSRMIG.EXE /SETGLOBALSTATE 1 command.

However, the conflict events may occur when you use the typical steps:

DFSRMIG.EXE /SETGLOBALSTATE 1
DFSRMIG.EXE /SETGLOBALSTATE 2

The unnecessary replication of files, without conflict events, always occurs when the migration reaches the Redirected state.

 

https://support.microsoft.com/kb/967326

 

Consider the following scenario: You use the DFS Replication service migration tool (Dfsrmig.exe) to migrate the SYSVOL share from the File Replication Service (FRS) to the Distributed File System Replication (DFSR) service in a Windows Server 2008-based domain.

Some read-only domain controllers (RODCs) exist in this domain.

In this scenario, the Windows NT File Replication Service (NTFRS) subscriptions containers are not deleted on domain controllers in this domain after the migration process. This issue may cause large data loss if all of the following conditions are true:

Active Directory is removed from one of the domain controllers in this domain.

Active Directory is installed on this same domain controller in another domain.

In the new domain, you use the Dfsrmig.exe tool to migrate the SYSVOL share from the FRS to the DFSR replication service. In this case, two junctions point to the same target ( %SYSTEMROOT%\Sysvol_dfsr\ domain) after the migration.

If an administrator finds the redundancy that is triggered by this scenario and deletes the additional junction, all group policy objects and scripts in the new domain are deleted on all domain controllers after Active Directory service replication.

 

https://support.microsoft.com/kb/969688

Consider the following scenario: You use the DFS Replication service migration tool (Dfsrmig.exe) to migrate the Domain System Volume (SYSVOL share) on a computer that is running Windows Server 2008.

You try to migrate the SYSVOL share from the File Replication Service (FRS) to the Distributed File System Replication (DFSR) service.

A disjoint namespace is configured in the domain.

In this scenario, the SYSVOL share migration process fails.