Platform Deployment Guide › Known Issues (Deployment) › General Deployment › CFSA Can Prevent BitLocker From Encrypting USB Devices

CFSA Can Prevent BitLocker From Encrypting USB Devices

The Client File System Agent (CFSA) can affect the operation of the BitLocker To Go encryption feature on endpoint computers.

If the CFSA is installed on an endpoint computer and configured to apply policy to files being copied to removable devices (such as USB drives or SD cards), BitLocker cannot initialize removable devices for encryption. That is, it cannot give these devices the "lockdown treatment". This is because the BitLocker initialization process is denied write access to the device by the CFSA.

Note: This problem only occurs if the CFSA is explicitly configured to apply policy to removable devices. Also, if a removable device has been initialized by BitLocker running on a different computer, the device can used on any endpoint computer hosting the CFSA, even if the CFSA is configured to apply policy to removable devices.

RDM, EAS and Windows 2003

This is a test you can run to confirm that CA DataMinder console users can retrieve e‑mails archived in the Zantaz Exchange Archive Solution (EAS).

1. On the Remote Data Manager (RDM) server, ensure that you are logged on to Windows with the same logon account as that used by the CA DataMinder infrastructure service (wgninfra.exe).
2. Open Internet Explorer and use the following URL to browse to EAS:

   http://<EASWebServer>/EAS_APP
     /easweb.dll?ServerGetMsg&msgid=
     <MSGID>&serverID=<ServerID>&compressed=0
   

   where:

   <EASWebServer>

   Is the name or IP address of the EAS IIS server.

   <MSGID>

   Is the numerical EAS message ID to be retrieved.

   <ServerID>

   Is the numerical ID of the EAS server containing that message.

   If Internet Explorer can retrieve a .MSG file from EAS in this way without being prompted for Windows credentials, then it will also be possible for RDM to do so.