Closed charlespineda closed 1 year ago
According to this page, that's a pretty generic "internal error."
What happens if you manually run sudo fdesetup changerecovery -personal
on an affected Mac?
fdesetup: do not return recovery key
fdesetup: use personal recovery key
fdesetup: device path = /
Enter the user name: `user`
Enter the password for user 'user':
Error: Unable to change key.
Error: User could not be authenticated.
Error: Unable to unlock or authenticate to FileVault.
Do the user trying to run the command have a secure token?
Yes all of them do but I am noticing underlying issues here since these machines use MOBILE profiles a lot of them and I would say majority of them have sync issues and are using two separate passwords to login to their machines.
I have no experience with bound machines using mobile profiles. Apple recommends against those anymore. If people have to enter two passwords to get into their computers then you defined have password sync issues which could explain why the FileVault re-keying is failing. You need to get the passwords back in sync.
Correct, I am working through some to confirm that is the case.
Confirmed that after syncing the MOBILE profile passwords and pushing out the Script again it worked fine.
Glad to hear it!
Summary
@homebysix I mass deployed the script to a large group of employees who are coming from a previous MDM after testing with a group of 40 users most of them completed successfully. Deploying to the rest of the required computers many of them exited with exit code 99 and I am unable to understand what this means at this time. Any assistance would be appreciated.
Steps to Reproduce
Steps to reproduce the behavior.
Expected/Desired Behavior
to escrow and complete successfully A clear and concise description of what you expected to happen.
Screenshots
Versions
Additional Information
Any other context you'd like to share.