Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Create and access a list of your products
Sign In Create an Account Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

Some article numbers may have changed. If this isn't what you're looking for, try searching all articles. Search articles

Windows server: How to Perform a Non-Authoritative Sync of SYSVOL Data Using the File Replication Service

Summary: This article illustrates the procedure for performing a non-authoritative sync of SYSVOL data on an Active Directory domain controller using the File Replication Service (FRS).

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Instructions

Important: This article is only applicable if SYSVOL data is being replicated using the File Replication Service (FRS). FRS has been deprecated but may still be in use in Active Directory domains that were created with functional levels earlier than Windows Server 2008. To determine whether FRS is in use, run the dfsrmig /getmigrationstate command at an elevated command prompt on a domain controller (DC). If the migration state is "Eliminated," FRS is not in use, and this article is not applicable.

The SYSVOL folder hierarchy, present on all DCs, is used to store two important sets of data:

  • Group Policy template files. These are stored in separate folders beneath \\SYSVOL\<domain>\Policies.
  • Logon, logoff, startup, and shutdown scripts used by machines in the domain. These are stored in \\SYSVOL\<domain>\scripts.
The scripts folder itself is shared as NETLOGON.


This data is replicated among DCs, but SYSVOL replication takes place separately from Active Directory replication. It is possible for one to fail while the other is fully functional. In some situations, SYSVOL replication may fail and be unable to resume without manual intervention. The following steps perform a non-authoritative sync of SYSVOL. In a non-authoritative sync, an affected DC copies all the SYSVOL data from another DC in the environment.

Important: If there is only one DC in the domain, a non-authoritative cannot succeed, since there is no other DC from which to copy SYSVOL data. In that situation, an authoritative sync should be performed instead. Instructions for performing an authoritative sync can be found in How to Perform an Authoritative Sync of SYSVOL Data Using the File Replication Service (FRS).

Before beginning this procedure, ensure that another DC exists in the environment and that its copy of the SYSVOL data is up to date. This requires browsing the SYSVOL folder hierarchy located by default at %systemroot%\SYSVOL to check the modified dates of Group Policy template files and script files.

To perform the non-authoritative sync of SYSVOL, follow these steps on the affected domain controller (that is, the DC with outdated or nonexistent SYSVOL data):

  1. Stop the File Replication Service.
  2. Launch Registry Editor.
  3. Browse to  HKLM\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup
  4. Double-click the BurFlags entry and set it to a hexadecimal value of D2.
  5. Start the File Replication Service.
  6. Launch Event Viewer and check the File Replication Service event log (located in Applications and Services Logs) for informational event 13516. It may take a few minutes for this event to appear.
  7. Once event 13516 has appeared, run the net share command and confirm the presence of the SYSVOL and NETLOGON shares in the output.
  8. You may also want to compare the data in the SYSVOL folder hierarchy of the affected DC to the corresponding data on a known good DC. They should now match.

The following video demonstrates the above procedure:

Non-Authoritative Sync of SYSVOL Data Using FRS

Duration: 07:51

Affected Products

Microsoft Windows Server 2016, Microsoft Windows Server 2019, Microsoft Windows Server 2022, Microsoft Windows 2008 Server R2, Microsoft Windows 2008 Server Service Pack 2, Microsoft Windows 2012 Server, Microsoft Windows 2012 Server R2

Products

PowerEdge XR2, Poweredge C4140, PowerEdge C6400, PowerEdge C6420, PowerEdge C6520, PowerEdge C6525, PowerEdge FC640, PowerEdge M640, PowerEdge M640 (for PE VRTX), PowerEdge MX5016s, PowerEdge MX7000, PowerEdge MX740C, PowerEdge MX750c , PowerEdge MX840C, PowerEdge R240, PowerEdge R250, PowerEdge R340, PowerEdge R350, PowerEdge R440, PowerEdge R450, PowerEdge R540, PowerEdge R550, PowerEdge R640, PowerEdge R6415, PowerEdge R650, PowerEdge R650xs, PowerEdge R6515, PowerEdge R6525, PowerEdge R740, PowerEdge R740XD, PowerEdge R740XD2, PowerEdge R7415, PowerEdge R7425, PowerEdge R750, PowerEdge R750XA, PowerEdge R750xs, PowerEdge R7515, PowerEdge R7525, PowerEdge R840, PowerEdge R940, PowerEdge R940xa, PowerEdge T140, PowerEdge T150, PowerEdge T340, PowerEdge T350, PowerEdge T40, PowerEdge T440, PowerEdge T550, PowerEdge T640, PowerEdge XE2420, PowerEdge XE7100, PowerEdge XE7420, PowerEdge XE7440, PowerEdge XE8545, PowerEdge XR11, PowerEdge XR12, PowerEdge XR4000r, PowerEdge XR4000w, PowerEdge XR4000z, PowerEdge XR4510c, PowerEdge XR4520c ...
Article Properties
Article Number: 000201393
Article Type: How To
Last Modified: 05 Dec 2024
Version:  8
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.