![]() As a workaround, you can set the 'HideAdminUsers' property to (no/false/0) to not hide admin accounts temporarily until this issue is resolved. If you see "HideAdminUsers = 1", then you are seeing the issue I described above. System_profiler -xml SPConfigurationProfileDataType | grep "HideAdminUsers" You can run the following command on an affected Mac to see if this setting is configured: This behavior has been reported to engineering and is currently being investigated. You have to force reboot to login with the new password at the login screen and then the new password will also work to wake/unlock the Mac. One thing I have noticed that is unique on. However, we have a single device that even though it prompts the user for their password to enable FileVault, it never actually enables. I have the process working on several test Catalina devices. We are working on getting FileVault enabled. ![]() If you have a '' payload installed and set the 'HideAdminUsers' property to (yes/true/1) and then the user changes their password and then puts the Mac to sleep or locks the screen (before rebooting the Mac), the new password is not accepted when you try to wake/unlock the Mac. There was a problem enabling FileVault on your computer. This can be caused by having a '' payload installed with the 'HideAdminUsers' property configured to hide the admin accounts ( ). We're running into the same issues, opened an Apple case and they suggested its a profile (payload) issue with our MDM, we use Workspace One. On my intel device that this does happen on, it doesnt show 1st and last name like my Apple Chipset device does on the lock screen. Not 100% about that but my other test device doesnt do this even after i removed the 2nd filevault enabled account. if there is more than one account that pops up on the log in screen, the issue doesnt happen. During DEP enrollment, user needs to auth to Okta then create a local account using setup assistant. Essentially I have an enrollment script that calls on the custom trigger 'FV2' to run, all using jamfhelper. This happens when there is only 1 single filevault enabled user. Filevault 2 enabling hidden management account and not passing secure token to next user. I am seeing this both on Intel and Apple chipset devices. Click Browse, and then click Choose for Not Encrypted. When the criteria is displayed, make sure the operator is set to is. Click Choose for All Criteria, and then click Choose for FileVault 2 Partition Encryption State. Work around is to input Finger print in Touch ID & Password to get back to desktop without having to reboot. Click Browse, and then click Choose for Eligible. New lock screen will not accept correct password to log back in. Whether you click lock screen or it times out and goes to screensaver. Others that use jamf reported this as well. But i dont think our Configuration profiles are the issue. Hey all, dealing with an issue after upgrading to Sonoma.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |