Home / server / Questions / 403093
In Process
Alex Berry
Asked: 2012-06-29 07:01:20 +0800 CST

Group policy issues

  • 772

We are having an issue on one of our clients relatively new sbs installs.

The domain consists of a single SBS 2011 server with 4 Windows 7 clients and 3 XP clients. Most of the time everything is fine, however roughly every 3 days, Windows 7 clients start timing out when trying to receive computer group policy.

This results in hour long delays before getting to the login screen in the morning. This is accompanied by event ID 6006, win login errors stating it took 3599 seconds to process policy. Once they've booted they can log in without issue however gpupdate fails again on computer policy and gpresult comes back with access denied, even when run as domain admin... At this point if we restart the server the network is fine for 3 days.

I thought perhaps it might be ipv6 or smb2, but disabling ipv6 on the clients doesn't help and the clients can browse the sysvol folder freely on smb2 anyway. Does anyone have any ideas or routes I can take to further diagnose the issue?

windows group-policy windows-7 windows-sbs-2011

1 Answers

  1. Sounds like your domain windows are trying to contact your DC but unable to get information what they need from DC. It could be either you have corrupted profile roaming or computers are trying to map a network drive but failed.

    I would do the following:

    1. Make sure SBS 2011 has all windows update installed and up to date.
    2. Since I do know have enough information on the structure of group policies you have in your DC I am unable to provide exact resolution but I would disable group policy one by one then do the gpupdate on domain PCs then check the result via eventviewer. If you have policy for profile roaming or network drive mapping on your computer container, remove one from the container and see what happens.
    3. Check there is no duplicated IP address assigned to your PC. I assume you have fixed IP address on your all domain PCs as well as your DNS.
    4. Rejoin your domain PCs.
    • 0