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
ODA (on demand access) token.will not authenticate when connecting thru a Netscaler VPN Gateway 57Number of Views FortiGate Firewall - RADIUS Configuration Using SSL VPN - RSA Ready Implementation Guide 87Number of Views Moving users across security domains using RSA Authentication Manager Bulk Administration (AMBA) 173Number of Views A Request Workflow in the Canceling state does not move to the Cancelled state in RSA Identity Governance & Lifecycle 415Number of Views FortiGate Firewall - Configure RADIUS Authentication Manager Using SSL VPN - RSA Ready Implementation Guide 121Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process RSA Release Notes for RSA Authentication Manager 8.8 RSA RADIUS Server service failed to start in the RSA Authentication Manager 8.1 Operations Console Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide RSA Release Notes: Cloud Access Service and RSA Authenticators