Performing an Agent Migration

The following agent migration scenarios are possible:

• Single-server migration

  Migration of agents belonging to a single server
  You can use both Rapid and Phased migration modes in this instance. Trend Micro recommends the use of Phased migration for large Trend VCS networks.

• Consolidation of different servers

  Migration of agents belonging to multiple servers
  Separate Trend VCS servers handled the control functions that restricted user access to specific segments of the antivirus network. Now, new Control Manager access control features combine these control functions into a single Control Manager server.

• Remember to start the destination Control Manager server's Remote Registry service or agent migration will not be successful.

The following detail agent and MCP migration:

• Trend VCS 1.8x agent migration

  During Trend VCS 1.8x agent migration, the agent migration tool performs the following:

  1. Upgrades Trend VCS 1.8x agents to version 1.86.

  2. Removes Trend VCS 1.8x server information from the registry and replaces them with Control Manager 3.5 server information.

  3. Unregisters from the Trend VCS server and registers to the destination server.

  In an event when AgentMigrationTool.exe is unable to complete or finish a Trend VCS 1.8x agent migration, it removes Trend VCS agent from the Control Manager 3.5 server and re-registers them back to the Trend VCS server.

• Control Manager 2.5x agent migration

  During Control Manager 2.5x agent migration, the agent migration tool performs the following:

  1. Stops the Trend Micro Management Infrastructure service of the destination server.

  2. Obtains the Product Directory information from the Control Manager server.

  3. Retains the Control Manager agent version (no upgrade takes place).

  4. Writes the agent information to the database of the destination server.

  5. Unregisters the selected agents from the Control Manager source server and then registers them to the destination server.

  AgentMigrationTool.exe removes the agent information from the Control Manager 3.5 database when the Control Manager 2.5x agent migration cannot be successfully completed.

  6. Restarts the Trend Micro Management Infrastructure service of the destination server.

  7. Stops and then restarts the Trend Micro Control Manager service of the destination server.

• MCP migration

  During MCP migration, the agent migration tool performs the following:

  1. Stops the Trend Micro Management Infrastructure service of the destination server.

  2. Obtains the Product Directory information from the Control Manager server.

  3. Retains the Control Manager agent version (no upgrade takes place).

  4. Writes the agent information to the database of the destination server.

  5. Restarts the Trend Micro Management Infrastructure service of the destination server.

  6. Stops and then restarts the Trend Micro Control Manager service of the destination server.

  7. Requests the source server to issue a Change Server command and waits for polling by the MCP agent.

• When migrating agents Trend VCS and 2.5x agents migrate first, then MCP migrates.

If an agent migration is unsuccessful, the following occurs:

• The agent continues to be managed by the source server

• Agent logs are on both the  source and destination servers

Migrated logs will not show logs unless the agents are registered to the destination server. Destination CM server will purge migrated logs when purge is triggered.