GPO Not Applying to Computer? Full Troubleshooting Guide
GPO not applied after applying policy
L2 Level: If a newly created policy isn't applying as expected,
several troubleshooting steps can be taken. First, verify the policy is
correctly assigned and that the targeted users or computers are indeed members
of the relevant groups. Additionally, ensure there are no conflicts with other
policies or misconfigured permissions. If needed, force a Group Policy update
using gpupdate /force or restart affected machines.
Here's a more detailed breakdown:
1. Verify Policy Assignment and Target Groups:
- Check
Policy Assignments:
Ensure the policy is assigned to the correct security group (e.g., SG1) using the appropriate command (e.g., Grant-CsExternalAccessPolicy). - Confirm
Group Membership:
Verify that the intended users or computers are actual members of the group to which the policy is assigned. - Examine
Policy Scope:
Double-check that the policy's scope (e.g., OU, domain, specific computers) is correctly configured.
2. Resolve Conflicts and Permissions:
- Check
for Conflicts:
Policies might conflict if they set conflicting settings. Review the policies for any potential overlaps. - Examine
Permissions:
Review the delegation tab to ensure that the appropriate users/groups have the necessary permissions to apply the policy (e.g., "Read" and "Apply Policies" permissions for Authenticated Users). - Verify
DNS and Sysvol:
Ensure DNS resolution and access to the SYSVOL and NETLOGON shares are functioning correctly.
3. Force Group Policy Updates and Reboot:
- Run
gpupdate /force:
Use the gpupdate /force command in an elevated command prompt to force a Group Policy update on the local computer. - Restart
Machines:
Restarting the affected computers can sometimes help to apply changes that have been delayed.
4. Check for Policy Replication:
- Verify
Replication: Make sure the Group Policy Object (GPO) has replicated to the
domain controllers where the client machines are getting the GPOs
from.
- Review
Replication Status: Check for any errors or warnings in the event logs
related to replication.
5. Troubleshoot Specific Issues:
- WMI
Filters:
If using WMI filters, verify their configuration and ensure they are not blocking the application of the policy. - Authenticated
Users Group:
A known issue exists where the "Authenticated Users" group may require specific permissions for the policy to apply correctly. Consider adding the group to the delegation tab with "Read" permissions.
6. Additional Tips:
- Use
gpresult:
The gpresult command can be used to determine which Group Policies are being applied to a user or computer, and whether they were applied successfully or not. - Check
Event Logs:
Review the event logs for any errors or warnings related to Group Policy processing. - Document
and Test:
Create a clear documentation of the policy and conduct thorough testing before deploying it.
L3 Level: When a Group Policy Object (GPO) fails to apply to a
computer, it is usually due to incorrect linking, security filtering
issues, or network connectivity problems.
1. Immediate Diagnostic Steps
Run these commands on the affected computer to identify why
the policy is being skipped:
- Generate
a Report: Run gpresult /h report.html in an elevated Command
Prompt. Open the resulting file to see a list of "Applied GPOs"
versus "Denied GPOs" and the specific reason for denial (e.g.,
"Empty," "WMI Filter," or "Security").
- Force
an Update: Run gpupdate /force to immediately pull the
latest settings from the Domain Controller (DC).
- Check
Computer vs. User Scope: Remember that a standard user account cannot
see computer-level policies in gpresult. You must run
Command Prompt as an Administrator to see the
"Computer Configuration" results.
2. Common Causes & Solutions
- Incorrect
Linking: Ensure the GPO is linked to the Organizational Unit
(OU) that actually contains the computer object. If the GPO has
computer settings but is linked to a "Users" OU, it will not
apply to computers.
- Security
Filtering (MS16-072): Since a 2016 security update, computers must
have Read access to a GPO even if it only contains user
settings. Ensure "Authenticated Users" or "Domain
Computers" has "Read" permission in the Delegation tab
of the GPO.
- Blocked
Inheritance: If the OU containing the computer has "Block
Inheritance" enabled (indicated by a blue exclamation mark in GPMC),
higher-level GPOs will not apply unless they are set to Enforced.
- WMI
Filters: Check if a WMI filter is attached to the GPO. If the
computer’s hardware or OS version doesn't match the filter's criteria, the
policy will be ignored.
- Network/DNS
Issues: The computer must be able to resolve the domain name and reach
the DC via LDAP (port 389) and SMB (port 445). Use nslookup to
verify the computer can find your domain controllers.
- Corrupt
Local Cache: If only one computer is affected, its local GPO cache may
be corrupt. Deleting the C:\Windows\System32\GroupPolicy\Machine\Registry.pol file
and running gpupdate /force can often fix this.

Comments
Post a Comment