I've never done it, but there are a lot of articles for reference if you search on recreating your default domain policies.
I've actually seen that event though on a few workstations that were not getting any policies processed correctly. It's usually just the first event recorded, pointing to the GUID of the default domain policy, like what you have below. All policies after that are typically not read at all, and then not applied on the station. So, my question would be, are you seeing this on other machines, or just this server? If it's just on the server, it's not probably an issue with the policy itself, but rather with the server's processing of policies. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jesse Rink Sent: Tuesday, December 1, 2015 8:34 AM To: [email protected] Subject: [NTSysADM] Event ID 1058 on DC My environment consists of only (2) DCs. One DC at each Site. Both are Win 2012 R2. All my Sysvol information (policies, scripts, etc.) seems to be replicating fine between the two DCs. However, once or twice a day, at random times, on the main DC (schema master, PDC emulator, etc.) I see event ID 1058 messages in the event System log. "The processing of Group Policy failed. Windows attempted to read the file \\mydomain.local\sysvol\mydomain.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\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." Now, oddly enough, every time I try, I can successfully access that file. The GUID corresponds to our Default Domain Policy. Running gpupdate/force on the DC results in everything looking good even though I see those errors in the event log randomly (but never when I just run gpupdate /force). There also seem to be no DFRS/replication issues from looking at the logs. Yet, once or twice a day, this error occurs. I'm wondering, is there any reason I can't DELETE the Default Domain Policy completely and re-create it with the same settings? I've never attempted to delete the Default Domain Policy, but I can't forsee any reason why it couldn't be delete and re-created like any other GPO? Hoping maybe that will fix the random error. JR
