Control Manager Installation Guide - Trend Micro? Online Help
Control Manager Installation Guide - Trend Micro? Online Help
Control Manager Installation Guide - Trend Micro? Online Help
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Upgrading Servers or Migrating Agents to <strong>Control</strong> <strong>Manager</strong><br />
Scenario 2: Migrating to a Fresh <strong>Control</strong> <strong>Manager</strong> 6.0<br />
<strong>Installation</strong> Using the Agent Migration Tool<br />
This scenario involves installing <strong>Control</strong> <strong>Manager</strong> 6.0 on a separate server from the<br />
existing <strong>Control</strong> <strong>Manager</strong> server. This method allows you to slowly decommission the<br />
previous server. See Planning <strong>Control</strong> <strong>Manager</strong> Agent Migration on page 4-10 for more<br />
information about migrating agents.<br />
Migrating a <strong>Control</strong> <strong>Manager</strong> 5.0/5.5 Server to a Fresh <strong>Installation</strong><br />
of <strong>Control</strong> <strong>Manager</strong> 6.0<br />
Procedure<br />
1. Back up the existing <strong>Control</strong> <strong>Manager</strong> 5.0/5.5 database.<br />
2. Perform a fresh installation of <strong>Control</strong> <strong>Manager</strong> 6.0 on a different computer.<br />
3. Use the Agent Migration Tool to migrate entities from the <strong>Control</strong> <strong>Manager</strong><br />
5.0/5.5 server to the <strong>Control</strong> <strong>Manager</strong> 6.0 server.<br />
Note<br />
The Agent Migration Tool only supports migrating managed products and managed<br />
product logs. The Agent Migration Tool does not support migrating reports or the<br />
Product Directory structure from the previous server.<br />
Scenario 3: Upgrading or Migrating a Cascading<br />
Environment<br />
<strong>Control</strong> <strong>Manager</strong> supports upgrading a cascading environment. To upgrade a cascading<br />
environment, unregister and then re-register the child <strong>Control</strong> <strong>Manager</strong> servers.<br />
Procedure<br />
1. Unregister all child <strong>Control</strong> <strong>Manager</strong> servers from the parent <strong>Control</strong> <strong>Manager</strong><br />
server.<br />
4-5