Upgrading from v2.7x to v2.8x

Configuring the installer (Step 4 of 6)

Heartbeat Options

The EventSentry heartbeat agent will run as a service under the LocalSystem account as a default if you leave the username field empty. Please note that when accepting the default, the heartbeat agent will likely return "Access denied" when monitoring the EventSentry service status on remote hosts. This is because the LocalSystem account does not have enough privileges to query a service status on remote hosts.

It is recommended that you to specify a user account that has permission to query the status of services on the remote host(s), such as a domain or local admin account.

You can also change this later by performing the following steps:

• Navigate to Start -> Programs -> Administrative Tools -> Services


• Locate the "EventSentry Heartbeat Monitor"


• Right-click on the services and select "Properties"


• Select the "Log On" tab, then change the user account


• Restart the "EventSentry Heartbeat Monitor" service

Database Options

Specify the hostname of the SQL server and select a login option (Windows authentication or server authentication). If Windows authentication is selected, then the currently logged account should have proper credentials to modify the EventSentry database on the SQL server. If Server authentication is selected, then the sa account or a similar administrative database login (that has permissions to modify the EventSentry database) is recommended.

By default the EventSentry database is named EventSentry. If you specified a different database name when you initially installed EventSentry, then you will have to enter that database name here. Otherwise, the installer will create a new database and name it EventSentry.

"View Optimization Tips" will show you various database optimization tips, such as setting the initial database size.

Completing the Update

We have configured all options and are now ready to run the update.