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: 2089 Source: MSExchangeDSAccess

Process <process name> (PID=<process id>). The Configuration Domain Controller specified in the registry (<distinguished name>)was not found in the Sites container in the Active Directory. DSAccess will choose the Configuration Domain Controller from the list of available Domain Controllers.
This event occurred after one of our DCs crashed. Appears to be similar to Event ID 2090 from the same source. Solution: In Exchange System Manager drill down to your server, right click, choose Properties and go to the "Directory Access" tab. Pull the drop down to select the category where the missing DC is listed, remove that DC and add one that can be contacted. Repeat for all categories as necessary.
As per Microsoft: "This message indicates that the configuration domain controller specified by the registry key does not exist. DSAccess will revert to the standard mechanism of automatically choosing the configuration domain controller. This event can occur if the Administrator misspells the hostname in the HKLM\System\CurrentControlSet\Services\MsExchangeDSAccess\Instance0\ConfigDCHostName registry key on the Exchange server". See MSEX2K3DB for additional information about this event.

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.