Starting with EventSentry version 2.70 you can view the native event log files usually with a .evt extension with the builtin event log viewer of EventSentry. Simply rightclick the Event Log Viewer container and select Open Log File. If you are running EventSentry v2.60 or earlier then you will need to open the event log files with th...
No restarting the EventSentry service on any machine will have no effect on other machines since the agent only works with the local event logs. The EventSentry agent does write a few events to the local machine39s Application event log upon a service restart however.
You will need to take additional configuration steps when configuring EventSentry to access resources located on different computer. By default the EventSentry agent runs under the LocalSystem account. This is a builtin system account that has administrative permissions on the local host but usually has no permissions on remote computers....
This is usually a permissions issue. When backing up the logs the EventSentry agent is running under the LocalSystem account by default and you might have to take additional steps in order for the backup to work. If you are only backing up the event logs then please click the help link below DOCID 18 for more information. If you are ba...
EventSentry Version 2.60 and earlier: This occurs only if you are using the summary notification feature and restarted the EventSentry service or the entire computer during the collection period. EventSentry Version 2.70: Starting with EventSentry 2.70 the FILTER variable is no longer supported for summary notifications due to an interna...
Added with version 2.21 was the ability to specify different credentials when using Remote Update. Please see the additional links for more information on this feature. If you cannot use the builtin authentication feature of EventSentry for some reason and are running Windows 2000 or higher then you can rightclick the GUI executable events...
EventSentry is an event log monitoring application and does by design not rescan the event logs. It monitors the event logs and processes current and new events in real time. It does not process past events. The only exception is when you have the Bootscan feature activated. When this feature is active EventSentry will rescan the event ...
EventSentry uses Windows RPC calls to update remote agents and remote update forwards all error messages reported by Windows when a remote update fails. EventSentry uses the following features: Remote Service Control connecting to the remote SCM service control manager File access EventSentry installs all required agent files to ...
Every application that is logging to the event log ussage has what is called a message file associated with it. Message files are used to translate event ids and their associated insertion strings to actual descriptive event messages. Message files are usually DLL or EXE files that are shipped with the application. For example the message fi...
The EventSentry management console is unfortunately not multiuser capable as such you cannot modify the configuration on the same machine from differnet user accounts. In fact the EventSentry console should not start if it is already opened by a different user. If multiple users need to work with EventSentry then we recommend that you eit...
EventSentry will log debug information to log files that help our support department troubleshoot configuration and software issues. All log files are limited to a certain size and will automatically switch to the next one when the maximum size has been reached. The following files are created: EventSentry Agent: eventsentrysvc1.log ev...
You can configure this behaviour in Tools Options by setting or clearing the Automatically collapse unselected groups check box. By default only one container at any given level in the tree is expanded at the same time. This is to help keep the interface clean but you can disable this option.
No you cannot assign email notification targets to system health packages. Only ODBC database notifications can be directly linked to a system health package. Instead you will have to create one or more event log filters that will look for events generated by the system health feature. All alerts generated by system health features e.g. ...
By using the 39Embedded Scripts39 feature and the 39Application Scheduler39 feature you can create a script that will write the disk defrag information to your local event logs on a regular basis. 1. Create the following embedded script: defrag.exe Systemdrive a v The file name should have a .cmd or .bat extension ...
Yes you can use the nessus.exe command line tool included with Nessus 4.x to run and export the results to a NBE file which can subsequently be imported into an EventSentry database. Please note that exporting results into the NBE format is only available in the Nessus command line utility. Nessus Command Line Interface: This will run a ...
As of EventSentry v2.92 the esdbnessusimport.exe utility only supports the NBE file format. Nessus version 4 only supports the NBE file format via the command line interface. Please see KB202 for more information on importing scans in the NBE format. Improved Nessus support including the .nessus format is planned for a future release.
To download an update from the EventSentry management console you need access to the following IPs ampamp PORTS: 216.92.10.83:80 EVENTSENTRY.COM 216.92.16.192:443 STORE.NETIKUS.NET
We can monitor bandwidth jitter latency and packet loss using performance monitoring by monitoring the output of an executable. The command line CLI can be found here: Speedtest CLIhttps://www.speedtest.net/apps/cli Download the above tool and for the purposes of this Howto we will copy it to C:\Tools on our EventSentry server. The...
