Posted on 10-17-2017 01:10 PM
Here is what I am experiencing.
I have a machine running macOS 10.13 (17A405)
I go through Setup Assistance and create a local account. Then in that user environment I enroll computer into Casper and run policies that create additional 'local accounts' via Local Account tool.
I verify I can login into all accounts created. Then I performed a reinstall of macOS 10.13 (17A405). All accounts created via Casper reject the password now. Only my original account that a created through the Setup Assistant retained the password.
I am not binding to AD or OD accounts.
Anyone else have this issue?
Posted on 11-29-2017 04:17 PM
We are having the same issue, thus far only experienced with new machines that shipped with High Sierra (so far we haven't had any problems with computers that upgrade to High Sierra). We start the computer and go through configuration, then we have a "thin provisioning" policy deployed through self service that deletes the initial account and adds either teacher or student account as well as a tech account for administration. After the thin provision is completed, the computer reboots and then, since the initial account was deleted, we only have the two accounts and passwords won't take on them. The best we can figure is that APFS doesn't like the dschutil command (High Sierra initially didn't come with many command line tools, though the latest patch puts them back, but that's also another possibility as to why our particular workflow is not working).
We also do not use AD; the JAMF create/delete account policy won't work for us because we need to create more than 1 account at a time prior to deployment. We are interested in hearing somebody's solution, as many create account pkg creators are no longer supported or aren't quite up to date with High Sierra yet.
Posted on 10-17-2018 02:30 PM
We are just experiencing this issue this school year due to using a policy to create a local admin account. Did either of you have a resolution o this?
Posted on 10-17-2018 04:00 PM
I noticed similar problems on machines that were upgraded to high sierra. A handful of them had to be recovered with the recovery key. It's like the account just decided it had a different password now.