Migrating from Previous Versions of Monitoring Studio

Monitoring Studio is the new name assigned to Application Sentry KM for PATROL. Previous versions of Monitoring Studio were formerly known as Application Sentry.

As only one version of Monitoring Studio can be installed on a PATROL Agent, a previous installation of Monitoring Studio will be overwritten by the latest version. No specific migration operation is required (you do not need to uninstall the previous version of Monitoring Studio). Upon startup, Monitoring Studio will take the action necessary to complete the migration (migrating configuration variables if needed).

Automatic migration is only supported from 8.x versions of Monitoring Studio. Earlier versions are no longer supported.

As for PATROL Agents, only one version of Monitoring Studio can be installed on a PATROL Console (Classic). The difficulty lies in the fact that a PATROL Console may need to connect to several PATROL Agents, each with different versions of Monitoring Studio. This version of Monitoring Studio supersedes previous versions. It means that with the latest version of Monitoring Studio on the PATROL Console, you will be able to seamlessly connect to Agents with previous versions of Monitoring Studio.

However, you do need to update the console profiles to include the new Monitoring Studio classes. To achieve this, all you need to do is:

•	Load the SW_SENTRY8.kml file in the PATROL Console.

This will add the new file security-related class. If you do not load the new class in the console, Monitoring Studio will not work properly, that is, you will not be able to monitor the security settings of a file.

Avoid the use of the "Developer" connection type in the PATROL Console. It is even more important that you never use the "Commit KMs" feature of the PATROL Console, especially when you deal with several versions of the same KM in your environment.

Version 8.5.00 of Monitoring Studio added various new Menu Commands in the PATROL Console. Therefore, ever since, although the new Menu Commands may seem available on all agents, previous versions of Monitoring Studio (formerly known as Application Sentry) will not be able to execute these new Menu Commands. In such case, an error message will be displayed in the System Output Window of the Agent. This problem will not occur on PATROL Central consoles.

As Console Server and PATROL Central are able to manage several versions of the same KM, you can install the current version of Monitoring Studio and earlier versions side-by-side on the same Console Server. Console Server will automatically use the appropriate version of the KM depending on what is running on the displayed agent. However, you still need to update the console profiles to include the new Monitoring Studio classes. To do so, you only need to:

If you do not load the new classes in the profile, Monitoring Studio will work but you will not be able to use the features of the new classes.