Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

SYSVOL Migration to DFRS

Primarily used to move from a Server 2008(R2) or 2012 environment to a Server 2016/2019 environment.

(1) Verify domain is 2008 or above

(2) Verify there are no replication issues using dcdiag

State 0: Start

dfsrmig /CreateGlobalObjects

Run commands below for each DC for verification:

dfsrdiag pollad /member:SERVERNAME

// replace SERVERNAME with name of server to be polled

Check the migration state of the server

dfsrmig /GetMigrationState

State 1: Preparation

dfsrmig /SetGlobalState 1

Replication can run on just the DFRS Global Settings

repadmin /replsingleobj * SERVERNAME "CN=DFSR-GlobalSettings,
CN=System,DC=NAME,DC=local (or TLD)"

Verify msDFR-Flags 16 is prepared

repadmin /showattr * "CN=DFSR-GlobalSettings,CN=System,DC=NAME,DC=local (or TLD)" 
/atts:msDFSR-Flags

If the above commands do not work, you can manually check using ADSI Edit

Run the command below on each DC to verify

Replicate from the DC, verify there are no errors

Check the migration state

NETLOGON and SYSVOL shares should still point to sysvol net share

State 2: Redirected

Run replication on just the DFRS Global Settings

Verfiy msDFR-Flags 32 is redirected

If the commands above do not work, you can manually check by using ADSI Edit

Run the command below to verify for each DC

Replicate from DC, verify there are no errors

Check the migration state

If the above commands do not work, you can manually check using ADSI Edit

State 3: Eliminated

This is irreversible - once you go to State 3, there is no going back!

Run the command below for each DC to verify

Replicate from DC, verify there are no errors

Check the migration state

NETLOGON and SYSVOL shares should now point to sysvol_dfsr, and the previous sysvol directory should be deleted.

Verify msDFR-Flags 48 is eliminated

PreviousRobocopyNextMoving Windows Recovery Partition

Last updated