RMMZit 0.6.2 — BitLocker recovery keys and policy, and the REST API.
New
- BitLocker recovery keys: the server reads the recovery keys of every Windows device with BitLocker once a day (or at once from the device's BitLocker page, linked from the device overview) and keeps them encrypted. Only administrators can show a key, after entering their password; every key shown and every wrong password is in the audit log.
- BitLocker by policy: a policy can require BitLocker on the system drive. The agent first checks the TPM and adds a recovery key, the server stores it, and only then does the encryption start (TPM, XTS-AES 256, used space only) — also for Windows 11 device encryption that is waiting for activation. Devices without a ready TPM, with a Windows edition without BitLocker or with bootable media in the drive show the reason under Activity. Administrators can also switch it on for one device.
- REST API at
/api/v1with personal tokens (My account → API tokens): a token acts as its user, with a role no higher than the user's, and is shown once. Read devices, inventory, alerts, tasks, jobs, the software library and policies; start tasks on devices (scripts, Windows Update search and installation, winget, Chocolatey, restart, agent update, BitLocker keys), follow and cancel them, install library packages and assign policies. Every change is audited with the token's name. Reference in the console under Documentation → API.
Updating
Settings → RMMZit updates installs 0.6.2 from GitHub. Agents update themselves (Settings → Agent updates); BitLocker needs agents 0.6.2.
