![]() Note: The methods described below only work with local accounts. For more details, please see below the jump. ![]() ![]() In both cases, a personal recovery key will be needed as the way to authorize the needed changes. However, it looks like there is a workaround for encrypted Macs which fixes the password problem and sorts out Secure Token in these scenarios. ![]() Up until the past few days, the only fix I knew of for that situation was to back up the data and wipe the drive. Usually, this happens because the local account password in question was changed outside of the Users & Groups preference pane in System Preferences and now Secure Token and the account password are out of sync with each other. “We’ve lost the password to the only local user account with a Secure Token, so now we can’t enable any other accounts on this Mac for FileVault.”.“I changed the password for my local account, but only the old password is being taken at the FileVault login screen.”.Among the potential complications are these scenarios: As mentioned in a previous post, Secure Token can present some interesting problems for Mac admins who work with FileVault-encrypted laptops. As part of FileVault on Apple File System, Apple introduced a new account attribute called Secure Token.
0 Comments
Leave a Reply. |