Which Sysvol Replication Migration State Is Done Entirely Using Frs?

Which Sysvol Replication Migration State Is Done Entirely Using FRS?

Sysvol (System Volume) is a shared folder in Active Directory infrastructure that stores group policies, scripts, and other important system files. Sysvol replication is crucial to ensure that all domain controllers have the same copy of these files. In Windows Server 2008 and later, Sysvol replication can be achieved through two different methods: File Replication Service (FRS) and Distributed File System Replication (DFSR).

FRS was the original replication method used in Windows Server 2000 and Windows Server 2003. It is a simple and reliable replication mechanism, but it has its limitations. DFSR was introduced in Windows Server 2003 R2 as the successor to FRS and provides more robust and efficient replication capabilities. However, migrating from FRS to DFSR requires careful planning and execution.

The migration process involves transitioning the replication of the Sysvol folder from FRS to DFSR. There are four possible migration states that can be used to track the progress of the migration:

1. Start: In this state, FRS is the active replication method, and no migration has been initiated. The Sysvol folder is fully replicated using FRS.

2. Prepared: In the prepared state, the domain controllers have been prepared for migration, but the actual replication is still happening using FRS. This state is a transitional stage where both FRS and DFSR coexist.

3. Redirected: Once the domain controllers are prepared, the replication is redirected from FRS to DFSR. The Sysvol folder is still being replicated using FRS, but any changes made to the folder are redirected to DFSR.

See also  Why Did Coach Prime Leave Jackson State

4. Eliminated: In the eliminated state, the migration is complete, and all domain controllers are using DFSR for Sysvol replication. FRS is no longer involved in the replication process.


1. Why should I migrate from FRS to DFSR?
Migrating from FRS to DFSR provides several benefits, including improved replication efficiency, faster replication of changes, better conflict resolution, and enhanced scalability. DFSR also offers better support for large files and supports more advanced features like Read-Only Domain Controllers.

2. How can I check the current migration state?
You can check the migration state using the “dfsrmig /getmigrationstate” command in an elevated command prompt on each domain controller. The command will display the current migration state for that particular domain controller.

3. Can I rollback the migration process?
Once you have reached the “eliminated” state, there is no built-in rollback option. It is essential to carefully plan and test the migration process before initiating it. However, if you encounter any issues during the migration, you can still revert to the FRS replication method by restoring the system state backup of the domain controller.

4. How long does the migration process take?
The migration process can vary in duration depending on the size of the Sysvol folder, the number of domain controllers, and the network bandwidth. It is recommended to start the migration during a maintenance window to minimize any potential disruption.

5. Can I skip the “prepared” state and directly go to the “redirected” state?
No, it is not possible to skip the prepared state. This state ensures that all domain controllers are ready for migration and have the necessary prerequisites in place. Skipping this step can result in replication issues and data loss.

See also  What County Is Fairfield Pa In

In conclusion, migrating from FRS to DFSR for Sysvol replication is a crucial step to improve the efficiency and reliability of your Active Directory infrastructure. It is essential to plan the migration carefully, test it thoroughly, and monitor the progress to ensure a successful transition. By following the migration states, you can track the progress and ensure that the migration is completed entirely using FRS.