Group Policy troubleshooting goes wrong when people start guessing. The setting is not applying, so someone forces a gpupdate, then reboots, then moves the computer to a different OU, and by the time the problem is solved nobody knows which change fixed it or whether it will come back.
There is a systematic order that works. It takes about ten minutes, it works for both computer and user settings, and it finds the cause rather than making the symptom go away.
Quick Facts
- Start with
gpresult /h report.htmlon the affected machine. It answers most questions in one file. - Policy applies in LSDOU order, Local, Site, Domain, OU, with the last one winning unless Enforced or Block Inheritance is in play.
- A GPO with only user settings linked to a computer OU does nothing, and vice versa. This is the most common cause by a distance.
- Security filtering needs read plus apply. Since the 2016 hardening change, computers also need read access through Authenticated Users or an explicit grant.
- If it applies on one DC and not another, suspect SYSVOL replication before anything else.
Step one. Get the report
Before touching anything, capture the current state from the machine that is misbehaving. Run this as an administrator on the affected computer, logged on as the affected user where the setting is user-side.
# Full HTML report, the single most useful command
gpresult /h C:\Temp\gpreport.html /f
# Computer settings only, when no user is available
gpresult /scope computer /h C:\Temp\gpcomputer.html /f
# Quick summary in the console
gpresult /r /scope computer
# From your own machine against a remote one
gpresult /s WKS041 /h C:\Temp\remote.html /f
Open the HTML file and go straight to the Denied GPOs section. It lists every policy that did not apply and gives a reason. Access Denied, Not Applied (Empty), Filtering: Not Applied. That reason is usually the whole answer.
Step two. Confirm the scope is right
More Group Policy problems come from scope than from anything else, and almost all of them are one of three things.
- The object is not in the linked OU. Check where the computer or user account actually lives, not where you think it lives. Security group membership is not the same as OU location.
- Computer settings in a GPO linked to a user OU. A policy containing only computer configuration linked to an OU holding users applies to nothing at all.
- The link is disabled, or the GPO has the relevant half of its configuration disabled in GPO Status. Both are easy to set accidentally and invisible unless you look.
In the Group Policy Management Console, the Scope tab of the GPO tells you every OU it is linked to and whether each link is enabled. The Details tab shows GPO Status. Check it says Enabled rather than User Configuration Settings Disabled.
Step three. Precedence and inheritance
Policy applies Local first, then Site, then Domain, then each OU from the top down. The last one to write a setting wins, which means the OU closest to the object normally takes precedence. Two things change that.
| Feature | What it does | Where it bites |
| Enforced | Makes a link win regardless of position | A domain-level enforced GPO overriding your carefully scoped OU policy |
| Block Inheritance | Stops policies from above applying to an OU | Everything domain-wide silently missing on one OU |
| Link order | Within one OU, lower number wins | Two GPOs setting the same thing, and nobody checked the order |
| Loopback processing | Applies user settings based on the computer | User settings appearing that are not linked to the user OU at all |
The Group Policy Inheritance tab on an OU shows the resulting order with everything accounted for. Read that rather than working it out yourself.
Step four. Filtering
Security filtering is the usual suspect. A GPO applies to an object only if that object has both Read and Apply Group Policy permissions. Since the security hardening changes in 2016, the computer account also needs Read, so if someone removed Authenticated Users from the Delegation tab without adding Domain Computers back, the policy will fail to apply even though the security filter looks correct.
WMI filtering is the quieter one. A WMI filter that returns false silently skips the GPO, and a filter written against an older Windows build often stops matching after an upgrade. Test the query directly on the affected machine.
# Test a WMI filter query on the affected machine
Get-CimInstance -Query "SELECT * FROM Win32_OperatingSystem WHERE Version LIKE '10.%'"
# Anything returned means the filter matches. No output means the GPO is skipped.
Step five. Replication and timing
If the policy works for some machines and not others, or worked yesterday and not today, look at replication before anything else. A GPO has two halves. The Group Policy Container in Active Directory and the Group Policy Template in SYSVOL, and they replicate by different mechanisms. If they get out of step, behaviour becomes inconsistent in exactly this way.
# Check for AD replication failures
repadmin /replsummary
repadmin /showrepl
# Check DFS Replication state for SYSVOL
Get-DfsrState -ComputerName dc01
dfsrdiag replicationstate /member:dc01
# Confirm version numbers match across domain controllers
Get-GPO -All | Select-Object DisplayName,@{n="AD";e={$_.User.DSVersion}},@{n="SYSVOL";e={$_.User.SysvolVersion}} | Where-Object {$_.AD -ne $_.SYSVOL}
That last command is worth keeping. Any GPO where the AD and SYSVOL version numbers differ is a replication problem, not a configuration problem, and no amount of scope checking will fix it.
The forced refresh, used properly
gpupdate /force is not a diagnostic. It reapplies everything rather than only what changed, which masks the difference between a policy that never applied and one that applied late. Use plain gpupdate when testing, and remember that some settings. Drive mappings, folder redirection, software installation. Only apply at logon or startup, so a refresh will never show them.
# Normal refresh, applies changed policy only
gpupdate
# Force reapplication of everything
gpupdate /force
# Refresh and log off so user settings that need logon apply
gpupdate /target:user /logoff
The event log, when the report is not enough
The Group Policy operational log holds the detail the report summarises. Open Event Viewer, Applications and Services Logs, Microsoft, Windows, GroupPolicy, Operational. Each policy processing cycle has a start and end event with a matching activity ID, and errors in between name the specific extension that failed.
Get-WinEvent -LogName "Microsoft-Windows-GroupPolicy/Operational" -MaxEvents 50 | Where-Object LevelDisplayName -ne "Information" | Format-Table TimeCreated,Id,Message -AutoSize -Wrap
Gear We Recommend
Managing a domain from a properly specified workstation makes all of this less painful. Here is our admin machine spec.
Browse our Admin Machine picks on AmazonAs an Amazon Associate, TechyGeeksHome earns from qualifying purchases
Glossary
| Term | What it means |
| GPO | Group Policy Object. A collection of settings applied to users or computers. |
| LSDOU | Local, Site, Domain, OU. The order in which policy is applied. |
| Security filtering | Restricting which objects a GPO applies to using permissions. |
| WMI filter | A query that must return true for the GPO to apply. |
| Enforced | A link setting that makes a GPO take precedence regardless of position. |
| Loopback processing | Applying user settings based on the computer being used. |
| SYSVOL | The replicated share holding the file-based part of every GPO. |
Frequently asked questions
Why is my GPO showing as Access Denied in gpresult?
The object lacks Read permission on the GPO. This usually follows someone editing security filtering and removing Authenticated Users without adding Domain Computers back, which the 2016 hardening change made necessary.
Why does my policy apply to some computers but not others?
Check SYSVOL replication first. Compare the AD and SYSVOL version numbers for the GPO across domain controllers. If they differ, the machines are getting different content depending on which DC they contacted.
Does gpupdate /force fix problems?
No, it reapplies everything, which can hide the real cause. Use plain gpupdate when diagnosing so you can tell the difference between a policy that never applied and one that simply had not refreshed yet.
Why do drive mappings not appear after a gpupdate?
Some extensions only process at logon or startup regardless of refresh. Drive maps, folder redirection and software installation are the common ones. Log off and back on to test them.
What does loopback processing actually do?
It applies user-side settings based on the computer the person is logged on to rather than where their account sits. It is the right answer for kiosks, terminal servers and shared machines, and a common surprise when someone else enabled it.
Disclosure: this post may contain affiliate links. If you buy through one of them, we may earn a small commission at no extra cost to you. We only recommend products we’ve tested or genuinely rate.
Discover more from TechyGeeksHome
Subscribe to get the latest posts sent to your email.