Continuing after Control-M/Server migration

Thisprocedure describes how to continue working with existing agents after you have finished the Control-M/Server migration.

To continue after Control-M/Server migration:

1. To continue working with Control-M/Agents from the old environment, do one or more of the following:
   • Add the new Control-M/Server host name to the Authorized Servers list for every Control-M/Agent. For more information on the Authorized Server field, see Control-M Installation Guide.
   • Configure the Control-M/Server default communication protocol to match the version of the majority of your connected Control-M/Agents. The default communication protocol version in Control-M/Server 9.0.00 is 11. For details, see Defining Control-M/Server system parameters and Communication parameters (in the Control-M Administration Guide).
2. Configure the correct Agent configuration parameter PROTOCOL_VERSION. The Server to Agent protocol version must be set to the lowest version of either the Control-M/Server or Agent. This parameter is set on both the Agent and the Server for that agent and they must match. You can use the Agent utility ctmagcfg to set the parameter on the Agent and the Control-M/Server utility ctm_menu to set it on the server. Here are the possible values for PROTOCOL_VERSION:

   Control-M/Agent Version      Version

   6.3.0x      07

   6.4.0x      08

   7.0.0x      09

   8.0.0x      10

   9.0.00 until 9.0.00.300      11

   9.0.00.400 until 9.0.19.200      12

   EXAMPLE: If Control-M/Server is 9.0.00 and the Agent is 8.0.00, then the PROTOCOL_VERSION should be set to 10.

3. If the ctmldnrs.dat file is migrated, copy the ctmldnrs.dat file from the Control-M/Server home folder (<server_home>) to the default location (<server_home>/ctm_server/tmp) or another location, as required.

   NOTE: On UNIX, the ctmldnrs.dat is deleted from the default location (<server_home>/ctm_server/tmp) when Control-M/Server is started.

4. After migrating from Linux to Windows, add the SYSTEM user to Control-M/Server security. For this task, you can use the ctmsec utility.

   For more information, see Control-M/Server security (in the Control-M Administration Guide).