Worked for me - hopefully this can be fixed. Are the JAMF devs not as close to Apple as they should be? (10.12.5 installer via Self Service anyone?) There seems to be a lot of things in the macOS now that the Casper/JAMF tools just don't handle well any more. That functionality was a welcome addition a few versions ago. It is very unfortunate that Composer can no longer capture the Recovery HD. After booting up I verified via diskutil list that there is now a Recovery HD partition and when I enabled FileVault, it worked just fine. However, if I take the 10.12.5 Recovery HD package this app creates and I put it in the imaging Config with a Priority 2 (the Macintosh HD has a Priority 1), the package installs correctly since during Netboot, the local hard drive is not ruled by SIP. This fails every time - apparently because of SIP. First I tried using Create-Recovery-Partition-Installer and installing the partition after the computer has been imaged without a Recovery HD. Using the above method, I have no issues in enabling FileVault 2 and remotely locking macs (also needs the recoveryHD) Create/update your configuration (in casper admin) to add a partition and use that new Recovery package you created.

Using Composer, 'Build OS Package', select the recovery HD only and create a new dmg package.Ĥ. Now mount the appropriate drive (mine is always 2s3): diskutil mount /dev/disk2s3ģ. Output will usually look something like this: JSS-BASE-3:~ admin$ diskutil listĢ: Apple_CoreStorage Macintosh HD 499.4 GB disk0s2ģ: Apple_Boot Recovery HD 650.0 MB disk0s3Ģ: Apple_CoreStorage Macintosh HD 250.1 GB disk2s2ģ: Apple_Boot Recovery HD 650.0 MB disk2s3Ģ. Get the Recovery drive identifier by listing all drives diskutil list If you choose to use Composer to make the images (like i do), then you have to mount the RecoveryHD first and then capture it separately.ġ.

Jamf mac create recovery partition