Migrating FRS to DFSR SYSVOL

As of June 20, 2017, the Windows RS1 system supports FRS for the last edition, and subsequent versions will no longer contain this feature, see details

Support.microsoft.com/en-us/help/4025991/windows-server-2016-rs3-no-longer-supports-frs

Introduction to Migration status

The migration process proceeds through a number of States, during which SYSVOL replication transitions from using File Rep Lication Service (FRS) to using distributed File System Replication (DFS Replication).

There are several states following the migration process from using FRS to SYSVOL replication using DFS:

Reference

Docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-r2-and-2008/dd641052%28v%3dws.10%29

State	Migration Process for SYSVOL Replication
Start (state 0)	FRS replicates the SYSVOL shared folder before the SYSVOL migration
Prepared (State 1)	FRS continues to replicate the SYSVOL shared folder used by the domain, and DFS Replication replicates the copy of the Sysvol folder. This copy of the Sysvol folder is not required to service requests from other domain controllers.
Redirected (state 2)	The DFS replica of the SYSVOL folder will be responsible for processing SYSVOL requests from other domain controllers. FRS continues to replicate the original SYSVOL folder, but DFS Replication now replicates the production SYSVOL folder using the domain controller in the redirected state.
Eliminated (State 3)	DFS Replication continues to process all SYSVOL replication. Windows deletes the original SYSVOL folder, and FRS no longer replicates the SYSVOL data.

Use the Dfsrmig command to migrate from the start state to the eliminated state, and roll back to the original state before changing to the eliminate State.

During the migration process, the status of each domain controller is as follows:

State number	Transition State Name
4	Preparing
5	Waiting for initial synchronization
6	Redirecting
7	Eliminating
8	Undo redirecting
9	Undo Preparing

Migration status

Large Circle Flag 4 migration status, Small circle indicates domain controller status

Fallback status

migrating to prepared status

Reference

Docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-r2-and-2008/dd639809%28v%3dws.10%29

Perform the following tasks when FRS continues to replicate the SYSVOL shared folder for the domain when it finishes, and DFS replicates a copy of the SYSVOL shared folder.

1. Verify the health of the domain Active Directory service

1) Execute the net share command on each domain controller to view the SYSVOL shared folder shared by the domain controller.

2) Confirm that disk space is sufficient to replicate a copy of the SYSVOL shared folder

3) Use Ultrasound diagnostic tool or manually verify the SYSVOL shared folder availability and FRS replicates the SYSVOL shared folder correctly

Ultrasound download

http://go.microsoft.com/fwlink/?LinkID=121859

Without ultrasound, refer to the following link and use the FRSDiag tool to check FRS replication blogs.technet.microsoft.com/askds/2008/05/22/ verifying-file-replication-during-the-windows-server-2008-dfsr-sysvol-migration-down-and-dirty-style/

4) Perform the repadmin/replsum command on one controller in the migrated domain (recommended on the PDC) to verify that Active Directory replication is working properly and that the command output should not contain errors

If replication displays errors

1. Check the replication status
Repadmin/showrepls
Repadmin/replsum
2. Force a copy
Repadmin/syncall/force
3.dcdiag/q Check the DC status

5) Use Registry Editor to view the SYSVOL for each controller's hkey_local_machine\system\currentcontrolset\services\netlogon\parameters registry Value Entry key value is [drive: \]windows_folder\sysvol\sysvol, and sysvolready Register list key value is 1

6) Each domain Controller view service in which DFS Replication is listed and has a status of started, the startup type is automatic.

Problems that you may encounter

• All files is conflicted on all domain controllers except the PDC Emulator when a DFSR migration of the SYSVOL share reach ES the redirected state in Windows Server, or in Windows Server R2

• DFSR SYSVOL fails to Migrate or Replicate, SYSVOL not shared, Event IDs 8028 or 6016

2. Raise the domain functional level to Windows Server 2008

* Requires that all domain controllers be at least Windows Server 2008.

* System upgrade does not automatically raise the domain functional level.

Query functionality on other domain controllers has been upgraded to Windows Server 2008

3. Backing up data for the SYSVOL shared folder

Back up[drive: \]windows_folder\sysvol\ directory to a different disk

4. Migrating domain to prepared state

After you start the migration, avoid modifying Group Policy and logon scripts until all domain controllers reach the redirected turntable. This ensures that the loss of the SYSVOL shared folder between migration States is temporarily unavailable, and client computers can also get the latest policies and scripts from the local cache

