Big Sur - FV2 deferred enablement is not working - Beta 1 & 2

App & System Services Core OS
ClassicII OP
Created Jul ’20
Replies 3
Boosts 0
Views 842
Participants 2
We have started testing FileVault 2 Enablement workflows. 

FB7824477

At least 6 MacAdmins have attempted to test different workflows (Script, MDM Profile & Policy) and we have been unable to get deferred FV2 enablement working.

After installing MDM Client logging I am seeing a few entries of note.

fdesetup: Volume appears to be APFS
Jun 29 16:03:31[5031:0]:::::::::::::::::: fdesetup: no user approved profile was passed
Jun 29 16:03:31[5031:0]: fdesetup: Exit status: 20

fdesetup: defer username was NULL

Setup the FV2 enablement policy
Login
You can never reach the desktop, kicks you back to the login window.
Replies  3
Boosts  0
Views  842
Participants  2
funkjoker OP
Jul ’20
Hey,

we are investigate in the same behavior and will open a Feedback to Apple. We defer the FV2 Policy (Private Key) via a Profile a few Minutes after the initial enrollment.
0
funkjoker OP
Aug ’20
Hey, it is also not working in Beta 4…Hope for Betta 5
0
funkjoker OP
Aug ’20
Hey,

the issue seems to be fixed in Beta 5 :-)

Kind regards,
Uwe
0
Big Sur - FV2 deferred enablement is not working - Beta 1 & 2
First post date Last post date
 
 
Q