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

Create a technical support case if you need further support.

Transferring Control Manager (TMCM) agents from an old TMCM server to a new server via AgentMigrationTool.exe

    • Updated:
    • 15 Oct 2015
    • Product/Version:
    • Control Manager 6.0
    • Platform:
    • Windows 2000 Advanced Server
    • Windows 2003 Datacenter Server
    • Windows 2003 Enterprise
    • Windows 2003 Enterprise Server
    • Windows 2003 Server R2
    • Windows 2003 Standard
    • Windows 2003 Standard Server Edition
    • Windows 2008 Enterprise
    • Windows 2008 Enterprise 64-bit
    • Windows 2008 Server R2
    • Windows 2008 Standard
    • Windows 2008 Standard 64-bit
Summary

Use the AgentMigrationTool to move TMCM agents from an old server to a new one.

Details
Public

AgentMigrationTool.exe works if the destination TMCM server has a version equal or higher than the source server. The tool can only migrate the following:

  • MCP-based agents
    • PortalProtect
    • ScanMail for Exchange
    • OfficeScan
    • InterScan Messaging Security Suite
    • InterScan Messaging Security Virtual Appliance
    • InterScan Web Security Suite
    • InterScan Web Security Virtual Appliance
    • IM Security
    • ServerProtect for Linux
    • ScanMail for IBM Domino
  • TMI-based Windows agents
    • ServerProtect 5.8 for Windows / Netware
    • ServerProtect 5.8 for Netapp Filer
    • ServerProtect 5.8 for EMC Celerra

To transfer TMCM agents to a new server:

  1. Ensure that the old TMCM server is still online.
  2. Make sure that the new TMCM version is installed on the new server with a new IP address or fully-qualified domain name (FQDN).
  3. Create the same TMCM account that was used to register the TMCM agents in the source server.
  4. Run AgentMigrationTool.exe directly on the destination server from the following location: <root>\Program Files\Trend Micro\Control Manager\
  5. Select the old TMCM server as the source server and then log in using an account with administrative privileges.
  6. In the Destination field, select the target TMCM server.
  7. Select the option Retain Tree Structure and Migrate Logs and then click OK.
     
    Failing to do Steps 8 to 12 will cause all of the Status Logs to show as "0".
  8. Enter the login details for each TMCM agent. Use an account with administrative privileges on the TMCM agent machines.
  9. Once the AgentMigrationTool.exe has finished, stop all TMCM services.
  10. Recount all the virus logs by doing the following:
    1. Go to the ..\Control Manager folder and run CMMaintainingTool.exe.
    2. Select all the options under the Recount the Control Manager Server Logs section.
    3. Under Packet Virus logs, click Recount Now. You may purge abnormal or duplicate communicator statuses.
    4. Run the RecountIMSSData.exe tool if IMSS is an entity in your TMCM program. Skipping this step will cause issues with IMSS reports.
  11. Start TMCM services.
Premium
Internal
Rating:
Category:
Migrate
Solution Id:
1031832
Feedback
Did this article help you?

Thank you for your feedback!

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.

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.


Need More Help?

Create a technical support case if you need further support.