Filtered SYSVOL shows as inaccessible in GPMC status

When you examine group policy replication by using the Group Policy Management Console (GPMC) Infrastructure Status option that was first introduced in Windows Server 2012, you notice that all domain controllers report "replication in progress."

When you examine the SYSVOL share on domain controllers, you notice that ADM files are not present in SYSVOL except on the PDC emulator. Further examination shows that SYSVOL was previously configured by an administrator to filter out ADM files in order to minimize size.

GPMC Infrastructure Status does not examine files in SYSVOL by type or capability and does not follow customized FRS or DFSR filtering rules. Any file count, hash, or security differences in the SYSVOL Policies folder contents�between domain controllers are flagged as replication in progress.�

This behavior is by design. There are several ways to work around this behavior. In order of recommendation, they are as follows:

• Switch to modifying group policy from Windows Vista or later computers using a centralized ADMX store with filters. Delete the existing ADM files from SYSVOL
• Switch to modifying group policy from Windows Vista or later computers using�local copies of ADMX (default behavior). Delete the existing ADM files from SYSVOL
• Use an alternative tool to GPMC Infrastructure Status. Do not use gpotool.exe
• Remove the filters and allow ADMs to replicate to all domain controllers

ADM files are not used for group policy processing, unless you have created non-Microsoft custom ADM files. They are used only for editing and RSoP logging from Windows Server 2003 and Windows XP. These operating systems are in their extended support lifecycle. Windows Vista replaced this file type and added a centralized SYSVOL store in 2007.

GPMC Infrastructure Status does not examine folders outside the Policies folder contents, such as NETLOGON and the central ADMX store PolicyDefinitions.�

For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.