Got a weird one. BitLocker policy pushes successfully from Hexnode, no errors or anything, but some laptops still show “Not Encrypted”. Anybody seen that?
Devices getting BitLocker policy but encryption never actually startsSolved
Tags
Replies (6)
Yep. Check the TPM status first. We had a bunch of systems where TPM was technically there, but not actually ready. BitLocker just sat there doing nothing.
Run this:
|
1 |
Get-Tpm |
Look at TpmPresent and TpmReady. If Ready says false, that’s usually the problem.
Also check:
|
1 |
manage-bde -status |
Super helpful for seeing whether BitLocker even started the protection process or not. We normally run both through Hexnode terminal before touching the policy itself.
Just checked one of the devices.
TpmPresent : True
TpmReady : False
So yeah looks like that’s it.
Yeah that’ll block silent encryption.
We fixed most of ours with:
|
1 |
Initialize-Tpm |
Some machines needed a reboot after that, but most started working fine.
We actually made a small remediation script for this later. Checks TPM state, initializes it if needed, then lets BitLocker continue normally. Pushed it through Hexnode so we didn’t have to remote into every single device manually.