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
Using PING to backup RSA Authentication Manager 8.2 and receiving error CIFS VFS: Error -32 sending data on socket to server Number of Views What to do after receiving a Clickatell test message when configuring Clickatell SMS for On-Demand Authentication with RSA… Number of Views Run sdadmin or sdlogmon without receiving the error message 'This account does not have permission to access the log datab… Number of Views Installing rsaservmgr scripts [exec] error reading information on service rsaservmgr error when installing RSA Web Tier o… Number of Views Missing sdconf.rec file causes SecurID to fail on Raptor Firewall Number of Views
Trending Articles
RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide View Transfer Tokens to Cloud Jobs RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide How to Upgrade Internal SHA-1 Certificates to SHA-256 in Authentication Manager Using rsautil RSA Release Notes for RSA Authentication Manager 8.8
