Migrating from Previous Versions

On PATROL Agents

No specific migration is required. If a previous version of Hardware Sentry has been installed, it will be overwritten by the latest version. Upon startup, Hardware Sentry will take the necessary action to complete the migration. If needed, it will migrate configuration variables.

On PATROL Consoles (Classic)

1.Install the latest version of Hardware Sentry on the PATROL Consoles. This version will let you connect seamlessly to PATROL Agents on which a different version of Hardware Sentry is installed. You just have to make sure the version installed on the PATROL Console is more recent than the one present on the PATROL Agent

2.Load the MS_HARDWARE_SENTRY1.kml file in the PATROL Console to update the console profile and include the Hardware Sentry classes. If you do not load the new classes in the console, Hardware Sentry will not work properly, that is, you will not be aware when a hardware agent used by Hardware Sentry has failed.

Avoid the use of the "Developer" connection type in the PATROL Console. Never use the "Commit KMs" feature of the PATROL Console, especially when you deal with several versions of the same KM in your environment.

On Console Server, PATROL Central - Web Edition

As Console Server and PATROL Central can manage several versions of the same KM, you can install different versions of  Hardware Sentry side-by-side on the same Console Server. Console Server automatically uses the appropriate version of the KM depending on what is running on the displayed agent.

After installing the latest version of Hardware Sentry, load the MS_HARDWARE_SENTRY1.kml file to update the console profile and include the Hardware Sentry classes. If you do not load the new classes in the profile, Hardware Sentry will work almost properly except that the profile will not be aware when a hardware agent used by Hardware Sentry has failed.