Group Policy Errors
I have errors in my event viewer for group policy that come up every 5 minutes and say:
The processing of Group Policy failed. Windows attempted to read the file \\domain.local\sysvol\doma
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.
What I found is that that file path for {6AC1..... is not in that folder. There is a different folder there. We migrated to this server a few years ago from a server running 2003. I am wondering if something didn't replicate properly.
If that is the case how do I resolve the issue. The old server is no longer available.
When I go into Group Policy Management there are additional GPOs listed for SBS but when I right click and edit it is unable to find the path specified.
Also when I run gpupdate on the server I get:
C:\Users\username>gpupdate
Updating Policy...
User Policy update has completed successfully.
Computer policy could not be updated successfully. The following errors were encountered:
The processing of Group Policy failed. Windows attempted to read the file \\domain.local\sysvol\doma
\gpt.ini from a domain controller and was not successful. Group Policy settings
may not be applied until this event is resolved. This issue may be transient 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.
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.
Any help would be great. Let me know if additional info is needed.
Thanks
The processing of Group Policy failed. Windows attempted to read the file \\domain.local\sysvol\doma
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.
What I found is that that file path for {6AC1..... is not in that folder. There is a different folder there. We migrated to this server a few years ago from a server running 2003. I am wondering if something didn't replicate properly.
If that is the case how do I resolve the issue. The old server is no longer available.
When I go into Group Policy Management there are additional GPOs listed for SBS but when I right click and edit it is unable to find the path specified.
Also when I run gpupdate on the server I get:
C:\Users\username>gpupdate
Updating Policy...
User Policy update has completed successfully.
Computer policy could not be updated successfully. The following errors were encountered:
The processing of Group Policy failed. Windows attempted to read the file \\domain.local\sysvol\doma
\gpt.ini from a domain controller and was not successful. Group Policy settings
may not be applied until this event is resolved. This issue may be transient 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.
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.
Any help would be great. Let me know if additional info is needed.
Thanks
ASKER
Thanks for Responding.
I saw that page before, but it says as a last resort to do that so wasn't sure if that is my only option or not.
Yes it is on the DC, its the only server in this environment.
Would you recommend running that command? what are the possible outcomes for issues?
Thanks
I saw that page before, but it says as a last resort to do that so wasn't sure if that is my only option or not.
Yes it is on the DC, its the only server in this environment.
Would you recommend running that command? what are the possible outcomes for issues?
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I would follow this path -
1. on affected server run 'set logonserver' to see which dc it is contacting for GPOs
2. login to that dc and open gpmc.msc Group policy mgmt. console.
3. go to the target ou in gpmc for the affected server
4. if you select a policy and go to the details option in right pane, you can see unique id for each GPO
5. match that id with 6AC1786C-016F-11D2-945F-00
this will let you know what policy is actually culprit then decide how to correct the issue.
there are multiple things you have to consider based on the policy that is failing but generally replication is the issue or missing access rights on the policy that is defined may cause or in extreme cases you may also consider network firewall as well so you will have to travel further to identify further.
1. on affected server run 'set logonserver' to see which dc it is contacting for GPOs
2. login to that dc and open gpmc.msc Group policy mgmt. console.
3. go to the target ou in gpmc for the affected server
4. if you select a policy and go to the details option in right pane, you can see unique id for each GPO
5. match that id with 6AC1786C-016F-11D2-945F-00
this will let you know what policy is actually culprit then decide how to correct the issue.
there are multiple things you have to consider based on the policy that is failing but generally replication is the issue or missing access rights on the policy that is defined may cause or in extreme cases you may also consider network firewall as well so you will have to travel further to identify further.
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
{6AC1786C-016F-11D2-945F-0
Microsoft default policies can be restored in case of failure. You can use DCGPOFIX to recreate policies. http://technet.microsoft.com/en-us/library/hh875588.aspx