GPO processing is slow
Documentation: Microsoft Learn
Work the problem
One workstation logs on slowly
Fictional case: A workstation takes several minutes to finish policy processing. Other clients in the same OU are fast.
Reasoning notebook
Record the evidence that supports your answer and the check you would run next. Your notes stay in this browser — nothing is uploaded.
Why it happens
Policy processing is a sequence of directory lookups and SYSVOL file reads, so it inherits every delay in DNS and controller location. A client that discovers a domain controller across a slow link pays that cost on every extension it processes. Individual extensions such as software installation or folder redirection add seconds of their own, and one slow extension dominates the total.
Check this first
What to look for
Use timestamps and extension events to identify the slow stage, then compare with a healthy client.
Working through it
- Generate a report with gpresult /h and open it to see which extensions consumed the time.
- Read the Group Policy operational log and look for the longest gaps between successive activity events.
- Check which domain controller the client selected against the site its subnet is assigned to.
- Confirm the client's DNS servers are the pair serving the local site rather than a remote one.
- Disable one suspect extension at a time through a test OU and measure again after each change.
Avoiding it next time
Verify the repair: Repeat policy processing on the affected client and compare extension timing, errors and effective settings with the baseline.