1) Perform a system state backup on all domain controllers using Wbadmin start systemstatebackup

2) Run the dfsrmig/setglobalstate 1 command on the PDC to migrate the domain to the prepared state

3) Wait for all controller status to prepared status, perform dfsrmig/getglobalstate view

The following output indicates that the migration status is prepared state

Current DFSR Global state: ' Prepared '
Succeeded.

4) Perform dfsrmig/getmigrationstate to confirm that all domain controllers are prepared state.

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

Because of the latency of the Active Directory and the amount of data, it can take some time.

5. Verify that the migration to prepared status is successful

1) Execute the net share command on each domain controller to confirm that all domain controllers in the domain SYSVOL shared folder still map to the FRS-replicated SYSVOL shared folder

2) Verify the SYSVOL shared folder availability using Ultrasound diagnostic tool or manually FRSDIAG and FRS replicates the SYSVOL shared folder correctly

3) Verify that the [drive: \]windows_folder\SYSVOL_DFSR folder has been created on each domain controller and verifythat [drive: \]Windows_ folder \sysvol folders were successfully copied to the[drive: \]windows_folder\SYSVOL_DFSR folder. The migration copy process will be includedin the [drive: \]windows_folder\sysvol folder and the Sysvol folder migrated to[drive: \]Windows_ Folder\SYSVOL_DFSR. This copy cadence takes a different amount of time depending on the size of the Sysvol folder.

4) Use DFS Management snap-in to create an analysis report of SYSVOL_DFSR files with Domain Admins administrator

Note: Periodically perform DFS Replication health reports and monitor DFS Replication event logs to monitor the status of DFS Replication to SYSVOL

Installing the Distributed File System Management component

Run the following command in the CMD window to perform the propagation replication test

DfsrAdmin Proptest new/rgname: "Domain System Volume"/rfname: "SYSVOL Share"/memname:hidtest\hidad01/domain:hidtest

Run the following command in the CMD window to generate the replication report

DfsrAdmin Proprep new/rgname: "Domain System Volume"/rfname: "SYSVOL Share"/memname:hidtest\hidad01/domain:hidtest/ Reportname:c:\preoprep.html

5) After confirming that the migration to prepared status is successful and that the SYSVOL folder replication status continues correctly, you can migrate the SYSVOL replication to the redirected state

Migrating to redirected status

Reference

Docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-r2-and-2008/dd641340%28v%3dws.10%29

In the redirected state, DFS Replication takes over the replication of the domain's primary SYSVOL folder, while FRS continuously replicates the SYSVOL folder

1. Performing dfsrmig/setglobalstate 2 on the PDC migrating the overall migration state to the redirected state

2. Perform dfsrmig/getglobalstate Verify that the overall migration status is redirected state, the following output indicates that the overall migration status is redirected state

Current DFSR Global state: ' Redirected '
Succeeded.

3. Perform dfsrmig/getmigrationstate to verify that all domain controllers reach the redirected state. The following output indicates that the migration status is redirected state

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

Because of the latency of the Active Directory and the amount of data, it can take some time.

4. Verify that the domain is migrated to the redirected state

1) Execute the net share command on each domain controller to confirm that all domain controller SYSVOL shared folders in the domain are mapped to the DFS replicated SYSVOL_DFSR folder, and the output is as follows:

2) Use DFS Management snap-in to create an analysis report of SYSVOL_DFSR files with Domain Admins administrator

3) Use the Ultrasound diagnostic tool or manually verify the SYSVOL shared folder availability and FRS replicates the SYSVOL shared folder correctly.

4) After confirming that the migration to redirected status is successful and that the SYSVOL folder replication status continues correctly, you can migrate the SYSVOL replication to the eliminated state

migrating to eliminated status

Reference

Docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-r2-and-2008/dd640254%28v%3dws.10%29

SYSVOL replication Migration final step migration to eliminated state, after migration is complete, all SYSVOL replication will take DFS Replication and cannot be rolled back to the previous state

1. Prepare to migrate to eliminated state

1) Log in to the PDC

2) Run dfsrmig/getmigrationstate to confirm that all domain controllers are redirected status, as follows:

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

3) Run repadmin/replsum confirm Active Directory copy is running normally without error output

4) Each domain controller runs Wbadmin start systemstatebackup Save System State

First BDC, then PDC

2. Migrating domain to eliminated state

1) Login PDC execution dfsrmig/setglobalstate 3 set domain migration status to eliminated

Note: You cannot revert to FRS replication after this step

