|
Title |
Description |
|
Unhandled exception in HudsonLake.exe when required DLLs are missing |
Application may exit with unhandled exception if the names of libraries are changed.
|
|
Remote Encryption Management test engine GUI may encounter intermittent ungraceful exits |
Application may experience rare ungraceful exits when unlocking many systems. |
|
Switching between EOI and WSMan in same session causes error |
The application will generate an “error starting service” message if switching between EOI and WSMAN in the same Remote Encryption Management session. Requires closing and restart the application before switching between EOI and WSMAN. |
|
Application incorrectly indicates that secure erase is successful when user password is provided to erase the drive |
Application correctly indicates that only admin passwords can be used when a user password is provided to securely erase a drive. The application then incorrectly indicates the drive was successfully erased when it was not successful. |
|
When unlocking some Opal* drives with an invalid password, the application provides an incorrect error status code |
The Remote Encryption Management test engine GUI reports error status code of “Invalid_parameter” when an unlock is attempted on some Opal* drives with an invalid password. |
|
Changing the client system security mode may require re-start of the test engine GUI. |
If the security mode of a client system is changed while the test engine GUI is active it may be necessary to re-start the test engine GUI to be able to successfully connect to the modified client. |
|
Unlocking a client with zero drives does not automatically stop the test engine GUI from attempting an unlock. |
It is possible to request an unlock operation in the Test GUI on a client with 0 drives. The Test GUI will start a remote encryption management session and will return an error for that client system unlock status. |
|
Copyright © 2006-2012, Intel Corporation. All rights reserved. |