Group Policy failed to apply
Hi,
I have 2 machines that are not getting GPs and getting below error. Please assist.
Message : The processing of Group Policy failed. Windows attempted to read the file
\\abc.corp\SysVol\abc.corp
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.
LogName : System
TimeCreated : 11/8/2018 7:13:38 PM
LevelDisplayName : Error
MachineName : xyz.abc.corp
Thank you in Advance.
I have 2 machines that are not getting GPs and getting below error. Please assist.
Message : The processing of Group Policy failed. Windows attempted to read the file
\\abc.corp\SysVol\abc.corp
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.
LogName : System
TimeCreated : 11/8/2018 7:13:38 PM
LevelDisplayName : Error
MachineName : xyz.abc.corp
Thank you in Advance.
From the effected system are you able to access \\abc.corp\SysVol
ASKER
Yes, i am able to access \\abc.corp\SysVol from the effected machine
Further can you try to browse to the policy in error and let me know if you face any errors.
Also check the eventvwr of the desktop and share the error events related to it.
Also check the eventvwr of the desktop and share the error events related to it.
How many DCs? Is SYSVOL/NETLOGON syncronizing correctly?
Run dcdiag /q and repadmin /showrepl against each DC first to make sure they are working OK and report back.
ASKER
rebooted servers, issue resolved.
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
For troubleshooting you can read more here.