Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 1058 Source: Microsoft-Windows-GroupPolicy

The processing of Group Policy failed. Windows attempted to read the file \\domain\SysVol\domain\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.
See the link to EV100186 ("Microsoft TechNet: Group Policy Preprocessing (Networking)") for details on solving this problem.
According to EV100608 (Group Policy Windows attempted to read the filed), this may happen if a group policy has not been yet replicated to one of the domain controller. The solution is to identify the specified policy, verify that it does exist on the domain controller reporting the error and then re-initiate the replication using gpupdate.
In my case, I tried what Microsoft recommended by going to and trying to open gpt.ini at \\dcname\SYVOL\<domain>\Policies\<guid>\gpt.ini and it still saying the path was invalid. So I went to the folder itselt in SYSVOL and I right clicked it and tried to do a rename and I saw that it contained extra information. So I deleted that and bingo, problem was solved.
This can happen if the domain controller has network discovery turned off. Here are the details: I attempted to visit \\domaincontroller from the domain controller itself, and was told that it couldn't be found. I then tried to browse the whole network, and was told that network discovery was turned off and to "click to turn network discovery on". When I turned network discovery on, I was able to browse the network, but it also resolved the 1058 error.
I really do not know why but in my case the only thing that had helped was to remove the "(same as parent folder) Host (A)" entry for the domain controller, not the "domain controller Host (A)" itself, from the DNS zone. Then went back to the client and did a gpupdate /force. The message now was not "Access denied" anymore, but "The network path was not found". After re-adding the above mentioned entry and another gpupdate /force it was all fine for me and the client.

For us it happened with a 2008 SP2 domain controller that also hosted their redirected My Documents. For some reason the Server service wasn't allowing incoming connections (firewall was disabled). After a reboot it was fixed and working again.
Windows Vista Business SP1 was not mapping network drives during logon among other things since Group Policy could not be read. I tried accessing the \\\netlogon share and the system could not resolve the full DNS name. It could however resolve \\domaincontroller\netlogon. I disabled the TCP/IP NetBIOS Helper service (among others) to help free up resources on the Vista computer so NetBIOS name resolution was not working. I restarted the TCP/IP NetBIOS Helper Service, then logged off and logged back in. After that, name resolution worked correctly and GP was applied.

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to



Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.