Previous Topic: Pre-Upgrade TasksNext Topic: Back Up and Suspend the CMS


Migrate Registry Values

Before you upgrade CA DataMinder, you may need to migrate the existing product registry keys.

Product Registry Key Has Been Renamed

CA Technologies is renaming its security portfolio to follow the Minder product family. In particular, CA DLP has been renamed to CA DataMinder in the current release. In parallel with this product name change, the registry key used by CA DataMinder components has also been renamed.

Do I Need to Manually Migrate Existing Registry Keys?

If you upgrade any pre-14.1 CA DataMinder computer by running setup.exe, the CA DataMinder installation wizard automatically migrates the existing product registry key to the new CA DataMinder registry key.

However, if you plan to upgrade CA DataMinder by running an .msi installer package directly (for example, server.msi or integration.msi), you must migrate the registry key manually before you upgrade CA DataMinder!

Specifically, before you upgrade any CA DataMinder server (including the CMS), endpoint computer or utility machine, use the migreg.exe utility to copy existing registry values to the new 'CA DataMinder' registry key. The upgrade is blocked if CA DataMinder detects that registry values have not been migrated to the new key.

To manually migrate existing registry keys

  1. Find migreg.exe in the \Support folder on your CA DataMinder distribution media. We recommend that you copy this utility to a suitable network location.
  2. Before you upgrade a CA DataMinder computer, run this command locally:
    <path>\migreg
    

    Where <path> specifies the migreg.exe location you chose in step 1.

  3. (Optional) After successfully upgrading all CA DataMinder components on a computer, run this command to purge the old Orchestria or CA DLP registry keys:
    <path>\migreg -p