Why does the SES not have the new password and recovery key for Bitlocker after re-encrypting?

Scenario:

This article discusses an issue where decryption is made necessary through Bitlocker’s management tools, and the device is re-encrypted without removing SecureDoc.    

This can be due to a motherboard, or other hardware replacement.

Product version affected:

SD 6.5, 7.1, 7.5, 8.2, 8.3

Environment:

Windows 7, 8, 8.1, 10

Issue:

With a SecureDoc managed Bitlocker encrypted device, the new password, key package, and recovery key are not captured and sent to the SES.

Reason:

SecureDoc is not able to capture the new Password, Recovery key, or key package generated when a Bitlocker encrypted device is re-encrypted while Secure

Resolution:

Bitlocker should be decrypted, and SecureDoc removed, before installing SecureDoc and allowing it to activate Bitlocker.