SES/SecureDoc Enterprise Client have limitations on use of Crypto-erase specific to versions V6.4SR1 and V6.5. Please read to determine if you are impacted by this.
The following limitation applies ONLY to version V6.4SR1 and V6.5 of SecureDoc Enterprise Server and the SecureDoc Enterprise Server-managed Client software.
The use of Crypto-erase has limitations for hardware encrypted drives in our existing releases 6.4 SR1 and V6.5.
WinMagic will work diligently to address in the V7.1 release all the those cells in the tables below that contain "Not supported", and in early 2015 WinMagic will update this article to confirm the exact product version in which this will be fixed.
Until there is an updated SES version containing that correction, if you have any questions or concerns surrounding crypto-erase on self-encrypting drives then please contact WinMagic Technical Support.
SecureDoc for Windows managing a self-encrypting drive | Remote crypto-erase from SES (e.g. by Policy or Admin command) | ||
At Pre-boot | Once device has loaded OS | ||
PBL (Win7) | PBU (Win8) | ||
Not supported | Not supported | Supported | |
SecureDoc OSA managing a self-encrypting drive | Supported | Not supported | N/A |
SecureDoc for Windows managing a self-encrypting drive | Key sequence crypto-erase (F1 + F9+ F11 – configurable) | ||
At Pre-boot | Once device has loaded OS | ||
PBL (Win7) | PBU (Win8) | ||
Not supported | Not supported | N/A | |
SecureDoc OSA managing a self-encrypting drive | Not supported | Not supported | N/A |