Appendix K. Migration

Steps to Migrate to Secure Communication in Operations Sentinel level 19.0

Operations Sentinel level 19.0 supports secure and non-secure connection types. Operations Sentinel level 19.0 by default uses non-secure connection type. However, Operations Sentinel OS 2200 Console components support either secure or non-secure communication. If both the connection types are enabled on the Operations Sentinel server, then, the OS 2200 Console components use secure communication as the preferred connection type.

Follow the below migration steps on all the Operations Sentinel Servers to enable secure communication:

Prerequisites

OS 2200 Server Management Control (SMC release with Software Series 3.0) should be installed on the Operations Server.
Operations Sentinel level 19.0 must be installed on Operations Sentinel Servers and Workstations.

Steps to Migrating to Secure Environment on an Operations Sentinel Server

Stop Operations Sentinel services.
Stop the SMC service.
Open Configuration Manager and select “Network Configuration” tab. Select “Non-Secure” and “Secure” connection type and click Update button.
Start Operations Sentinel Services.
Start the SMC services.

Note: Stopping and starting the SMC services (step 2 and step 5) is applicable only on an Operations Server.

Steps to Migrate to Secure Environment on Operations Sentinel Workstation if some of the Operations Sentinel Servers are Configured to Use Non-Secure Connection

Open Operations Sentinel Console (OSC), select Operations Sentinel server from the list and then select “Secure Connection” checkbox in the “Select Server” dialog.
In OSC, click Tools and select Options, this opens the Options dialog box. In this dialog box, under Servers tab, select each Operations Sentinel servers from the list which are configured to use non-secure connection and then delete it.
Click OK.
Close all OS 2200 Console Views.
Execute “Clear OS 2200 Console Server MRU List” from Operations Sentinel product Start menu.
Open OS 2200 Console Manager, Click Tools and select Options, this opens the Options dialog box. Now, select “Secure connection” and click OK.
Refresh OS 2200 Console Manager.

Notes:

Step 3 and step 4 must be performed by every user if the same system is used by multiple users.
If the server list or MRU list contains Operations Sentinel server names that are configured to use non-secure connection type, then, opening the OS 2200 Console might not work for some instances.

Steps to Migrate to Non-Secure Environment on Operations Sentinel Workstation if some of the Operations Sentinel Servers are Configured to Use Secure Connection

From the Start menu, open Operations Sentinel Console (OSC), “Select Server” dialog box appears. Now select Operations Sentinel server from the list and uncheck the “Secure Connection” checkbox.
In OSC, click Tools and select Options, this opens the Options dialog box. In this dialog box, under Servers tab, select each Operations Sentinel servers from the list which are configured to use secure connection and then delete it.
Click OK.
Close all OS 2200 Console Views.
Execute “Clear OS 2200 Console Server MRU List” from Operations Sentinel product Start menu.
Open OS 2200 Console Manager, Click Tools and select Options, this opens the Options dialog box. Now, clear “Secure connection” and click OK.
Refresh OS 2200 Console Manager.

Notes:

Step 3 and 4 should be performed by each user if same system is used by multiple users.
If the Server list or MRU list contains Operations Sentinel Server names which are configured to use secure connection type, then opening the OS 2200 Console might not work for some instances.

Steps to Enable Secure Connection on Operations Sentinel Windows Resource Monitor

In the Services Applet window, right-click Operations Sentinel Windows Resource Monitor. Then in the shortcut menu, click Properties and in the dialog box that appears, use the “Operations Sentinel Servers” tab to select Secure connection check box and click OK.
Restart Operations Sentinel Windows Resource Monitor Service.

Caution
Operations Sentinel 19.0 now supports Secure communication with its components. While the communication is encrypted in secure type, it is not encrypted in non-secure type. Therefore, it is recommended to move all Operations Sentinel servers to secure connection type to experience seamless operations. Setting mixed connection type (secure and non-secure) requires to perform some additional steps as described above in the document.