This section includes overviews of common problems including step-by-step checklists to solve specific issues.
Group Policy Engine/Core Processing Failures
Catastrophic failures can occur causing all of policy processing to fail including client side extensions (CSEs).
These kinds of failures generally occur during the information gathering part of policy processing. Errors are logged under Userenv source in the Event Log.
The types of errors causing Group Policy core failures include:
DNS problems. For example no DNS is available or there are missing or stale entries in the DNS database. (To diagnose this issue, use the netdiag tool, as explained earlier.)
Network/Active Directory issues. For example, you cannot connect to the network, or you are unable to ping, find, or bind to a domain controller. To diagnose this issue, use NLTEST, as explained earlier.
Replication. Differences in replication time between directory service replication and SYSVOL replication. Version number is mismatched in the Group Policy container or Group Policy template between Active Directory and SYSVOL. (To diagnose this issue, use the GPOTool.)
Replication between domain controllers causing different versions of policy to be stored. (To diagnose this issue, use the GPOTool.)
Note: Event log errors use source Userenv. Not all failures are logged in the Event Log to avoid Event Log “flooding.”
|
