Post

Replies

Boosts

Views

Activity

Big Sur - FV2 deferred enablement is not working - Beta 1 & 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.
3
0
842
Jul ’20
Big Sur Beta 1 & 2 - AD Mobile Accounts = Network Account + User Account & User Folder not created.
Hello, I tested Active Directory Bind and Mobile Account login on Beta 1 & 2. FB7870925 The settings are Create mobile account at login Force local home directory on startup disk Allow network user to log in at login window Expected on first login Mobile account and user folder is created. Once finished the account is listed as Mobile. What actually happens User logs in, but the account and user folder are not created. The account is listed as "Network"
1
0
967
Jul ’20
Big Sur - FV2 deferred enablement is not working - Beta 1
We have started testing FileVault 2 Enablement workflows. 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.
0
0
820
Jun ’20