RSA File Security Manager (FSM)
Microsoft Windows Server 2003 SP1
The folder in this case is not in use. Data in one folder called c:|Private, and Test data in c:\test-private. Can not encrypt c:\Private folder.
In FSM 2.1.0.9, there is a known issue that Security Officer can not encrypt a folder containing ReadOnly files/folders and is addressed in v2.2 and higher. Contact RSA Customer Support for latest version 2.2 of FSM.
Alternative workaround:
- Encrypt an empty folder e.g. c:\private\test\
- Copy the files and folder from c:\private\accounts_public\ to the encrypted folder i.e. c:\private\test\
- Rename the source folder c:\private\accounts_public\ to desired name and rename the encrypted folder (c:\private\test\) to c:\private\accounts_public\.
- Refresh the Adapter Manager Console using Refresh button far right in the right pane.
- User can delete the renamed source folder (unencrypted) after confirming that all data is intact in encrypted folder c:\private\accounts_public\
Related Articles
When configuring fob-style token profile, the token is configured as PINPad-style when using RSA Authentication Manager 8.… Number of Views 'com.rsa.authmgr.admin.tokenmgt.ListTokensByPrincipalCommand execution' error when trying to assign a token on RSA Authent… Number of Views Quick Setup Guide - Cloud Access Service RADIUS Clients - Step 5: Add an Access Policy Number of Views StealthAUDIT hosts have a status of Offline in RSA Identity Governance and Lifecycle Number of Views What are the specifications for RSA SecurID Standard Token Card Pinpad token and Key Fob tokens? Number 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
