The same Group Policy applies to some computers but not others: a complete troubleshooting sequence
When a GPO applies inconsistently, compare OUs, policy versions, security and WMI filters, DNS, SYSVOL, client results, and events instead of relying on gpupdate alone.

Establish a factual baseline with “OU placement and inheritance chain” and “security filtering and deny permissions”, then move to “WMI filtering”. Use identity, name resolution, replication and policy as the evidence chain and avoid changing production before the fault boundary is clear.
Risk boundaries and prerequisites
Start by checking OU placement and inheritance chain, security filtering and deny permissions and WMI filtering independently. A healthy result for one of these checks does not establish the state of the entire service path.
Evidence and safe checks
| Check | Why it matters | Recommended action |
|---|---|---|
| 01 · OU placement and inheritance chain | Checking OU placement and inheritance chain helps establish whether the directory, name resolution and policy state are consistent; compare it with a known-good baseline and the incident timeline. | Record the actual state of OU placement and inheritance chain. Capture read-only results from the affected controllers and clients. Compare objects, DNS records, policy versions and events before making changes. |
| 02 · security filtering and deny permissions | Checking security filtering and deny permissions helps establish whether the directory, name resolution and policy state are consistent; compare it with a known-good baseline and the incident timeline. | Record the actual state of security filtering and deny permissions. Capture read-only results from the affected controllers and clients. Compare objects, DNS records, policy versions and events before making changes. |
| 03 · WMI filtering | Checking WMI filtering helps establish whether the directory, name resolution and policy state are consistent; compare it with a known-good baseline and the incident timeline. | Record the actual state of WMI filtering. Capture read-only results from the affected controllers and clients. Compare objects, DNS records, policy versions and events before making changes. |
| 04 · GPO versions and SYSVOL | Checking GPO versions and SYSVOL helps establish whether the directory, name resolution and policy state are consistent; compare it with a known-good baseline and the incident timeline. | Record the actual state of GPO versions and SYSVOL. Capture read-only results from the affected controllers and clients. Compare objects, DNS records, policy versions and events before making changes. |
| 05 · actual gpresult/RSOP result | Checking actual gpresult/RSOP result helps establish whether the directory, name resolution and policy state are consistent; compare it with a known-good baseline and the incident timeline. | Record the actual state of actual gpresult/RSOP result. Capture read-only results from the affected controllers and clients. Compare objects, DNS records, policy versions and events before making changes. |
| 06 · GroupPolicy event log | Checking GroupPolicy event log helps establish whether the directory, name resolution and policy state are consistent; compare it with a known-good baseline and the incident timeline. | Record the actual state of GroupPolicy event log. Capture read-only results from the affected controllers and clients. Compare objects, DNS records, policy versions and events before making changes. |
gpresult /h C:\Temp\gpresult.html
gpupdate /forceInvestigation and change sequence
- Capture a baseline for OU placement and inheritance chain and security filtering and deny permissions and compare it with a known-good system.
- Correlate evidence from WMI filtering and GPO versions and SYSVOL to distinguish the direct fault from dependent symptoms.
- Only if evidence points to actual gpresult/RSOP result, plan a controlled change with backups, a change window and rollback triggers.
- Finally check GroupPolicy event log and the real business workflow. Retest representative user sign-in, domain discovery, Group Policy or cross-domain access and confirm replication and event health.
Validation and rollback evidence
- Retest representative user sign-in, domain discovery, Group Policy or cross-domain access and confirm replication and event health.
- Recheck actual gpresult/RSOP result and GroupPolicy event log against the expected business outcome.
- Retain initial configuration, event evidence, validation results and rollback triggers for production changes.
Common actions that increase risk
- Assuming OU placement and inheritance chain is sufficient while overlooking security filtering and deny permissions and dependent checks.
- Changing several settings before preserving the original evidence for WMI filtering.
- Do not replace root-cause analysis with destructive directory operations or forced rebuilds.
Common questions and acceptance criteria
What should be checked first?
Begin with OU placement and inheritance chain and security filtering and deny permissions. Capture reproducible errors and protect recoverable data before changing production.
What proves the issue is resolved?
Retest representative user sign-in, domain discovery, Group Policy or cross-domain access and confirm replication and event health.
What evidence should be retained?
Retain original logs, configuration snapshots, the approved change scope, business verification and rollback conditions.
