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
Error ?The password does not meet the password policy requirements'. when changing EnVision windows user account passwords Number of Views 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 Change Your Account Name and Password in the Cloud Administration Console Number of Views Error message "The underlying connection was closed: An unexpected error occurred on a send" when trying to run RSA Authen… Number of Views FIPS status of RSA Cloud Access Service components Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Unable to login to RSA Authentication Manager Security Console as super admin Manual synchronization introduced in RSA Authentication Manager 8.2 Service Pack 1 patch 6 Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to verify NTP server synchronization is not working in RSA Authentication Manager 8.x