2) Perform dfsrmig/getglobalstate Verify that the overall migration status is eliminated state, the following output indicates that the overall migration status is eliminated state

Current DFSR global state: ' Eliminated '
Succeeded.

3) Perform dfsrmig/getmigrationstate to verify that all domain controllers reach the eliminated state. The following output indicates that the migration status is eliminated state

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

Because of the latency of the Active Directory and the amount of data, it can take some time.

4) Execute the net share command on each domain controller to confirm that all domain controller SYSVOL shared folders in the domain are mapped to the DFS replicated SYSVOL_DFSR folder, and the output is as follows:

5) Use DFS Management snap-in to create an analysis report of SYSVOL_DFSR files with Domain Admins administrator

6) Confirm on each domain controller that the[drive: \]windows_folder\sysvol folder has been deleted if dfsrmig/setglobalstate 3 o'clock cmd or Windows window opens the folder, the folder exists but there is no file

7) After a period of time, each domain controller in the domain FRS service is stopped and disabled.

Migration rollback

Reference

Docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-r2-and-2008/dd640509%28v%3dws.10%29

A rollback operation can occur if a critical amount of the problem occurs before migrating to the eliminated state, or if you do not want to use DFS Replication.

Considerations for rolling back to a previous state

Although you can change the global migration state back and forth as needed before changing the global migration State to the eliminated state, you should wait for the domain controller to stabilize (its local state matches the global migration state) until you change the global migration state again.

When you roll back a migration, you can skip the steady state. For example, from the redirected state to the start state. The disadvantage of this approach is that you do not have the opportunity to troubleshoot problems in the intermediate stability state until the specified state has been reached.

Preparing to roll back to a previous state

1) Log on to the PDC

2) perform dfsrmig/getmigrationstate to verify that all domain controllers are in a consistent migration state. The following output indicates that the migration state is in a consistent migration state.

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

3) Execute the net share command on each domain controller to verify that all domain controllers in the domain SYSVOL shared folders.

If you want to roll back from redirected to a previous state, this folder needs to be mapped tothe [drive: \]windows_folder\sysvol_dfsr\sysvol folder of DFS Replication. The output looks like this:

If you want to return from the prepared state, this folder needs to be mappedto DFS Replication's [drive: \]windows_folder\SYSVOL\sysvol folder

4) Use the Ultrasound diagnostic tool or manually verify the SYSVOL shared folder availability and FRS replicates the SYSVOL shared folder correctly.
5) If you need to return the prepared state from the redirected state, use the DFS management snap-in to create an analysis report of the SYSVOL_DFSR folder administrator the domain administrator to confirm that the SYSVOL_DFSR folder is replicating properly

6) Run the SYSVOL_DFSR folder to confirm that the Active Directory is working properly and the output has no error

7) Confirm the Sysvolready under hkey_local_machine\system\currentcontrolset\services\netlogon\parameter in the Registry Editor the registry key value is 1.

In order to roll back from the redirected state to an earlier state, the SYSVO registry key under the same path has the Lkey value of [drive: \]windows_folder\sysvol_dfsr\sysvol

Rollback from prepared state, the key value should be [drive: \]windows_folder\SYSVOL\sysvol

8) Perform Wbadmin start systemstatebackup backup System State before performing a rollback

Rolling back migration status

1) Log in to the PDC

Returns the prepared state from the redirected state, performing Dfsrmig/setglobalstate 1.

Returns the start state from the prepared state, performing dfsrmig/setglobalstate 0.

2) Perform dfsrmig/getglobalstate Verify that the overall migration status is the previous state, the following output indicates the overall migration status

Current DFSR Global state: ' State '
Succeeded.

3) Perform dfsrmig/getmigrationstate to verify that all domain controllers reach the target state. The following output indicates that the migration status is the target migration state

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

Because of the latency of the Active Directory and the amount of data, it can take some time.

4) Execute the net share command on each domain controller to confirm that all domain controllers in the domain SYSVOL shared folders, which need to be mapped to FRS-replicated [drive: \]windows_folder\sysvol \sysvol folder

5) Use the Ultrasound diagnostic tool or manually verify the SYSVOL shared folder availability and FRS replicates the SYSVOL shared folder correctly.
6) If you need to return the prepared state from the redirected state, use the DFS management snap-in to create an analysis report of the SYSVOL_DFSR folder administrator the domain administrator to confirm that the SYSVOL_DFSR folder is replicating properly

7) Run the SYSVOL_DFSR folder to confirm that the Active Directory is working properly and the output has no error