Group Policy Not Applying: Diagnosis with gpresult and Event Logs

If a GPO doesn’t reach the client, rule out scope, filters, precedence, loopback and SYSVOL in order; find the root cause with gpresult and event IDs.
Technical summary
Technology
Group Policy, GPMC, gpresult, RSoP, DFSR, Windows Event Log
Topic
Diagnosing a GPO not applying on the client
Level
Intermediate
Prerequisites
  • Knowledge of Active Directory and OU structure
  • Using GPMC
  • Local administrator rights
In this article9 sections

When a “the GPO isn’t coming through” complaint arrives, the first reflex is to run gpupdate /force and wait. Most of the time nothing changes, because the cause is a wrong OU, a filter, a precedence conflict, an unreachable SYSVOL or the client never processing the GPO. The order below rules out these possibilities from the cheapest check to the most expensive; for each step we note what each tool shows and what each event entry points to.

Processing order and precedence

Before starting diagnosis, be clear about how the winner is determined. Group Policy is processed in this order: local policy, site, domain, OU (from parent OU to child OU). If the same setting is defined in more than one GPO, the last one processed wins; so the GPO in the OU closest to the object usually comes out on top.

  • Link order: Among GPOs linked to the same container, Link Order 1 has the highest precedence; it is processed last.
  • Enforced: An enforced link wins over conflicting settings in child OUs and can’t be cut off by Block Inheritance.
  • Block Inheritance: Cuts off non-enforced GPOs coming from above to the OU. It is a common cause of the “the domain policy doesn’t reach us” complaint; often someone turned it on years ago and forgot.
  • Loopback: This setting, enabled in a computer GPO, determines user settings based on the computer’s OU rather than the user’s. In Merge mode the two lists are combined and the computer side wins; in Replace mode the user settings in the user’s own OU aren’t processed at all.

Background refresh is by default 90 minutes plus a random 0–30 minute delay on member computers, and 5 minutes on DCs. Security settings are reapplied every 16 hours even if nothing changed. So “I just changed the setting and it didn’t come through” is often just a matter of waiting.

A good share of problems are solved at the first step, without going deep into the system infrastructure. Select the GPO in GPMC and look at the Scope tab and the relevant object:

  • Is the computer or user really under the OU the GPO is linked to? The default CN=Computers and CN=Users are containers, not OUs; GPOs can’t be linked to them. This is the common mistake: a machine newly joined to the domain stays in the Computers container and no OU GPO reaches it. Redirect the default location to an OU with redircmp.
  • Is the link enabled (Link Enabled)? A disabled link turns off the GPO completely.
  • Is the GPO Status “User configuration settings disabled” or “Computer configuration settings disabled”? Settings defined in a disabled half are ignored.
  • Is the setting in the right half? A setting in user configuration, if linked to an OU containing computer objects, doesn’t reach the user without loopback.

Security and WMI filters

For the GPO to apply, the target object must have Read and Apply group policy permissions on the GPO. Since the MS16-072 update in 2016, user GPOs are read in the security context of the computer account. If you remove Authenticated Users from Security Filtering and add only a user group, you must give Domain Computers (or Authenticated Users) Read permission on the Delegation tab. If you don’t, the GPO is silently skipped. It shows up as access denied in the gpresult report.

WMI filters are evaluated on the client; if the result is false, the GPO isn’t applied. The filter below selects only client operating systems (ProductType 1 is client, 2 DC, 3 member server):

SELECT * FROM Win32_OperatingSystem WHERE ProductType = "1"

A wrong namespace, a typo or a corrupt WMI repository on the client makes the filter return false every time. Test the filter directly on the problem machine:

Get-CimInstance -Query 'SELECT * FROM Win32_OperatingSystem WHERE ProductType = "1"'

If the result is empty, the filter is evaluated incorrectly on that machine. If you use Group Policy Preferences, item-level targeting is a separate filter layer: the GPO appears applied, but the preference item was blocked by the targeting condition. A GPO showing green in the report doesn’t mean the setting arrived.

Analysis with gpresult and RSoP

The basic tool for seeing the resultant set of policy (RSoP) is gpresult; all parameters are listed in the gpresult command reference. To see computer data, open the command prompt as administrator:

gpresult /r /scope computer
gpresult /h C:\Temp\gp-report.html /f
gpresult /s PC-0412 /user CONTOSO\ayse.k /h C:\Temp\pc0412.html

In the HTML report, look at three sections: Applied GPOs, Denied GPOs (with the reason: “Empty”, “Access Denied (Security Filtering)”, “False WMI Filter”, “Disabled Link”) and Component Status (the result of the last run of each client-side extension). The Winning GPO column, which shows which GPO a setting came from, directly reveals a precedence conflict. This is the column that ends the debate.

You can get the same report for a remote machine with PowerShell:

