I'm doing an upgrade from version 14.0 to 14.6. Anyone have any feedback or gotchas on the process to share?
As stated in r14.6 Bookshelf:
"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."
In my case, version upgrade went smooth. A little reminder: For safe play, you may backup your CMS configurations. I hope won't experience any hurdles.
Thanks. I always backup configs first, or checkpoint VM's if possible. At which stage did you run migreg.exe, as the product names changed?
In my case upgradation was performed in test environment (CMS,database,iConsole and PE etc. on single machine) using setup.exe, so need for product reg keys manual migration wasn't felt.
Thanks. I'm kicking off an upgrade on Monday IN QA but have to document each step for each component next week.Thought MigReg.exe was needed to bump the registry from 'CA DLP' to 'CA DataMinder' prior to installation.
Why are you upgrading to 14.6? why not 15.0?
If you had already been testing 14.6 for months, I would understand as you would need to re-test everything.
But it sounds like you are only just starting the testing process. 14.6 would come to EOL sooner than 15.0 and force the need for another upgrade.
Surely this is poor value for the customer...
Retrieving data ...