Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Installing Control Manager (TMCM) on a cluster server

    • Updated:
    • 15 Apr 2021
    • Product/Version:
    • Control Manager 6.0
    • Platform:
    • Windows 2008 Enterprise
    • Windows 2008 Server R2
    • Windows 2008 Standard
Summary

Learn how to install Control Manager (TMCM) on a Microsoft 2008 R2 Cluster Server.

Details
Public
  1. Build the Windows 2008R2 cluster. To get more help, check this article: Guide to Creating and Configuring a Server Cluster under Windows Server 2008R2.
  2. Build the SQL Server 2008R2 failover cluster. To get more help, check this article: Guide to Creating and Configuring a Microsoft SQL Server 2008R2 Failover Cluster.
  1. Install TMCM on shared-disk both for node 1 and node 2.

    Nodes

    1. Make sure TMCM is on both nodes.

      Click Yes to install Visual C++ Redistributable Package

      Visual C++ 2005 Redestributable Package

    2. Install your prerequisites.

      Click Next

      Question

    3. Select the shared-disk to install TMCM physical files.

      Select the shared-disk

      Enter the Activation Key

    4. Choose Feedback option, and then click Next for the Host Address of TMCM.
    5. Enter the Cluster virtual name (created in Windows 2008R2 cluster service) as FQDN or use Virtual IP.

      Click Next

      Click Next

      Choose Destination Location

      Set up Control Manager Database

    6. Set TMCM services to Manual Startup Type.

      Set TMCM services to manual startup type

    7. Copy files the following files from Control Manager folder to CmBackup folder after the first TMCM cluster node installation completes:
      • Schema.dtd
      • Schema.xml

        Copy the files

    8. Start the installation on Node 2.

      Start the installation on Node 2

      Select Destination Folder

      Click Next

      Select an option

      Click Yes to continue

      Click OK 

  2. Import key for ASP.net
    If the first node installs first, followed by the 2nd node, the web.config file will be overwritten by the 2nd cluster node. Furthermore, key to use for the ASP.net will be based on the 2nd node and not the 1st node.
    1. Exporting RSA key first from 2nd cluster node
      1. Logon to the 2nd node.
      2. Open the command prompt as “administrator”.
      3. Run the command below to export RSA key under Windows\Microsoft.Net\Framework\v2.0.50727\ directory:

        aspnet_regiis.exe –px “NetFrameworkConfigurationKey” “c:\keys.xml” –pri

    2. Create a copy “c:\keys.xml” to be used for the 1st cluster node.
      1. Import the RSA key for the 1st node.
      2. Shutdown the 2nd node, and then start up the 1st node to import the RSA key from 2nd node.
      3. Open the command prompt as “administrator”.
      4. Run the commands below to import RSA key under Windows\Microsoft.Net\Framework\v2.0.50727\ directory:

        aspnet_regiis.exe –pi “NetFrameworkConfigurationKey” “c:\keys.xml”

    3. Restart the World Wide Web service in Cluster.

      Select Service or Application
      Generic Script Info
      Client access point

      1. Add the following Trend Micro Resources to the new TMCM Service and Application in the cluster resources:
        • TMCM
        • TMCM CCGI
        • TMI

        Select Service

        Client access point

Premium
Internal
Partner
Rating:
Category:
Configure; Deploy; Install
Solution Id:
1060869
Feedback
Did this article help you?

Thank you for your feedback!


*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.