FileVault config and storing the key in JSS

Hi,

I think you won't be able to deactive FileVault as long as it has not been done activating it. So maybe it takes some time, depending on the size of the volume.

Regarding the reporting is the question which version of the JSS are you using and which version of macOS is running on the client? There were some changes with macOS 10.13.

Greetings,
Marco

Oh damn, I forgot that info. @mkolb latest JSS, 10.13 Macs. The Mac I tested on sat there for 15 hours or so, drive was encrypted but no key written to JSS. Deactivating issue was me not paying attention. I didn't unlock the preference pane to turn off FileVault, I am good now as far as deactivating does.

No problem.

With 10.13. it can be a little confusing as the "FileVault Recovery Key Redirection" payload in the configuration profile DOES NOT WORK!

Instead you have to use the Security & Privacy payload. At "File Vault" you can find an option called "Enable Escrow Personal Recovery Key". This is what you need. Enter the URL of the JSS and it should work.

Hope this helps with the reporting issue!

@mkolb

Where do I put the jss url? Those fields are just descriptions aren't they?

Also do you know what happens with machines where FileVault is already enabled? Can the JSS grab the key or is there a way to pull the info?

You enter the JSS URL in the "Escrow Location Description" field. And yes, it should also work to get the key if FileVault is already enabled.

Actually I see the key stored in the management tab now. That was strange. I guess I did have it setup right, but I still don't see a place to add the JSS URL

@mkolb Thanks! I should be good now.

Okay .. my bad. Should have read the tiny text more carefully :P

OF COURSE it will get stored inside the JSS the configuration profile got pushed from..

What you enter in this field is just the text, that get's shown to the user when FileVault gets enabled. Something like "Your trusty IT Department" and then the user would get a message like "Your FileVault recovery key will be stored at Your trusty IT Department".

So yes.. should work to report no matter what you enter there... sorry for the misunderstanding!

You may need to run a recon to get the keys. I've found that to be the case after the Profile/Policy has been deployed.

you ever create the config profile and test and test and get nowhere, then realize you forgot to add the scope? Asking for a friend.