Hello Cubert,
Thank you for the response and details, really do appreciate it! I updated Bitlocker for Automate to version 1.0.0.9 a couple of hours ago, as you suggested. I also had CW Automate support reboot my server and clear some cache, it is running much faster now and the Bitlocker tab loads in a little over a minute (I'm good with that).
In regards to Bitlocker and its use of the TPM to generate and securely store a recovery key, my understanding is that as long as there are no sort of boot-up/ hardware/ software/ OS changes with the computer, the computer boot-up process and access to the encrypted drive is transparent and seamless from the end-user perspective (sounds like the recovery key is fetched from the TPM during boot). However, if for some legitimate reason, something changes with the computer, the user will likely need to use a Bitlocker recovery key as a failsafe to access encrypted volume data. How can we use Bitlocker for Automate to store that recovery key in Automate - this is something of a "Break Glass in Event of Emergency"
Key Used Only When Boot Measurements are Accurate
https://docs.microsoft.com/en-us/window ... es-the-tpm
Interesting you mentioned the lock images, I am also experiencing that even after the 1.0.0.9 update. I select several agents without selecting the drive and can see that there are encrypted volumes. However, I don't see a gold lock or anything where the recovery key is suppose to populate. I'll keep an eye on it for next 24-48 hours and see if something changes. However, if there is anything you would like me to check or send you, please let me know.
I have images, but not sure how to include them in this posting
