The utility runs during Control-M/Agent Fix Pack 3 installation and generates new keys to replace all BLOWFISH encrypted data as above Store the new key in data/keys/local.key Transform all locally stored encrypted data from a current key to a new key: If you didn't skip Control-M/Agent version 9 fix pack 3 and problem occurred installing Control-M/Agent version 9 fix pack 4 will not resolve the issue.ģ. If you skip Control-M/Agent version 9 fix pack 3, this problem will not appear after installing Control-M/Agent version 9 fix pack 4. From the release notes of PAKAI.9.0.00.400 where CAR00155392 is mentioned: This problem occurs when the AES key randomly generated by the Fix Pack 300 installation contains a particular byte.Ģ. Please check CAR00134526 in the Release Notes for 9.0.00.300. Control-M/Agent for UNIX and Microsoft Windows 9.0.00.300 has updated an encryption mechanism to AES256 from Control-M/Agent for UNIX and Microsoft Windows 9.0.00.200 (Blowfish). Rerun Control-M/Agent V9 ctmagcpk utility to update the AES encryptionġ. Solution 3: Regenerate the local.key and AES encryption on Control-M/Agent V9 FP3:ħ. Remove the "/data/cfg_backup\passwrds.bak" if foundħ. Navigate to /data/cfg_backup and ensure that there is none AES encrypted passwrds.bak fileĦ. Delete the local.key file (under data/keys)ĥ. Restore PASSWRDS.dat (Blowfish encrypted file from Control-M/Agent V9 FP2 or earlier) file from backupĤ. Restore REQUESTS.dat, UDA.dat, UDA_BMC.dat (under data) as Solution 1 aboveģ. Solution 2: Upgrade to latest Control-M/Agent V9 Fixpack:Ģ. Extract the attached (zipped) files to \data\ The local.key file should be deleted from the \data\keys\ directory, so the Agent will revert to Blowfish encryptionĢ. Keep the file in a safe location in case it is needed later. Move the \data\keys\local.key file to a different folder. Solution 1: Downgrade back to the previous encryption method.ġ. Please see further information on CDM's MSI parameters.Use one of the following solution to resolve this CAR if found after installing Control-M/Agent 9.0.00 Fixpack 3:ĬAR00155392 : AGENT FileWatcher jobs fails on Agent after upgrade to V9FP3 when AES local.key contains x'00' Please note all MSI parameters are case sensitive and need to be ALL CAPS. This can be auto installed with msiexec /i "C:\CDM\setupcdm圆4.msi" /qn INSTALLCDMFILEWATCHER=TRUE To enable this feature via manual install make sure this box is ticked during the install wizard (it is unticked by default). However for now if you wish to solve this problem, we've built a file watcher service that will automatically quietly refresh File Explorer whenever you make changes to our drives which means they'll automatically show any new files or file changes with the File Explorer window open. This is related to the drives current use of webdav and will not exist with our next generation V3 client. You might notice that when saving files to drives from a 3rd party application while you have File Explorer open, the file doesn't immediately appear and you have to hit right-click 'refresh' to see the file. This article relates to our product Cloud Drive Mapper. Modified on: Thu, 21 Apr, 2022 at 5:40 PM Solution home Cloud Drive Mapper Drive Mappings
0 Comments
Leave a Reply. |