What's new 
We are trying to clean up FileVault compliance for a large group of managed Macs. Some devices have FileVault disabled, while others already have FileVault enabled but do not seem to have the personal recovery key escrowed in Hexnode. Previously, we were using a manual script-based process after assigning a FileVault policy, but the results were inconsistent.
Sometimes FileVault stayed off in System Settings, sometimes the device showed as encrypted but still non-compliant, and in a few cases users had issues after restarting. What is the recommended way to handle both types of Macs: devices where FileVault is disabled and devices where FileVault is already enabled but the recovery key is missing?
10 Views
