The Jamf Pro GUI allows you to automatically set up the necessary payloads to manage the FDE Recovery Key Escrow process for macOS 10.13+.
However, the settings reside in the "Security & Privacy" grouping within the Jamf Pro GUI, forcing you to manage settings other than those related to recovery key escrow. You may inadvertently lock your users out of being able to make changes to the firewall, analytics settings, screen saver password requirement, etc.
You can upload a custom profile to the Jamf Pro Server that manages only FDE Recover Key Escrow preferences, but it takes a little work.
You'll also need to sign your resultant configuration profile to prevent the Jamf Pro Server from manipulating its contents or preventing deployment. You can use an Apple Developer certificate, or your Jamf Pro Server's CA (if self signed).
-
Create a temporary configuration profile for doing this setup. Name it something disposable – you'll delete it when done. "TEMP - FDERKE Setup" works. Set the level to "Computer level." Make sure you do not add a scope to the profile; we're not deploying it.
-
Click the "Security & Privacy" group, then click "Configure." Select the "FileVault" tab. Apply these preferences:
- ☑️ Enable Escrow Personal Recovery Key
- Escrow Location Description: Describe where the recovery key is being shipped. This is visible to the end-user, so "My Company IT" or whatever is appropriate. We'll edit this elsewhere, so you can leave it blank.
- Device Key for Escrowed FileVault Recovery Key: Text displayed at the FileVault unlock screen when a user has apparently forgotten their password. Despite the help text, you should leave this blank. By default it will be replaced with the device's serial number which will aid your technicians in recovering the correct key.
- Personal Recovery Key Encryption Certificate: Set to "Automatically encrypt and decrypt recovery key."
-
Save the profile, then click the "Download" button.
-
Next we'll convert the profile to a useable format. In Terminal, run these commands:
/usr/bin/security cms -D -i /path/to/downloaded/profile.mobileconfig -o /path/to/de-signed.mobileconfig plutil -convert xml1 /path/to/de-signed.mobileconfig -
Copy the
template-fde-recovery-key-escrow.mobileconfigincluded in this gist to a new file in your favorite text editor. Change the values ofPayloadOrganizationandLocationas needed. -
Open the de-signed profile originally downloaded from the Jamf Pro Server in your text editor. Find the
PayloadContentbelowPayloadCertificateFileName– it's the big, obvious block of certificate data. Copy and paste this to the same location in your editedtemplate-fde-recovery-key-escrow.mobileconfigfile, making sure you get the indentation correct. Save this file with a suitable name likeFileVault Recovery Key Escrow.mobileconfig. -
Sign the new profile thusly:
/usr/bin/security cms -S -N "Common Name of signing certificate in your keychain" -i /path/to/FileVault\ Recovery\ Key Escrow.mobileconfig -o /path/to/Signed-FileVault\ Recovery\ Key\ Escrow.mobileconfig"Common Name of signing certificate in your keychain" refers to any signing certificate in your login or System keychain.
-
Delete the temporary configuration profile from your Jamf Pro Server.
-
Upload your completed
Signed-FileVault Recovery Key Escrow.mobileconfigprofile to your Jamf Pro Server, then set an appropriate scope and deploy it.
Thanks to @opragel for the template/example configuration profile.
Unfortunately this no longer works. The profile results in 2 errors and won't save. Based on testing, the PayloadContent "Security And Privacy" is required. Removing everything else saves but when you download the profile everything is back. Any ideas?