Share via

Overview of the SYSVOL Migration Procedure

  • Article

Updated: April 15, 2009

Applies To: Windows Server 2008, Windows Server 2008 R2

The following sections provide an overview of the procedures that you perform when you migrate SYSVOL replication from File Replication Service (FRS) to Distributed File System (DFS Replication).

  • Migrating to the Prepared State

  • Migrating to the Redirected State

  • Migrating to the Eliminated State

  • Rolling Back Migration

Warning

To minimize the likelihood of the SYSVOL replication migration process causing problems in your environment, test the procedure prior to migrating a production environment. Consider testing the procedure in a lab (especially if domain controllers are separated by firewalls), using a simple domain as a pilot project, or by installing DFS Replication on domain controllers in the domain and testing the replication of other shared folders.

Migrating to the Prepared State

This migration phase includes the tasks in the following list. After this phase is complete, FRS will continue to replicate the SYSVOL shared folder that the domain uses, whereas DFS Replication replicates a copy of the SYSVOL folder.

  • Raising the domain functional level to Windows Server 2008.

  • Verifying that the SYSVOL shared folder is healthy and that FRS is correctly replicating SYSVOL by using the Ultrasound diagnostic tool or a manual procedures.

  • Backing up the data in the SYSVOL folder.

  • Verifying that the DFS Replication service is installed, has a Start Type of Automatic, and is running on the PDC emulator.

  • Running the dfsrmig /SetGlobalState 1 command on the PDC emulator to start the migration to the Prepared state.

  • Waiting for all domain controllers to reach the Prepared state, which you can verify by running the dfsrmig /GetMigrationState command.

  • Verifying that migration to the Prepared state succeeded.

Tip

To monitor the status of DFS Replication for SYSVOL, periodically run DFS Replication health reports and monitor the Event Log for DFS Replication events.

For information about how to raise the domain functional level to Windows Server 2008 and migrate SYSVOL replication to the Prepared state, see Migrating to the Prepared State.

To download Ultrasound, see https://go.microsoft.com/fwlink/?LinkId=121859. For information about Ultrasound, see the Ultrasound Help.

Migrating to the Redirected State

This migration phase includes the tasks in the following list. After this phase is complete, the DFS Replication copy of the SYSVOL folder becomes responsible for servicing SYSVOL requests from other domain controllers. FRS continues to replicate the original SYSVOL folder, but DFS Replication now replicates the production SYSVOL folder that domain controllers in the Redirected state use.

  • Verifying that migration has reached the Prepared state on all domain controllers and that the domain is prepared to migrate to the Redirected state.

  • Running the dfsrmig /SetGlobalState 2 command on the PDC emulator to start the migration to the Redirected state.

  • Waiting for all domain controllers to reach the Redirected state, which you can verify by running the dfsrmig /GetMigrationState command.

  • Verifying that migration to the Redirected state succeeded.

For information about how to migrate SYSVOL replication to the Redirected state, see Migrating to the Redirected State.

Migrating to the Eliminated State

This migration phase includes the tasks in the following list. After this phase is complete, DFS Replication is exclusively responsible for SYSVOL replication. Windows deletes the original SYSVOL folder, and FRS no longer replicates SYSVOL data.

  • Verifying that migration has consistently reached the Redirected state on all domain controllers and that the domain is prepared to migrate to the Eliminated state.

    You cannot reverse migration after migration reaches the Eliminated state. Therefore, you should make sure that all domain controllers have migrated to the Redirected state and that the DFS replication service can handle SYSVOL replication correctly before you begin the migration to the Eliminated state.

  • Running the dfsrmig /SetGlobalState 3 command on the PDC emulator to start the migration to the Eliminated state.

  • Waiting for all domain controllers to reach the Eliminated state, which you can verify by running the dfsrmig /GetMigrationState command.

  • Verifying that migration to the Eliminated state succeeded.

  • Removing the FRS role service if it is not used for other purposes and is no longer needed.

Warning

If you migrate directly from the Start state to the Eliminated state, each domain controller automatically progresses through all of the intermediate steps and eliminates FRS. Doing so gives you no opportunity to troubleshoot problems before you commit your domain to the migration. Therefore, this approach is not recommended.

For information about how to migrate SYSVOL replication to the Eliminated state, see Migrating to the Eliminated State.

Rolling Back Migration

You can reverse the migration process any time before you migrate to the Eliminated state. However, after you migrate to the Eliminated state, you can no longer roll back the migration of SYSVOL replication to DFS Replication. The steps for rolling back migration resemble the steps for advancing through the migration phases. For more information about how to roll back the migration process, see Rolling Back SYSVOL Migration to a Previous Stable State.

Additional references

SYSVOL Migration Procedure

Troubleshooting SYSVOL Migration

SYSVOL Migration Reference Information

SYSVOL Migration Series: Part 1 – Introduction to the SYSVOL migration process