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: 2068 Source: msmq

The list of MQIS servers in registry is empty.
See ME839929 for information on fixing this event.
This event may be recorded on a stand-alone server that has Message Queuing Services installed that it is not part of any domain.

From a newsgroups posting: "The combination of NT4 supporting server and W2K dependent client is not supported. You can install a W2K Independent Client in an NT4 environment, though. When you install Independent Client, you'll be asked for the name of your site controller.  Give the name of one of your NT4 PSCs (or the PEC).  The Independent Client will join your NT4.0 MSMQ Enterprise just like an NT 4.0 IC or any other MSMQ 1.0 system. At that point, a program running on your Windows 2000 system can open a queue anywhere in your MSMQ Enterprise just like any of the NT 4.0 systems do.  You can use pathname to open public or private queues, you can use MQLocate to search for a public queue, etc."

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.