Check Group Policy Infrastructure Status

项目
08/31/2016

Applies To: Windows Server 2012 R2, Windows Server 2012

Group Policy is a complicated infrastructure that allows you to apply policy settings to remotely configure computer and user experiences within a domain. Most of the troubleshooting advice comes to IT administrators when Group Policy fails to perform in the expected manner. But this advice does not scale well when you have thousands of Group Policy Objects (GPOs) that apply to thousands of computers and users.

In some cases, when you have a large enterprise spread over multiple countries and time zones, there could be a significant replication delay between domain controllers. GPO mismatches in version numbers between the Group Policy container and the Group Policy template, or GPO mismatches between different domain controllers, can be expected due to a delay in replication. They can also indicate an issue with Group Policy. In previous versions of Windows, there were tools (such as GPOTool.exe) to provide a view of the GPO replication, but they provided inconsistent information.

In Windows Server 2012, the Group Policy Management Console (GPMC) was enhanced to provide a report for the overall health state of the Group Policy infrastructure for a domain, or to scope the health view to a single GPO.

The GPMC domain status tab (added in Windows Server 2012) displays individual pieces of information that indicate the health of the Group Policy infrastructure with regards to domain controllers, GPO replication, and GPO versioning. This Group Policy infrastructure health status can help you find inconsistencies and anticipate issues.

In this document

We will look at what makes up a GPO and where the parts of the GPO are stored in a domain-based environment. Then we will look at how to use the Group Policy infrastructure health status information to monitor for issues with GPO replication and what to do for further investigation of replication issues.

Prerequisites

You can run Group Policy infrastructure health checks only by using the GPMC from domain-joined computers running:

Windows Server 2012 or Windows Server 2012 R2
Windows 8 or Windows 8.1 with Remote Server Administration Tools for Windows 8

An understanding of how GPOs are stored in a domain will help you make full use of the data that is displayed on the infrastructure status page.

In a domain that contains more than one domain controller, Group Policy information takes time to propagate or replicate from one domain controller to another. Low-bandwidth network connections between domain controllers slow replication. The Group Policy infrastructure has mechanisms to manage these issues.

Each GPO is stored partly in Active Directory and partly in SYSVOL on the domain controller. The portion of the GPO that is stored in Active Directory is called the Group Policy container, and the portion of the GPO that is stored in SYSVOL is called the Group Policy template. The GPMC and Group Policy Management Editor manage the GPO as a single unit. For example, when you set permissions on a GPO in the GPMC, the GPMC is actually setting permissions for objects in Active Directory and in SYSVOL. It is not recommended that you manipulate these separate objects independently outside of the GPMC and the Group Policy Management Editor. It is important to understand that these two separate features of a GPO rely on different replication mechanisms. The file system portion, Group Policy template, is replicated through Distributed File Service Replication (DFS-R) or File Replication Service (FRS), independently of the replication that is handled by Active Directory in the Group Policy container.

Temporary lack of synchronization can occur between the GPO data that is stored in Active Directory (Group Policy container) and the GPO data that is stored on SYSVOL (Group Policy template). This is due to the differences in the replication schemes used by Active Directory and DFS-R or FRS.

Group Policy provides a framework that extends Group Policy management to more features. These components are referred to as Group Policy snap-ins or extensions. For those Group Policy extensions that store data in only one data store (Active Directory or SYSVOL), this is not an issue, and Group Policy is applied as it is read. Such extensions include administrative templates, scripts, folder redirection, and most of the security settings.

For any Group Policy extension that stores data in Active Directory and SYSVOL, the extension must properly handle the possibility that the data is unsynchronized. This is also true for extensions that need multiple objects in a single store to be atomic in nature, because neither storage location handles transactions.

An example of an extension that stores data in Active Directory and SYSVOL is Software Installation. The script files are stored in SYSVOL, and the Windows Installer package definition is stored in Active Directory. If a script exists, but the corresponding Active Directory features are not present, nothing happens. If a script file is missing, but the package is known in Active Directory, application installation fails gracefully and retries on the next processing of Group Policy.

The tools used to manage Active Directory and Group Policy (such as GPMC, the Group Policy Object Editor, and Active Directory Users and Computers) communicate through domain controllers. If there are several domain controllers available, changes to objects (including users, computers, organizational units, and GPOs) may take time to appear on other domain controllers. The administrator may see different data depending on the last domain controller on which the changes were made and on which domain controller they are currently viewing the data.

