Hi @ren_ben,
For a BitLocker recovery key to appear in the Device Summary, the policy must be applied to the correct device and the device must complete BitLocker encryption.
If a Windows policy remains in Pending, first confirm that the policy is assigned to the active device record. A stale or incorrect device entry can keep the policy status pending because the device is not checking in.
Recommended checks:
- Confirm the target Windows device has checked in recently.
- If the device is online but the policy is still pending, run a Scan Device action.
- If the scan does not complete, restart the Windows device and try again.
- Open the Hexnode agent on the device and use Sync, then run Scan Device again from the portal.
- Make sure the BitLocker policy is assigned to the correct device, not an older or duplicate device record.
After the policy is successfully deployed, the device still needs to be encrypted. Once the BitLocker policy has been applied, restart the Windows device. The device should then prompt for BitLocker encryption based on the configured policy.
If the encryption prompt does not appear after restart, you can initiate it from Hexnode:
- Go to the Windows device in Hexnode.
- Select Actions > Security.
- Choose Force BitLocker Encryption.
- Follow the on-screen instructions.
- Set the required password or PIN according to the policy requirements. In this case, use a minimum length of 8 characters.
After encryption is triggered and the recovery key is generated, the BitLocker recovery key should become available in the Device Summary.
Best Regards,
Isabel Lora
Hexnode UEM