Get-GPResultantSetOfPolicy -Computer PC-0412 -User CONTOSO\ayse.k `
  -ReportType Html -Path C:\Temp\rsop-pc0412.html

Invoke-GPUpdate -Computer PC-0412 -Force -RandomDelayInMinutes 0

If you suspect the change hasn’t propagated yet, run the “what would happen if this user signed in on this computer” scenario with the Group Policy Modeling wizard in GPMC. Modeling is calculated on the DC; if it differs from the actual result (Results), the problem is on the client side.

The GroupPolicy Operational log

gpresult shows the result; the event log shows the reason. The relevant log is under Applications and Services Logs > Microsoft > Windows > GroupPolicy > Operational. Each processing cycle is marked with the same Activity ID; filter all entries for a cycle by this ID and read them together.

Event ID Meaning
4000 / 4001 Computer startup / user sign-in processing started
4006 / 4007 Computer / user background processing started
5308 / 5326 DC used / DC discovery time
5314 Link speed estimate (slow link detection)
5312 / 5313 List of GPOs to apply / those filtered out
8000 / 8001 Startup / sign-in processing completed, and its duration

Errors also land in the System log with the GroupPolicy source. Common ones: 1058 (couldn’t access the gpt.ini file; usually SYSVOL or DNS), 1030 (couldn’t query the GPO list), 1129 (processing failed because there was no network connection to the DC) and 1085 (a specific client-side extension failed). To see the errors of the last hour together:

Get-WinEvent -FilterHashtable @{LogName='System'; ProviderName='Microsoft-Windows-GroupPolicy'; Level=2,3; StartTime=(Get-Date).AddHours(-1)} |
  Select-Object TimeCreated, Id, Message | Format-List

If the log isn’t enough, turn on detailed debug logging: under HKLM\Software\Microsoft\Windows NT\CurrentVersion\Diagnostics, set a DWORD value named GPSvcDebugLevel to 0x30002; output is written to the %windir%\debug\usermode\gpsvc.log file. Remove the value when done; debug logging left on fills the disk.

Problems caused by SYSVOL and replication

A GPO consists of two parts: the Group Policy Container (GPC) in Active Directory and the Group Policy Template (GPT) in SYSVOL. If their version numbers differ between DCs, the client gets old or missing settings depending on the DC it connects to. Typical symptom: the problem occurs only at a particular site or on clients connecting to a particular DC. The same GPO behaves differently in two offices.

  • In GPMC, select the domain and compare GPC/GPT consistency across all DCs with Detect Now on the Status tab.
  • Verify the SYSVOL replication mechanism: the dfsrmig /getglobalstate output should be “Eliminated.” If FRS is still in use, that is a migration debt that needs to be closed separately.
  • Check the DFSR backlog; look for entries 2213 (replication stopped after a dirty shutdown) or 4012 (disconnected for too long) in the DFS Replication log.
Get-DfsrBacklog -GroupName "Domain System Volume" -FolderName "SYSVOL Share" `
  -SourceComputerName DC01 -DestinationComputerName DC02 -Verbose
repadmin /replsummary

To monitor the general health of domain controllers as part of scheduled maintenance, use the steps in the Active Directory health check article; they catch these problems before users call.

If the client measures the link to the DC below the default 500 kbps threshold, it treats it as a slow link. Registry-based policies and security settings are still applied; software installation, folder redirection and some script extensions may be skipped. This is often the cause of the “drive mapping sometimes doesn’t come through” complaint from VPN users. Event 5314 shows the measured speed.

Some extensions run only at startup and sign-in, i.e. in the foreground. For fast logon, Windows opens the desktop without waiting for the network; if you want these extensions applied at first sign-in, enable the Always wait for the network at computer startup and logon setting. Sign-in time gets longer. That’s why you should give this setting only to the computer groups that need it.

From symptom to cause: check table

Symptom Likely cause Check
GPO not in the report at all Object in the wrong OU, link disabled GPMC Scope, location in ADUC
Denied: Access Denied Security filtering, missing Read permission Delegation tab
Denied: False WMI Filter Filter query or WMI repository Get-CimInstance test
Applied, but the setting is different Precedence conflict, loopback Winning GPO column
Problem at only one site SYSVOL/AD replication Detect Now, Get-DfsrBacklog
1058/1129 in the System log DNS or DC access nltest /dsgetdc, DNS setting
Some settings missing over VPN Slow link detection Event 5314

Following the table from top to bottom gives results faster than running gpupdate over and over and waiting. If the same kind of GPO problem keeps recurring, the issue isn’t a single setting but the OU design and the number of GPOs; we handle regular maintenance of the Group Policy structure within our server and cloud management service. If the problem started after a DC replacement, also see the checks in the domain controller replacement and FSMO transfer article.

Frequently asked questions

What should I do if running gpupdate /force doesn’t fix the problem?

gpupdate only re-triggers processing; if the GPO is out of scope or blocked by a filter, the result won’t change. First check in the gpresult /h report whether the GPO is in the applied or the denied list, then read the error entries in the GroupPolicy Operational log.

Why don’t computer settings appear in the gpresult report?

When gpresult doesn’t run with administrator rights, it can’t show computer-scope data. Open the command prompt as administrator or get the report again with the /scope computer parameter.

Why are some settings applied only at restart or sign-in?

Extensions such as software installation and folder redirection don’t run during background refresh; they need foreground processing. These settings are applied at the next boot or sign-in; because of the fast logon optimization, two boots are sometimes needed.

Why did the GPO stop working after removing Authenticated Users from security filtering?

The computer account also needs Read permission to be able to read the GPO. If you removed Authenticated Users, give the Domain Computers group Read permission only, from the Delegation tab; the Apply permission can stay with the user group.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek System Support

Server installation, configuration, incident response and scheduled maintenance. Active Directory, virtualization and backup are managed with the same discipline.

Knowledge Center

Other articles