Control-M/Enterprise Manager clients installed with client distribution do not configure SSL on the client when the web server is configured with HTTPS causing the client to fail to connect with message: "Can't connect to Naming Server"

Knowledge Article

Control-M/Enterprise Manager clients installed with client distribution do not configure SSL on the client when the web server is configured with HTTPS causing the client to fail to connect with message: "Can't connect to Naming Server"
Control-M/Enterprise Manager clients installed with client distribution do not configure SSL on the client when the web server is configured with HTTPS causing the client to fail to connect with message: "Can't connect to Naming Server"
Control-M/Enterprise Manager
Control-M/Enterprise Manager
Control-M/Enterprise Manager 9 with client SSL and HTTPS enabled
Control-M/Enterprise Manager clients installed with client distribution do not configure SSL on the client when the web server is configured with HTTPS causing the client to fail to connect with message: "Can't connect to Naming Server"
CAR00136539 - cannot connect to the Control-M client if it was installed with Client Distribution when the Web Server is configured with HTTPS
This issue is addressed by CAR00136539, which in available in Control-M/Enterprise Manager 9.0.00.512.

To resolve this issue, please do the following:
  1. Install Control-M/Enterprise Manager 9 Fix Pack 5, available here: ftp://ftp.bmc.com/pub/control-m/opensystem/CONTROL-M_Enterprise_Manager/9.0.00/PANFT.9.0.00.500/
    • Following the installation instructions for the appropriate platform included in the PDF
  2. Install Control-M/Enterprise Manager 9 Patch 512, available here: ftp://ftp.bmc.com/pub/control-m/opensystem/CONTROL-M_Enterprise_Manager/9.0.00/PANFT.9.0.00.512/
    • Following the installation instructions for the appropriate platform included in the PDF
    • Note that Fix Pack 5 is a prerequisite of Patch 512 and must be installed before attempting to install patch 512
  3. Ensure that the hostname value in Client_Updates/conf/web_server_parameters.xml on the Control-M/Enterprise Manager matches exactly the Subject Common Name (CN) that is in the certificate in use on the Control-M/Enterprise Manager's web server.
  4. Ensure that the certificate in use by the Control-M/Enterprise Manager's web server is trusted by Windows installation where the Client Deploy installation will be run. This may require importing the Certificate of the Signing Authority that generated the web server's certificate into the Windows Trusted Root CA keystore.
    • Consulting with the Windows System Admin team for assistance with this process may be required for some environments
  5. Using a working Client installation, log in to the Control-M Configuration Manager (CCM) and follow the below steps:
    1. select the "Manage" tab, and click the "Client Distribution" button
    2. In the resulting window, choose Fix Packs on the left hand side
    3. In the "Distribute Control-M Workload Automation client version" drop down, choose 9.0.00.500 and click OK
  6. Test a new Client Deploy installation
    • a new message should be shown indicating that Fix Pack will be installed on the client following the installation of the base client, this indicates that the change was successful
    • It is recommended to uncheck the "Launch Workload Automation" check box so that the Fix Pack installation can run unimpeded.
Control-M/Enterprise Manager
Control-M/Enterprise Manager
Control-M/Enterprise Manager 9 with client SSL and HTTPS enabled
Control-M/Enterprise Manager
Control-M/Enterprise Manager
Control-M/Enterprise Manager 9 with client SSL and HTTPS enabled
Attachment(s):