CHI-LTD
asked on
gpupdate errors
getting:
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\dradministrator>g pupdate /force
Updating Policy...
User Policy update has completed successfully.
Computer policy could not be updated successfully. The following errors were enc
ountered:
The processing of Group Policy failed. Windows attempted to read the file \\domain.local\SysVol\doma in.local\P olicies\{4 49D5950-AC E9-4FCA-96 57-0AD4613
A39C7}\gpt.ini from a domain controller and was not successful. Group Policy set
tings may not be applied until this event is resolved. This issue may be transie
nt 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 invoke gpmc.msc to access infor
mation about Group Policy results.
C:\Users\dradministrator>
this is happening on a member server running windows 2008 standard as RDS on our DR site. There was an issue with the subnet mask of the network card so this was changed/resolved.
Our other servers are updating fine using gpupdate /force....
however not all the gpo are showing on the DR site domain controller.
ideas?
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\dradministrator>g
Updating Policy...
User Policy update has completed successfully.
Computer policy could not be updated successfully. The following errors were enc
ountered:
The processing of Group Policy failed. Windows attempted to read the file \\domain.local\SysVol\doma
A39C7}\gpt.ini from a domain controller and was not successful. Group Policy set
tings may not be applied until this event is resolved. This issue may be transie
nt 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 invoke gpmc.msc to access infor
mation about Group Policy results.
C:\Users\dradministrator>
this is happening on a member server running windows 2008 standard as RDS on our DR site. There was an issue with the subnet mask of the network card so this was changed/resolved.
Our other servers are updating fine using gpupdate /force....
however not all the gpo are showing on the DR site domain controller.
ideas?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
found the FRS had stopped..... was set to manual1!!!!!!!!!!!!!!!!!11
ASKER
fixed by starting FRS
ASKER
the DR site sysvol hasnt updated the same as our live site sysvol directories....