EERM will not initialize or detect a Blackberry Storm, Sprint Treo, and other smartphones? I thought that EERM detects all removable media regardless if a drive letter is assigned or not. The memory or media SD card on a BB Storm is not detected by EERM. I can still write files and folders to these phones. These phones are listed under Other devices in Windows Explorer and a drive letter is not assigned. How can I make these phones read only when EERM will not work? I already have Make unprotected files and folders Read-Only (when used with EEFF). I cannot implement Device Control at this point.
Well I just learned that if you change the Auto Enable Mass Storage Mode When Connected to Yes than EERM will initialize and attempt protection of the device. I have not found this option yet on the Sprint Treos.
Probably answering my own question but I will have to implement Endpoint Encryption for Mobile to protect Sprint Treos and Windows Mobile devices.
Will this be a feature in EE v6.1.x? Or is this a protection under Device Control?
not sure what your question is - do you want to prevent attachment of them (device control), encrypt data on them natively (EEMO), or encrypt the storage on them when plugged into a PC (EERM)?
Correction. Forcing encryption on BlackBerries and other Smartphone/PDAs is a bad idea for my organization. I would like EERM to make these devices Read Only if the user decides not to encrypt.
Unfortunately the devices are recognized by Windows under Other or Portable Devices. It is not recognized as a device with removable storage but I can still access the memory/media card. I can write files to the device without the intervention of EEFF and EERM. I guess the only choice is have the user Encrypt (or self-extract) the files and folders before placing them on these devices.
Guess I will have to implement EE for Mobile for the Windows Smartphones and Device Control for the BlackBerries/MP3s.