This procedure describes how to upgrade from Control-M/Agent 8.0.00.500 and higher to the latest version of Control-M/Agent on Windows. If you want to upgrade multiple instances of Control-M/Agent on several computers using the same configuration, use the automatic upgrade, as described in this procedure.
NOTE: This procedure upgrades Control-M/Agent locally. To deploy and upgrade multiple Control-M/Agents from the CCM, see Control-M/Agent deployment.
NOTE: You can only upgrade Control-M/Agent with no down time from version 9.0.00.200
Before You Begin
Ensure that your operating system and database software is compatible with the new version of Control-M/Agent, as described in Control-M/Agent system requirements.
To upgrade Control-M/Agent on Windows:
NOTE: There is no confirmation to shut down Control-M/Agent processes. It is done automatically.
A confirmation message appears.
The automatic upgrade XML parameters file that is created (<filename>.xml) is relevant only for computers with the same agent instance name. Otherwise, a separate <filename>.xml file must be created for each computer, or modified manually for each computer.
<source_path>\Setup_files\components\agent\setup.exe -silent <xml_path>\<filename.xml>
The upgrade log can be found at the following location:
%temp%\BMC_Control-M_Agent_<date-time>.log
After you have upgraded Control-M/Agent, you need to run a script that removes the Log4j v2 vulnerability, as described in 000391322.
Parent Topic |