Upgrading Control-M/Server on Windows

This procedure describes how to upgrade from Control-M/Server 9.0.00.100 and higher to the latest version of Control-M/Server on Windows. If you want to upgrade multiple instances of Control-M/Server on several computers using the same configuration, use the automatic upgrade, as described in this procedure.

Before You Begin

• Ensure that your operating system and database software is compatible with the new version of Control-M/Server, as described in Control-M/Server Windows system requirements.
• If you are upgrading on cluster environment, see Control-M/Server Windows cluster configuration.

To upgrade Control-M/Server on Windows:

1. Log in to the computer using a user ID that has Administrator permissions.
2. Do one of the following:
   • From the Installation DVD, double-click the setup.exe file.
   • From a command prompt window, enter <source_path>\setup.exe.
3. Do one of the following:
   • Interactive upgrade: Select the Control-M/Server option and continue with the on-screen instructions until the upgrade is complete.
   • Automatic upgrade: Create a parameter file and then run the automatic install in a non-interactive mode, as follows:
     1. Select the Control-M/Server option and continue with the on-screen instructions until the Summary window.

        NOTE: There is no confirmation to shut down Control-M/Server processes. It is done automatically.

     2. Click Generate and select the location to create the XML parameter file.
     3. Click Yes to quit the upgrade.

        A confirmation message appears.

     4. Click Yes.
     5. Copy the automatic upgrade parameters file to a network location that is accessible to all computers where you want to perform an automatic upgrade.
     6. Log in using a user ID that has Administrator permissions on the current computer.
     7. Ensure that the upgrade DVD is still in the DVD drive, and run the upgrade script, as follows:

        <source_path>\Setup_files\components\ctm\setup.sh -silent <xml_path>\<filename.xml>

   The upgrade log can be found at the following location:

   %temp%\BMC_Control-M_Server_<date-time>.log

   After you have upgraded Control-M/Server, you need to run a script that removes the Log4j v2 vulnerability, as described in 000391322.