Sysvol migration - Migrating to the ‘ELIMINATED’ state

I was recently working with a customer helping them migrate to the Eliminated state of Sysvol migration so I thought to highlight the steps that we took for this migration.

Before the migration, we verified:

- All domain controllers are in the Redirected state. Run dfsrmig /getmigrationstate against each domain controller in the domain to verify this. It is very important step

- Run net share to verify the Sysvol share. Confirm that Sysvol share is still being shared out by all domain controllers and that the Sysvol share path points to the path that is being replicated by the DFS Replication service

- Verify Active directory replication. You can check this by running the command repadmin /replsum.

Once the prerequisites are verified, you can run the below command on the PDC Emulator to migration Sysvol to Eliminated state:

dfsrmig /setGlobalState 3

Use dfsrmig /getMigrationState’ to confirm that each domain controller has reached the Eliminated state. When the DFS Replication service on each domain controller reaches the ‘ELIMINATED’ state, Information event 8019 will be registered in the event log.

Read my favorites blogs:

Assigning File Share permissions using Power Shell

Disk Read Error when migrating virtual machine from one cluster to another

Designing a backup less Exchange 2010 Architecture

Appear Offline in Microsoft Office Communicator Server 2007

Microsoft Exchange 2010 Test cases

Microsoft Exchange 2013 and ADRMS Integration