Updating to version 2.92

EventSentry 2.92 includes important changes to the Syslog Daemon component, Access and the default agent location. Please read this document carefully, especially if you are currently using the Syslog functionality.

EventSentry v2.92 introduces a new service, the "Network Services" service, which includes the SNMP as well as the Syslog daemon. Previously, up until version 2.91, the Syslog daemon was included in the main EventSentry agent (the EventSentry service). Starting with version 2.92 however, the Syslog daemon has been moved to newly added "Network Services" service. This is a better choice, since the Syslog daemon usually only runs on a small number of machines, and as such it is unnecessary to include the Syslog capability in every agent.

If you are receiving Syslog messages in EventSentry, then you will need to make sure that you select this component when installing EventSentry v2.92. Please note that your settings will be migrated.

The Network Services service requires that at least a 10-host heartbeat license is installed. The service will not function properly without this license.

This requirement does not exist for evaluation users, the Network Services service will also run properly with an evaluation license.

If the Syslog component is running on a computer other than where you are running the setup, then you will need to manually install the EventSentry Network Services service. This is a one-time process, and should only take a few minutes.

Simply run the EventSentry v2.92 setup, and select the "Network Services" and "Management Console" component. You will not need to select any other components. Once complete, you can launch the management console, and configure the syslog and snmp daemon.

Please follow the steps below to install the network services service on a remote computer:

1.	Copy the EventSentry installation folder (e.g. C:\Program Files\EventSentry) to a temporary directory on the remote computer. Alternatively, you can also temporarily share the installation folder and access it from the remote computer.

3.	Click "Install". When asked for the source folder, specify the EventSentry installation folder.

4.	When complete, copy the Microsoft.VC90.CRT folder to %SYSTEMROOT%\system32\EventSentry\ folder.

EventSentry no longer includes, and supports, the Microsoft Access Database that shipped with earlier versions of the EventSentry. Access was dropped since it provides little scalability and does not work well when monitoring more than one computer. Instead, EventSentry now ships with the MS SQL Express 2008 R2 Setup Assistant which automatically downloads, configures and installs SQL Server Express 2008 R2.

The installation location for the agents has changed from %SYSTEMROOT%\system32 to

This folder now contains all EventSentry-related files, including temporary and log files. This change is transparent to users and will be handled automatically by the remote update functionality in the management console and remote update tool.

The behavior of timer filter has changed slightly. Filters configured to clear timers, will now act like normal filters (and notify the configured action) if they match events while no timer is active. Prior to v2.92, these filters would never notify an action.