Updating from version 2.60

Please read this information if you are upgrading from EventSentry v2.60!

This chapter contains very important information for users updating to version 2.7x from earlier versions of EventSentry. Read this chapter carefully to avoid losing parts of your configuration.

With the introduction of filter packages, the previously introduced Local Filters feature has become obsolete and will not be supported anymore. While local filters will be migrated to a "Local Filters Package" on the computer where you run the EventSentry setup, they will be lost on remote computers that are updated with the remote update feature.

Local filters from version 2.60 (and earlier) will be lost the first time you update the remote agents or push the configuration.

If you need to retain the local filters that you created on remote computer then you will have follow the steps below:

1.	Connect to the remote computers that have local filters and note down the names and properties of these filters, including the computer name.

2.	After you have migrated to version 2.70 create a filter package, for example "Custom Filters".

3.	Add all the filters to this package, and make sure that enter the computer name where these filters are from in the Computer Name field. This will ensure that the filter will only be processed on that computer.

4.	Make the package global or assign it to all computers that had local filters in version 2.60.

With the introduction of filter packages, the previously introduced Global Filters feature will not be available anymore, instead you can create global packages that will be processed on all computers. Global filters will be automatically migrated to a Migrated Global Filters package when updating to version 2.70.

Starting with version 2.70, filters are not organized through groups, global and local containers anymore. Instead, filters are organized into filter packages which are then assigned to either groups or computers. Filter packages can also be made global so that they apply to all computers, regardless of group membership.

Your configuration will of course be preserved, and all filters that previously belonged to a group will be automatically migrated to a package. For example, all filters from the SERVERS group will be migrated to Migrated filters from SERVERS. Health and tracking packages are now also organized using packages, and will migrated in a similar fashion.

We recommend that you review your configuration after the migration carefully and make adjustments as necessary. For example, you will almost always be able to consolidate your health packages into one or two packages.

Filter package order is not relevant for package/filter processing. Exclude filters will always be processed before include filters, regardless of their package order.

Since new tables were added to the database it is also necessary to update the database. If you are using Microsoft SQL Server, then you the database will be automatically updated during the installation, make sure that you select the database feature and provide login information.

If you are using MySQL, Oracle or Access then you will need to update the database using the Database Setup Wizard. Running the Database Setup Wizard after the installation has been updated will ensure that all necessary tables exist.

1.	Download the most current setup file and start the installation on the machine where the management console is installed. You will not have to apply any patches if you download the latest setup, which already has all patches incorporated into it.

The MSI installer will now automatically upgrade your existing installation. If the upgrade fails, uninstall version 2.60 (make sure you have a configuration backup) and then run the latest setup again. If your configuration was not preserved, import the previously exported configuration (File -> Import).

Perform a Remote Update "Manage Agent(s)" to update the service on the remaining computers, and ensure that "Always update configuration when updating remote agents" is checked in Tools -> Options -> Remote Update. Read the Local Filters section above as local filters on remote computers will be discarded when you update the configuration on remote hosts.