GPMC Infrastructure Status replication in progress, missing ADM files
Content provided by Microsoft
Applies to: Windows Server 2012 DatacenterWindows Server 2012 DatacenterWindows Server 2012 StandardWindows Server 2012 StandardWindows 8Windows 8 EnterpriseWindows 8 ProMore
When you examine Group Policy replication by using the Group Policy Management Console (GPMC) Infrastructure Status option that was introduced in Windows Server 2012, you notice that all domain controllers report "replication in progress." Additionally, when you examine the SYSVOL share on the domain controllers, you notice that administrative template (ADM) files are not present in SYSVOL except on the primary domain controller (PDC) emulator.
By following KB 813338 you see that SYSVOL was previously configured by an administrator to filter out ADM files in order to minimize size.
The GPMC Infrastructure Status option does not examine files in SYSVOL by type or capability and does not follow customized File Replication Service (FRS) or Distributed File Service Replication (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 descending order of recommendation, they are as follows:
Use a monitoring solution, such as System Center Operations Manager, to ensure group policy is synchronized
Manage Group Policy from computers that are running Windows Vista or a later version of Windows by using a centralized ADMX store together with filters. This will prevent further ADM creation. Delete the existing ADM files from SYSVOL.
Manage Group Policy from computers that are running Windows Vista or a later version of Windows by using local copies of ADMX. (This is the default behavior). This will prevent further ADM creation. Delete the existing ADM files from SYSVOL.
Use a third party tool to examine group policy synchronization.
Remove the filters, and let ADM files replicate to all domain controllers.
ADM files are not used for Group Policy processing unless you 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 life cycle. This file type was replaced in Windows Vista, and a centralized SYSVOL store was added in 2007.
The GPMC Infrastructure Status option does not examine folders outside the Policies folder contents. For example, it does not examine NETLOGON or the central ADMX store PolicyDefinitions folder.
Do not use Group Policy Verification Tool (gpotool.exe). This tool incorrectly checks group policy file synchronization and is not supported on Windows Server 2008 and later operating systems.
For more information on the workarounds and behaviors, click the following article numbers to view the articles in the Microsoft Knowledge Base:
929841 How to create the Central Store for Group Policy Administrative Template files in Windows Vista
813338 How to minimize SYSVOL size by removing administrative templates (.adm files)