EventSentry requires the EventSentry agent to installed on running on all machines that you need to monitor. If the agent is not installed or stopped no monitoring will occur. If the EventSentry is stopped then you can either start it by opening up the Services control panel selecting the EventSentry service and starting it or you can...
It is not recommended to run the Heartbeat Agent under the LocalSystem account if you are monitoring the status of the EventSentry service agent on remote computers. This is because the LocalSystem account does not in most cases have permission to query the status of the EventSentry service. This results in Access Denied error messages ...
EventSentry secures the registry key where the EventSentry configuration is stored HKLM\Software\netikus.net\EventSentry by removing the following builtin users and groups every time the Management Console or Agent is started: Users Power Users Everyone Guest Terminal Server User from the ACL that protects the main registr...
You can configure EventSentry to connect to database servers either by using an ODBC connection string recommended or by using an ODBC System DSN. System DSN39s are generally not recommended due to resulting additional administrative overhead. If you configure an EventSentry database action with a System DSN then all computers that are runn...
EventSentry currently uses ODBC to communicate with the available database servers including MySQL. As such an ODBC driver for the selected database type needs to be installed on all hosts that are running the agent and need to consolidate information to the database. As such you will need to install the MySQL ODBC driver on all machines t...
It is not recommended that you use the supplied Access database in an EventSentry installation that includes more than one computer. Microsoft Access does not handle large quantities of data well and the remote computers running the ES Agent will need to be reconfigured so that they can access the central Access database. If you are looki...
The EventSentry registry contains the installdir value that stores the physical location where EventSentry is installed with the setup program C:\Program Files\EventSentry by default. This registry value does not affect machines that are only running the EventSentry agent. If this value is missing or wrong then you might have troubles...
The Process Tracking feature of EventSentry relies on the Operating System logging security events to the security event log indicating when processes are started and stopped. These security events are generated when Audit Process Tracking is enabled in the active security policy. Please see the additional links below for information on ...
The Logon Tracking feature of EventSentry relies on the Operating System logging security events to the security event log indicating when users log on and log off. These security events are generated when Audit Logon Events is enabled in the active security policy. Please see the additional links below for information on how to enable ...
To enable ASP support on IIS ASP support is disabled by default follow the steps below: IIS 6 Go to Start Settings Control Panel Open Add or Remove Programs Click on Add/Remove Windows Components Select Application Server and click Details Select Internet Information Services IIS and click Details Select World Wide ...
Since no database action was found in the EventSentry configuration you will not be able to consolidate any information e.g. events performance information inventory etc.. You need to setup a database action including an EventSentry database to start consolidating information. Please see the additional links below for more information.
The support utility was not able to connect to one of the configured database actions which usually indicates a connectivity problem between the host where the support utility was launched and the database server. Please try the following steps: Make sure that you have the required ODBC drivers installed. See Database ODBC Drivers for m...
