How to Migrate SYSVOL Replication from FRS to DFSR

Applies to: Windows Server 2025 / 2022 / 2019 / 2016 / 2012 R2 / 2012 / 2008 R2 / 2008

Active Directory domain controllers use the SYSVOL share to replicate Group Policy files and logon scripts. Older domains can still use File Replication Service (FRS) for SYSVOL, while modern Windows Server environments use Distributed File System Replication (DFSR).

If your domain still uses FRS, you should migrate SYSVOL replication to DFSR before introducing newer domain controllers. Windows Server 2019 and later cannot be promoted as replica domain controllers in a domain that still uses FRS for SYSVOL replication.

In This Article

• 1. Before You Start
• 2. Check the Current Migration State
• 3. State 1 — Prepared
• 4. State 2 — Redirected
• 5. State 3 — Eliminated
• 6. Validate the Migration
• 7. Key Takeaways

1. Before You Start

Do not start SYSVOL migration until Active Directory replication and SYSVOL are healthy across all domain controllers.

• Verify that the domain functional level is at least Windows Server 2008.
• Confirm Active Directory replication is healthy.
• Confirm the SYSVOL and NETLOGON shares exist on all domain controllers.
• Resolve DFSR, FRS, DNS, or AD replication errors before continuing.
• Make sure recent system-state backups are available.

Useful pre-checks include:

dcdiag /e /c
repadmin /replsummary
repadmin /showrepl
net share

2. Check the Current Migration State

Before changing anything, check the current global state and confirm whether all domain controllers have reached it:

dfsrmig /getglobalstate
dfsrmig /getmigrationstate

The migration uses four global states:

• 0 — Start: SYSVOL is still replicated by FRS.
• 1 — Prepared: DFSR creates and synchronizes a replicated copy while FRS remains active.
• 2 — Redirected: SYSVOL replication switches to DFSR.
• 3 — Eliminated: FRS configuration for SYSVOL is removed.

Always wait until dfsrmig /getmigrationstate reports that all domain controllers have reached the current state before moving to the next one.

3. State 1 — Prepared

Move the domain to the Prepared state:

dfsrmig /setglobalstate 1

Then monitor progress:

dfsrmig /getmigrationstate

Do not continue until every domain controller reaches the Prepared state.

4. State 2 — Redirected

After all domain controllers are Prepared, redirect SYSVOL replication to DFSR:

dfsrmig /setglobalstate 2

Again, wait for convergence:

dfsrmig /getmigrationstate

At this stage, DFSR is responsible for SYSVOL replication.

5. State 3 — Eliminated

Only after the Redirected state is healthy on every domain controller should you move to the final state:

dfsrmig /setglobalstate 3

Important: The Eliminated state is irreversible. After the domain reaches state 3, SYSVOL cannot be rolled back to FRS by using DFSRMIG.

Confirm completion:

dfsrmig /getmigrationstate

6. Validate the Migration

After the migration completes, validate Active Directory and SYSVOL again:

dcdiag /e /c
repadmin /replsummary
net share
dfsrmig /getglobalstate
dfsrmig /getmigrationstate

The expected final global state is Eliminated, and all domain controllers should report that they reached the current migration state. SYSVOL and NETLOGON should remain shared on every domain controller.

7. Key Takeaways

• Check AD replication and SYSVOL health before starting.
• Move through Prepared, Redirected, and Eliminated one state at a time.
• Wait for every domain controller to converge before advancing.
• State 3 — Eliminated is irreversible.
• Domains still using FRS must migrate before adding modern domain controllers that no longer support FRS-based SYSVOL.

References

• Microsoft Learn – Migrate SYSVOL replication from FRS to DFS Replication
• Microsoft Learn – dfsrmig
• Microsoft Learn – SYSVOL DFSR migration and Windows Server 2019