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: 1062 Source: VirtualServer

"<virtual machine>" could not be started because a disk-related error occurred.
When you try to start a virtual machine with a user account that does not have Write access to the virtual machine configuration folder, you will receive a message such as, "The virtual machine Virtualmachinename could not be started. An unexpected error occurred" or "Virtualmachinename could not be started because a disk-related error occurred". This occurs because Virtual Server creates an empty saved state (.vsv) file in the virtual machine configuration folder when a virtual machine starts up. You can resolve this problem by granting Write permission on the virtual machine configuration folder to the user account for the virtual machine. See the link to "Release Notes for Virtual Server 2005 R2 SP1" to view the source of this information.

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.