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: 1054 Source: Microsoft-Windows-GroupPolicy

The processing of Group Policy failed. Windows could not obtain the name of a domain controller. This could be caused by a name resolution failure. Verify your Domain Name Sysytem (DNS) is configured and working correctly.
According to Microsoft, this event occurs because the domain from which the group policy should be downloaed either does not exist or could not be contacted. After ensuring that the network connectivity to the domain controller has been reestablished, refresh the Group Policy on the computer:

Open the Start menu. Click All Programs and then click Accessories.
Click Command Prompt.
In the command prompt window, type gpupdate and then press ENTER.
When the gpupdate command completes, open the Event Viewer.
Group Policy is working correctly if the last Group Policy event to appear in the System event log has one of the following event IDs:


ME324174 also provides an example where this behavior may occur if the address for the configured preferred DNS server on the client is invalid or unreachable.

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.