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
SAML 2.0 Requirements for Service Providers Number of Views Set Requirements for Security Questions Number of Views The documentation for enabling the RSA Database Security Manager adapter for SQL Server 2005 discusses the requirement for… 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 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
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device How to replace the RSA Authentication Manager self signed console certificate with a signed certificate from Microsoft Act… RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide How to Request Access to the RSA Authentication Manager AMI for AWS via RSA Support
