Only one version of Hardware Sentry can be installed on a PATROL Agent, therefore, a previous installation of Hardware Sentry will be overwritten by the latest version.

No specific migration operation is required (you do not need to uninstall the previous version of Hardware Sentry first). Upon startup, Hardware Sentry will take the necessary action to complete the migration (migrating configuration variables if needed).

Just as for PATROL Agents, only one version of Hardware Sentry can be installed on a PATROL Console (Classic). Logically, this could cause problems if a PATROL Console is connected several PATROL Agents with different versions of Hardware Sentry.

However, with this latest version of Hardware Sentry on the PATROL Console, you will be able to connect to Agents with previous versions of Hardware Sentry seamlessly. All you need to ensure is that the PATROL Console has a more recent version than that on the PATROL Agents.

In any case, it is essential to update the console profiles to include the new Hardware Sentry classes. To do this:

Load MS_HARDWARE_SENTRY1.kml file in the PATROL Console

This will add the two new connector-related 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.

As Console Server and PATROL Central can manage several versions of the same KM, you can install Hardware Sentry 1.4x, 1.3x, 1.2x and 1.1x 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.

However, it is still essential to update the console profiles to include the new Hardware Sentry classes. To achieve this:

Load the MS_HARDWARE_SENTRY1.kml file in the profile.

This will add the two new connector-related 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.