We have an SBS 2008 environment with only one DC. I was on a Windows 7 client computer and I noticed in the event viewer that the Group Policy was not being applied. When I run “gpupdate” from cmd prompt, I get the following:

Updating Policy…

User policy could not be updated successfully. The following errors were encount
ered:

The processing of Group Policy failed. Windows attempted to read the file \repo
rtersink.local\SysVol\reportersink.local\Policies{BAD2EE73-95F3-4A2F-9D3F-CBBB9
BE3C94A}\gpt.ini from a domain controller and was not successful. Group Policy s
ettings may not be applied until this event is resolved. This issue may be trans
ient and could be caused by one or more of the following:
a) Name Resolution/Network Connectivity to the current domain controller.
b) File Replication Service Latency (a file created on another domain controller
has not replicated to the current domain controller).
c) The Distributed File System (DFS) client has been disabled.
Computer policy could not be updated successfully. The following errors were enc
ountered:

To diagnose the failure, review the event log or run GPRESULT /H GPReport.html f
rom the command line to access information about Group Policy results."

Also under administrative events I see a bunch of 1058 errors. How can I troubleshoot this?

Additionally It seems to be only happening on Windows 7 machines, on the XP computers “gpupdate” is successful and there are no event id 1058’s in the XP machines either

3 Spice ups

If one set of clients is working and another is not, then likely the problem is not the server. Have you checked the Win7 clients’ connectivity to the server? Are these desktops, laptops, etc.? Can you open that path by hand on the client, i.e. copy and past the path up to gpt.ini and see if you can see and open the file?

1 Spice up

Have you tried running gpupdate with just computer settings? What does rsop wizard from gpmc say?

@Sopipater - Yes the path is Accessible by the Windows 7 clients and the file opens. Also they are not loosing connectivity. I noticed that the XP computers login quicker but the Windows 7 PC’s take about 5-10 minutes to login because of the GP no processing right.

Besides OS, are there any common differences between the set that succeed and the set that fails?

If it is OS based, then I’d check through your policy that is being applied and see if any settings have been deprecated between XP and Win7.

I have to wait until Friday when I am back there next but I will check.

Hello Paul,

Did you managed to resolve this issue? I am having the same issue none of the group policies are getting updated in Win 7 and Win 8 systems but it’s working fine in XP sp3 clients