Group Policy - "Computer policy could not be updated successfully" - Help needed.

[AvaFX]

Hi guys,

 

I just wondered if someone could please help me troubleshoot a Group policy issue on Server 2019?

 

During a brief window of around 45mins-1hr at around 1pm every day, Group policy updates can't process. I've pasted the error from the command-line (see below), I was hoping someone could please point me in the right direction? I'm not seeing any obvious errors my end as of yet.

 

Thank you

 

[EDIT: All the machines are wired]

...

 

 

 

"Updating policy...Computer policy could not be updated successfully. The following errors were encountered:The processing of Group Policy failed. Windows attempted to read the file \\\SysVol\\Policies\{624EAD89-2A6B-47FA-9142-C0E054B8F51D}\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.User Policy update has completed successfully.The following warnings were encountered during user policy processing:The Group Policy Client Side Extension Folder Redirection was unable to apply one or more settings because the changes must be processed before system startup or user logon. The system will wait for Group Policy processing to finish completely before the next startup or logon for this user, and this may result in slow startup and boot performance.To diagnose the failure, review the event log or run GPRESULT /H GPReport.html from the command line to access information about Group Policy results."

Edited February 23, 2021 by AvaFX

[chazzy2501]

I see these all the time, it just a characteristic of Windows isn't it. policy refreshes occur periodically, missing a window shouldn't be an issue. The network or OS wasn't ready at the time.

[computer_expert]

Is there a a backup/scheduled task/AV scan/active directory replication running at about that time killing the DCs or server/client performance?

 

If a backup is running - is your network/server hardware(/hypervisor if virtual) being overloaded?

Edited February 23, 2021 by computer_expert

[AvaFX]

Is there a a backup/scheduled task/AV scan/active directory replication running at about that time killing the DCs or server/client performance?

 

If a backup is running - is your network/server hardware(/hypervisor if virtual) being overloaded?

 

Thanks for your reply! There's no backups or tasks scheduled for that time (only out of hours) and I've monitored the DCs performance in vSphere and there's no spikes in resources. I can't see anything network-related that might cause an impact on this.

[RobD]

Double check the domain controller is replicating the good as it should:

https://bohemiangrove.co.uk/domain-controller-sysvol-and-group-polices/

Failing that try and clear the local gpo cache on the machine:

https://bohemiangrove.co.uk/clear-group-policy-cache/

[AvaFX]

Double check the domain controller is replicating the good as it should:

https://bohemiangrove.co.uk/domain-controller-sysvol-and-group-polices/

Failing that try and clear the local gpo cache on the machine:

https://bohemiangrove.co.uk/clear-group-policy-cache/

 

Thank you Rob, I appreciate the links. I will give this a go!