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: 1055 Source: Userenv

Windows cannot determine the computer name. (<error message>). Group Policy processing aborted.
I also had this issue and managed to resolve it. My environment consisted of a Terminal Server TS1, a Domain Controller and an Exchange/File Server SBS1. One user (out of several tens), after changing his password and logging in on the TS1 server could not access any resources on SBS1, be that Exchange or files/folders. The user received an authentication question were no passwords were accepted. To fix the problem I opened the password applet from Control Panel -> User Accounts -> Stored User Names and Passwords and I removed the entry for SBS1.
As per Microsoft: "A network connectivity or network configuration problem is preventing Group Policy settings from being applied. Group Policy processing for the computer or user fails and will continue to fail until this error is resolved". See MSW2KDB for more details.

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.