Utilizing Content Protection - Real World Feedback
Posted 08-26-2009 at 05:00 AM by hdawg
Tags content protection
d_fisher posed a question about implementing Content Protection ... and we got some real world feedback.
Here's a quick glimpse at one response:
1. How does setting the rule to Strong/Stronger/Strongest effect the end-users experience? If slower, how significant is the slow down?
The response of the device on unlocking is MUCH slower on the Strongest setting. To unlock, when Content Protection is enabled, takes up to 7 seconds in my experience. On older devices (prior to Bold) the wiping of said devices takes up to 3 hours as well. so if a user forgets their password x number of times and it wipes, they are SOL for up to 3 hours. The device does however wipe, then scrub to DoD standards
2. Is the slow down all the time or only when unlocking the device?
There is a very small slowdown during operation at all times, though most users will not notice. The unlocking is the pain.
3. Does this effect the functionality of applications or BT devices?
I do not allow Bluetooth devices in my environment (excluding the CAC reader) so I cannot comment on this, though I seriously doubt Bluetooth would have any noticeable difference. (Encryption on BT is separate)
4. Does this cause any support issues? I know some previously existed.
The only one I have come across is the user wiping their device/complaining about the sluggishness to unlock. On devices not running 4.5+ and BES prior to 4.1.6, you could NOT reset the password for a user when content protection was enabled (could not translate plain text to encrypted text and back). These issues have been resolved with the above listed software versions.
... Check out the thread and provide any input you might have!
Here's a quick glimpse at one response:
1. How does setting the rule to Strong/Stronger/Strongest effect the end-users experience? If slower, how significant is the slow down?
The response of the device on unlocking is MUCH slower on the Strongest setting. To unlock, when Content Protection is enabled, takes up to 7 seconds in my experience. On older devices (prior to Bold) the wiping of said devices takes up to 3 hours as well. so if a user forgets their password x number of times and it wipes, they are SOL for up to 3 hours. The device does however wipe, then scrub to DoD standards
2. Is the slow down all the time or only when unlocking the device?
There is a very small slowdown during operation at all times, though most users will not notice. The unlocking is the pain.
3. Does this effect the functionality of applications or BT devices?
I do not allow Bluetooth devices in my environment (excluding the CAC reader) so I cannot comment on this, though I seriously doubt Bluetooth would have any noticeable difference. (Encryption on BT is separate)
4. Does this cause any support issues? I know some previously existed.
The only one I have come across is the user wiping their device/complaining about the sluggishness to unlock. On devices not running 4.5+ and BES prior to 4.1.6, you could NOT reset the password for a user when content protection was enabled (could not translate plain text to encrypted text and back). These issues have been resolved with the above listed software versions.
... Check out the thread and provide any input you might have!
Total Comments 0
