Upgrade Guide › Upgrade Procedures › Recommended Upgrade Procedure

Recommended Upgrade Procedure

We recommend that you systematically work down the machine hierarchy, upgrading each parent server before you upgrade its child machines. This will minimize disruption to users, and prevent possible loss of policy changes. Indeed, this is essential if upgrading from version 5.0 and any database cleanup operations are needed.

To upgrade CA DLP

1. (Only required if upgrading from version 5.0 or 6.0) Migrate the old Orchestria registry keys.
2. Upgrade and then restart the CMS.

   Note: After upgrading your CMS, you will be unable to run searches or reports in the iConsole until it too is upgraded.

3. Upgrade and then restart the following CA DLP servers:
   • Gateways
   • Policy engines
   • Event import machines
   • Remote Data Manager machines
   • Quarantine Manager machines
4. Upgrade your iConsole servers and the standard iConsole searches and reports.
5. Upgrade your email server agents, including:
   • Exchange server agent
   • Domino server agent
   • Milter MTA agent
   • IIS SMTP agent
6. Upgrade other CA DLP components, including:
   • Integration agents
   • File scanning agent jobs
   • Universal Adapter
7. Upgrade and then restart your client machines

   If you plan to upgrade your client machines using a managed deployment method such as Group Policy, you must manually upgrade the parent gateway before upgrading the client machines.

   Note: For details on Group Policy deployments, see the Deployment Guide; search the index for ‘client machines, installation, Group Policy’.