Microsoft Windows Server 2003 SP2
Moving FSM encrypted files from one hardware platform to another
The plan is to image the existing server, power it off, then drop the image on the new hardware with a SAN. Since it is an image, it will retain the encryption old key. Then will encrypt the new folder created on the SAN drive without any changes.
Here is recommendations:
Have new system setup and create an encrypted folder using same key
Since using same KEY for encrypting the new folder, use the policy ?Read-Encrypt? and "Write-DoNot-Encrypt" for Robocopy application. Here the copy operation is fast because there is no penalty of Decrypting and Encrypting data again.
After everything is copied over for the FSM Adapter, you will have same keys available.
Note: It is still recommend having backup of data and metadata files. With standard installation, they will be under "C:\Program Files\RSA Adapter Manager Common\DataFiles\ "
Related Articles
How to resolve ORA-22285 error thrown in the Data Archiving process of RSA Identity Governance & Lifecycle 29Number of Views AFX Requests fails to process as the Usage Store Manager is full in RSA Governance & Lifecycle 163Number of Views What is the Return Merchandise Authorization (RMA) process for SID800 tokens? 138Number of Views Data Purging process (as part of Data Archiving) fails with ORA-01722 in RSA Identity Governance & Lifecycle 208Number of Views Users unable to authenticate with LDAP password on both Security Console and Self-Service Console for RSA Authentication M… 207Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x