Skip to content

Disk encryption and recovery keys

Oneleet MDM can require disk encryption on managed Macs and Windows PCs, and it saves each device’s recovery key so an admin can get someone back into a locked device.

FileVault (macOS) BitLocker (Windows)
Require it Configuration Profiles > macOS > FileVault Configuration Profiles > Windows > BitLocker
See the recovery key Encryption key on the device’s page Encryption key on the device’s page
Replace the recovery key On the Mac, in Terminal Manage device > Rotate BitLocker recovery key…

Admins can reveal recovery keys, and each reveal is recorded in your workspace’s audit log.

In the macOS policy, turn on Enable FileVault. A Mac that isn’t encrypted prompts the person using it to turn FileVault on at their next logout or restart, and the Mac sends its recovery key to Oneleet.

Open the Mac’s page and click the eye icon next to Encryption key.

A Mac sends its recovery key only when the key is created. If FileVault was already on before the Mac enrolled, Encryption key shows Not escrowed and the page asks you to rotate the key.

On the Mac, run:

Terminal window
sudo fdesetup changerecovery -personal

Enter the password of an account that can unlock FileVault. The old recovery key stops working. Oneleet can take up to three days to receive the new one.

The Oneleet Agent shows the same request on the Mac under Needs your attention. For an administrator, its Open Terminal button runs the command. For the next three days, the agent shows Waiting for Oneleet to receive your new key instead of the button, since running the command again would replace the key just saved.

On a standard account, the agent asks the person to contact their IT team, since the command needs an administrator account.

On the Mac’s Activity tab, filter for FileVault recovery key saved or FileVault recovery key couldn’t be saved. A Mac whose key has to be rotated produces neither, because it doesn’t send a key until it’s rotated. If saving keeps failing, keep the Mac online and contact Oneleet support. Activity entries never include the recovery key.

Oneleet keeps the key it saved before and labels it Saved before re-enrollment; not yet reconfirmed. The key usually still works. If the Mac was wiped or its key was rotated, it doesn’t. Rotate the key as above to save a current one. If the key stays unconfirmed, contact Oneleet support.

BitLocker management is in early access. Ask your Oneleet contact to turn it on. A device needs Oneleet Agent 2.6.0 or later and Windows Pro, Enterprise, or Education. It also needs a TPM, unless its drive already unlocks with a PIN, startup key, or password. Devices that don’t meet these aren’t encrypted, and their disk encryption check keeps failing.

In the Windows policy, turn on Require BitLocker on the system drive. On each managed device, the agent saves the recovery key to Oneleet first and then encrypts the drive in the background. Nobody has to restart or do anything.

Setting What it does
Encryption method XTS-AES 256 by default, or XTS-AES 128
Encrypt used space only Faster. Data deleted before encryption stays recoverable.
Resume suspended protection Turns protection back on an hour after someone suspends it indefinitely
Block writes to removable drives BitLocker doesn’t protect Makes unprotected USB drives read-only

A drive that’s already encrypted stays encrypted with the method it has. Oneleet saves its recovery key.

Open the device’s page and click the eye icon next to Encryption key.

  • Uses XTS-AES 128, not the XTS-AES 256 the policy asks for: the drive was encrypted before the policy reached it, often by Windows itself during setup. To move it to the policy’s method, run manage-bde -off C: in an elevated prompt on the device. Once the drive is decrypted, the agent encrypts it again with the policy’s method and saves a new recovery key. The drive isn’t protected until encryption finishes, which can take hours. If Group Policy requires a method, Windows uses that one.
  • Secure Boot is off, so a firmware update can ask for the recovery key: shown for a drive that unlocks with its TPM. Windows Update and many vendor updaters suspend BitLocker for that restart themselves. For one that doesn’t, run Suspend-BitLocker -MountPoint C: -RebootCount 1 in an elevated PowerShell before updating. Windows resumes protection after the restart, and Resume suspended protection leaves that kind of suspension alone.
  • Saved from a recovery password Oneleet didn’t create: the person using the device or another system may hold this key too. Rotate it so only Oneleet holds the key.
  • Not the current key: the device’s latest report doesn’t include the saved key, so it may not unlock the drive. Right after a rotation, this shows until the device next reports in.
  1. Reveal the key on the device’s page before the person starts typing it. The BitLocker recovery screen may turn the device off after about a minute without input. Turning it back on brings the screen back.
  2. Check that the Recovery key ID on the device’s screen matches the first 8 characters of the key ID under Encryption key.
  3. Type the 48 digits on the device. The screen adds the dashes.

Once Oneleet holds a key for the device, open it and choose Manage device > Rotate BitLocker recovery key…. The agent creates a new key, saves it to Oneleet, and removes every other recovery key from the drive, so copies saved to Active Directory or Microsoft Entra ID stop working.

  • Only the system drive (C:) is managed.
  • Turning the requirement off, or excluding a device from MDM, doesn’t decrypt anything.
  • A startup PIN can’t be set remotely.