Ideally, you would like to proactively check to make sure that all your GPOs within a domain are consistent. In the past, GPOTool.exe was used for this check. However, GPOTool.exe is limited to checking the values in the GPT.ini file, which only indicates if the versions in the Group Policy container and the Group Policy template on each domain controller are in sync.

In Windows Server 2012 and Windows Server 2012 R2, the GPMC contains a more comprehensive replication check than what was previously done with GPOTool.exe.

Step 1: Check Group Policy infrastructure health

Windows Server 2012 includes a graphical reporting feature in the GPMC that enables you to choose a baseline domain controller for comparison. You can see the current Group Policy replication status with synchronization details when a comparison finds a differential from the baseline domain controller.

Important

You can only run the Group Policy infrastructure status report from the GPMC. You cannot schedule this report, and there is no Windows PowerShell or other command-line equivalent. The report does not persist between GPMC sessions. Do not close the GPMC until the report gathering process has completed to avoid losing the report information.

To create and analyze an infrastructure status report

Run an infrastructure status report for a domain or for a GPO:
1. For an entire domain In the GPMC console tree, click the name of the domain for which you want to check the replication status of all the GPOs.
2. For a single GPO In the GPMC console tree, navigate to the Group Policy Objects container. Expand the Group Policy Objects container and click the GPO for which you want to check the replication status.
Click the Status tab in the results pane.
Click the Detect Now button to gather infrastructure status from all of the domain controllers in this domain.

Step 2: Check the results of the Group Policy infrastructure status report

To validate consistency between the baseline and each domain controller, the GPMC compares the Group Policy information that is stored in Active Directory (Group Policy container), and it separately compares the Group Policy information that is stored in SYSVOL (Group Policy template) on all the domain controllers in the selected domain.

Here is a list of comparisons that are performed:

ACL for each Group Policy container
Version number attribute on each Group Policy template
Count of Group Policy container objects
ACL on each Group Policy template
Version number stored in the gpt.ini file in each Group Policy container
Count of Group Policy template folders and files
File hash for each file in Group Policy template folders

During the Group Policy infrastructure status report gathering process, if the GPMC cannot contact a domain controller, or if a domain controller is found to not be consistent with the baseline domain controller, the domain controller in question is added to the Domain controller(s) with replication in progress list.

To verify GPO replication consistency for all domain controllers

When the infrastructure status report gathering process is complete, click the Status tab, and in the Status Details section, verify that there are no domain controllers listed in the Domain controller(s) with replication in progress list.
Group Policy application requires clients to access specified servers, including domain controllers and other servers, such as those used for sharing documents and as installation points. Group Policy management also requires access to domain controllers.

If a domain controller is listed as Inaccessible in the Domain controller(s) with replication in progress section of the Status Details, check the following:
1. The domain controller is working and accessible on the network.
2. The event logs and operation logs of the domain controller do not report any errors that would cause the server to not respond to network requests.
3. SYSVOL and Active Directory are available from the domain controller that is listed as inaccessible.
If a domain controller is listed in Domain controller(s) with replication in progress due to inconsistencies in the Group Policy container portion of the GPO, see Step 3: Check Active Directory replication issues
If a domain controller is listed in Domain controller(s) with replication in progress due to inconsistencies in the Group Policy template portion of the GPO, see Step 4: Check file services replication issues

Step 3: Check Active Directory replication issues

Inbound or outbound replication failure can cause Active Directory objects that represent the replication topology, replication schedule, domain controllers, users, computers, passwords, security groups, group memberships, and Group Policy to be inconsistent between domain controllers.

If you suspect that you have an issue with Active Directory replication, see the following resources to understand how these mechanisms work and how you can troubleshoot issues:

Step 4: Check file services replication issues

The Group Policy template portion of Group Policy resides in SYSVOL. Group Policy depends on SYSVOL replication working correctly for the Group Policy template to remain consistent between domain controllers within a domain. SYSVOL replication depends on the Distributed File System Replication (DFS-R) or the File Replication Service (FSR), depending on how you have configured your domain controllers.

If you suspect that you have an issue with SYSVOL replication, see the following resources to understand how these mechanisms work and how you can troubleshoot issues:

通过