A. If you create a new Active Directory (AD) domain in Server 2008 mode, DFSR is used for SYSVOL replication. However, if you install a new domain in any mode besides Server 2008, or if you just upgrade, then NTFRS is used for SYSVOL replication, even if all servers are running Server 2008.

To migrate from NTFRS to DFSR, use the DFSRMIG utility provided with DFSR. Microsoft wrote this tool for the purpose of migrating all the domain controllers (DCs) within a domain from FRS to DFSR.

You run the tool in the following stages. The administrator sets the desired global stage.

0 'Start'
1 'Prepared'
2 'Redirected'
3 'Eliminated'

By default, your domain will be in Start mode. You can view the status of a DC by using the /GETGLOBALSTATE switch.

dfsrmig /getglobalstate

Current DFSR global state: 'Start'
Succeeded.

The /GETMIGRATIONSTATE switch will list any DCs whose local state doesn't match the global desired state.

dfsrmig /getmigrationstate

All Domain Controllers have migrated successfully to Global state ('Start').
Migration has reached a consistent state on all Domain Controllers.
Succeeded.

To set a new global stage for all DCs to attain, use the /SETGLOBALSTATE switch. The tool will work through all the stages to prepare a new DFSR set for SYSVOL, switch to DFSR as the primary , and retire the NTFRS replica set. I'll jump straight to stage 2. This stage sets the global state to “redirected.” It will take time for all DCs to achieve the new desired stage. You can run the /GETMIGRATIONSTATE switch to track migration progress.

dfsrmig /setglobalstate 2

Current DFSR global state: 'Start'
New DFSR global state: 'Redirected'

Migration will proceed to 'Prepared' state. DFSR service will copy the contents of SYSVOL to SYSVOL_DFSR folder. Migration will proceed to 'Redirected' state.

The SYSVOL share will be changed to SYSVOL_DFSR folder.

If any changes have been made to the SYSVOL share during the state transition from 'Prepared' to 'Redirected', please robocopy the changes from SYSVOL to SYSVOL_DFSR on any replicated RWDC.
Succeeded.

dfsrmig /getglobalstate

Current DFSR global state: 'Redirected'
Succeeded.

dfsrmig /getmigrationstate

The following Domain Controllers are not in sync with Global state ('Redirected'):

Domain Controller (Local Migration State) - DC Type
==============================================

SAVDALDC01 ('Start') - Primary DC
SAVDALDC02 ('Start') - Writable DC

Migration has not yet reached a consistent state on all Domain Controllers.

State information might be stale due to AD latency.

dfsrmig /getmigrationstate

The following Domain Controllers are not in sync with Global state ('Redirected'):

Domain Controller (Local Migration State) - DC Type
=========================================

SAVDALDC02 ('Waiting For Initial Sync') - Writable DC

Migration has not yet reached a consistent state on all Domain Controllers.
State information might be stale due to AD latency.

dfsrmig /getmigrationstate

All Domain Controllers have migrated successfully to Global state ('Redirected').
Migration has reached a consistent state on all Domain Controllers.
Succeeded.

When I want to remove the NT FRS I set the global state to 3 and wait for that change to take effect.

dfsrmig /setglobalstate 3

Current DFSR global state: 'Redirected'
New DFSR global state: 'Eliminated'

Migration will proceed to 'Eliminated' state. It is not possible to revert this step.

If any RODC is stuck in the 'Eliminating' state for too long then run with option /DeleteRoNtfrsMembers.
Succeeded.

dfsrmig /getmigrationstate

The following Domain Controllers are not in sync with Global state ('Eliminated'):

Domain Controller (Local Migration State) - DC Type

============================================== SAVDALDC01 ('Redirected') - Primary DC
SAVDALDC02 ('Redirected') - Writable DC

Migration has not yet reached a consistent state on all Domain Controllers.
State information might be stale due to AD latency.

dfsrmig /getmigrationstate

All Domain Controllers have migrated successfully to Global state ('Eliminated').
Migration has reached a consistent state on all Domain Controllers.
Succeeded.

At this point, you should be able to verify that the DCs are part of a new DFSR Domain System Volume replica group via the DFS Management snap-in.

If you run the NTFRSUTL SETS command, you'll see that the old SYSVOL share replica set is stopped.

ntfrsutl sets

ACTIVE REPLICA SETS
DOMAIN SYSTEM VOLUME (SYSVOL SHARE) in state STOPPED

DELETED REPLICA SETS

You are now a DFSR replica shop! The SYSVOL share now points to the SYSVOL_DFSR structure.