Prices Excluding VATPrices Including VAT

Basket

How To

Guide to migrate FRS to DFSR using DFSRMIG

By August 14, 2019 No Comments

For many customers this text solely applies you probably have or have had a Window 2003/ 2003 R2 Domain Controller in your environment that you’re planning to get rid off. Fairly quickly I hope! 😉

SYSVOL is a folder shared by domain controller to hold its logon scripts, group policies and different items associated to AD. All of the domain controllers in the network will replicate the content of SYSVOL folder. The default path for SYSVOL folder is %SystemRoot%\SYSVOL. This folder path can be defined whilst you set up the active directory.

Windows Server 2003 and 2003 R2 makes use of File Replication Service (FRS) to duplicate SYSVOL folder content to different domain controllers. However Windows server 2008 and later makes use of Distributed File System (DFS) for the replication. DFS is more efficient than FRS. Since windows server 2003 has long gone out of support, most individuals already performed or still in search of migrate in to newest versions. Nonetheless migrating FSMO roles WILL NOT migrate SYSVOL replication from FRS to DFS. A lot of the engineers overlook this step when they migrate from windows 2003 to new versions.

For FRS to DFS migration we makes use of the Dfsrmig.exe utility. Extra information about it accessible on https://technet.microsoft.com/en-au/library/dd641227(v=ws.10).aspx

In my surroundings, I’m using windows server 2019 server and I migrating from a windows server 2008 R2 server. There was a windows 2003 server on the network and we have just decommissioned it.

In order to proceed with the migration forest function level should set to windows server 2008 or later. So in case your organisation not performed this yet, the first step is to get the forest and domain function level up to date.
You can confirm if the system makes use of the FRS using dfsrmig /getglobalstate , To do that:

1) Log in to domain controller as Domain admin or Enterprise Admin
2) Launch powershell console and type dfsrmig /getglobalstate. Output explains it’s not initiated DFRS migration but.

Before moving in to the configurations we’ll have to look into levels of the migration.

There are 4 stable states going together with the 4 migration phases.

1) State 0 – Start
2) State 1 – Prepared
3) State 2 – Redirected
4) State 3 – Eliminated

State 0 – Start

With initiating this state, FRS will replicate SYSVOL folder among the many domain controllers. It is very important have updated copy of SYSVOL before begins the migration process to keep away from any conflicts.

State 1 – Prepared

On this state while FRS continues replicating SYSVOL folder, DFSR will replicate a replica of SYSVOL folder. It will likely be positioned in %SystemRoot%\SYSVOL_DFRS by default. However this SYSVOL won’t response for some other domain controller service requests.

State 2 – Redirected

In this state the DFSR copy of SYSVOL begins to response for SYSVOL service requests. FRS will proceed the replication of its own SYSVOL copy, however it won’t be involved with the SYSVOL replication.

State 3 – Eliminated

In this state, DFS Replication will continue its replication and servicing SYSVOL requests. Windows will delete original SYSVOL folder users by FRS replication and cease the FRS replication.

In order to migrate from FRS to DFSR its must to go from State 1 to State 3. This step can’t be reversed.

Migration Steps:
Prepared State
1. Log in to domain controller as Domain admin or Enterprise Admin
2. Launch powershell console
3. Type dfsrmig /setglobalstate 1 and press enter

4. Type dfsrmig /getmigrationstate to verify all domain controllers have reached prepared state

Redirected State
1. Log in to domain controller as Domain admin or Enterprise Admin
2. Launch powershell console
3. Type dfsrmig /setglobalstate 2 and press enter

4. Type dfsrmig /getmigrationstate to verify all domain controllers have reached redirected state

Eliminated State
1. Log in to domain controller as Domain admin or Enterprise Admin
2. Launch powershell console
3. Type dfsrmig /setglobalstate 3 and press enter

4. Type dfsrmig /getmigrationstate to verify all domain controllers have reached eliminated state

This completes the migration process and to verify the SYSVOL share, type net share command and enter.

Additionally be certain in each domain controller FRS service is stopped and disabled. This could occur automatically, however please confirm.

Leave a Reply