Before you upgrade CA Data Protection, 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 Data Protection in the current release. In parallel with this product name change, the registry key used by CA Data Protection components has also been renamed.
HKEY_LOCAL_MACHINE\SOFTWARE\Orchestria\Active Policy Management
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA DLP
HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA DataMinder
Do I Need to Manually Migrate Existing Registry Keys?
If you upgrade any pre-14.1 CA Data Protection computer by running setup.exe, the CA Data Protection installation wizard automatically migrates the existing product registry key to the new CA Data Protection registry key.
However, if you plan to upgrade CA Data Protection 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 Data Protection!
Specifically, before you upgrade any CA Data Protection server (including the CMS), endpoint computer or utility machine, use the migreg.exe utility to copy existing registry values to the new 'CA Data Protection' registry key. The upgrade is blocked if CA Data Protection detects that registry values have not been migrated to the new key.
To manually migrate existing registry keys
<path>\migreg
Where <path> specifies the migreg.exe location you chose in step 1.
<path>\migreg -p
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|