Shulou(Shulou.com)06/03 Report--

Suppose you try to upgrade an Active Directory domain controller (DC) running on a previous version of Windows Server to Windows Server 2019. You may see the following error:

"replica verification failed. The specified domain [DomainName] is still using the File replication Service (FRS) to replicate SYSVOL shares. FRS has been deprecated."

The SYSVOL folder of the DC domain control C drive is used to copy login scripts and group policy files to other DC domain controllers. The old version of Windows Server (2000 amp 2003) used FRS replication to synchronize SYSVOL. Starting with Windows Server 2008, Microsoft decided to use distributed file system replication (DFSR), such as domain functional level (DFL) set to Windows Server 2008, and domain replication SYSVOL folders replicated through DFST. However, if the customer does not upgrade DFL to at least the Windows Server 2008 domain functional level, replication between DC domain controls still uses the old FRS to replicate SYSVOL

Compared with FRS, DFSR is more reliable and scalable. It solves several problems that have existed in FRS for many years. What should we do if you want to use DFSR? You can migrate FRS replication to DFSR, or you can create a new domain with DFL at least at the Windows Server 2008 domain functional level.

As you can see in the error message above, because FRS has been deprecated, you must configure the domain to migrate from FRS to DFSR.

There are usually three ways to migrate:

Quick Migration (AD domain status unknown, rollback operation)

Express Migration (AD domain status is healthy, rollback operation)

Hyper Migration (AD domain status is healthy and cannot be rolled back)

We can use Quick Migration when we don't know the health status of all DC domain controllers, AD and SYSVOL. If you know the health and status of the AD environment, you can use "Express Migration" or "Hyper Migration". The only difference between the two is whether you want to be able to roll back. Express Migration will allow you to roll back and encounter a failed Active Directory in case a problem occurs.

FRS to DFSR migration time

In applying the changes, many customers are worried about the migration time. In my experience, this process is relatively simple. On smaller networks with less than five DC domain controls, the migration takes about 5 minutes to complete. On larger networks, it may take longer, ranging from a few hours to several hours. In rare cases, it may even take a few days. It is recommended to evaluate the migration plan in advance before migration.

SYSVOL folder permissions

After the migration is complete, you may see the following notification when you open the Group Policy Management console.

Prompt that the permissions of the GPO policy in the SYSVOL folder are not consistent with the permissions in Active Directory. To change SYSVOL permissions to Active Directory permissions, click OK.

There is a certain risk in any change. It is recommended that you back up the AD domain control and read the Migration Guide wizard before migrating from FRS to DFSR.

SYSVOL Replication Migration Guide: FRS to DFS Replication Migration Wizard

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.