Lets remember that Apple took THREE dot versions of Sierra to eliminate the hideous badpasswordattempt bug which saw many MANY AD users locked out of their accounts. They don't seem to be QA'ing AD much if at all, and have tried to outsource their enterprise QA to their customers. Sorry Apple, but you don't pay me (or seemingly anyone) to QA the enterprise features of your product.
Historically, the OS updates come out about every 6 weeks (+/- 1 or 2)
I wouldn't expect 10.13.1 until end of October-ish
And, it wasn't until 10.12.3 in late January that we got the crippling iCloud AD account lockout bug fixed.
Just discovered another potential issue...
While it is just my first test case, upgrading from 10.12.6 to 10.13.0 broke the administrative privileges set in our Directory Bindings via JAMF.
We have groups in AD setup to "Allow administration by" and after updating to 10.13 those accounts would not work to elevate. If I unbound and rebound with our Binding policy the group regained admin privileges.
anyone else seeing an issue with AD bound computers having issues with users not being able to log back in if they do the upgrade off site? i have 6 users who have upgraded while traveling and now they are unable to login to their computer.
I have run across this behavior. If I take a 10.12 machine which is bound to our AD and upgrade it to 10.13, everything works just fine, the user can log in.
However, if I try a clean install of 10.13 and bind it to AD with mobile accounts turned on, it will not login, just gives a generic error message saying something went wrong.
If I setup a new machine with local accounts on, everything works fine, can login to the same AD account that would not work using mobile accounts.
Go figure. Anyone have any ideas, or do I skip building new 10.13 loads for now?
we had an Apple System Engineer came on campus yesterday, and he did confirmed late bug issue with High Sierra and AD/Mobile accounts/changing passwords etc..
His advise was to hold off upgrades...
Apple Professional Services emailed this morning:
Hello, Just a quick update regarding the issue with password changes while bound to Active Directory and logged into your Mac with an Active Directory account in macOS High Sierra. If your organization is impacted by this issue and you have a paid Apple Developer Program account or Apple Developer Enterprise Program account, please test macOS High Sierra 10.13.1 beta seed 17B25 or later, which includes a fix for this issue.
In my limited testing, this issue is NOT resolved in macOS 10.13.1 (17B25c).
We have found that logging in with a local admin account and re-binding the machine does allow AD accounts to log in, then we have to re-sync the login/FV password in System Preferences > Security & Privacy > FileVault - Enable Users. Oddly, it still shows that the user who just clearly unlocked the drive cannot unlock this.
@dhorsfall We've noticed in our environment (AD Mobile accounts) that you don't have to re-bind, just authenticate the user in System Preferences from a local admin account (i.e. click on the Unlock icon and have the user login with their credentials). They have to be either on the network or VPN'd in, and have to be admins on the computer. Saves the effort of having to unbind and rebind. (we also had to have remote employees create a tempadmin account with the fancy Single User Mode trick of removing /var/db/.applesetupdone).
We've also experienced this issue. Somewhat related, using an AD account, I am not able to turn on FileVault at all with a brand new fresh install of High Sierra. I get the following error: "Authentication server refused operation because the current credentials are not authorized for the requested operation." but I am able to continue setting it up with a local account. The problem with enabling it on the local account is that it's our IT account and so my worry is that every time the machine reboots, I need to enter the IT account password to decrypt the drive instead of the AD user account. Then of course if this is true, then password changes required on the AD account side won't be cascaded to FileVault.
i have now had users unable to login after the upgrade onsite but some of the users who have upgraded at home were fine. The user who was onsite, we just had to unbind the computer from AD and bind it back and she was able to login again. Apple still has not told me if they have came up with a fix yet or not. the only thing i have gotten out of them is that there might be a resolution to this issue in the next patch.
Once I found some clients could not log in using their ID and password that were using AD it wasn't necessary to unbind and re-bind. Have them use their regular ID and password but have them use an ethernet cable that is connected to the domain to log in. Disconnect the ethernet cable after and they're good to go. I understand that this is an okay work around if you have clients that are onsite and your team can run around with cables and adapters to resolve.
I did try making the user an admin in sys pref but that did not work. Maybe something to do with how the profile was originally set up as a mobile/managed account?
Unfortunately in two instances so far I have found the computer name to be changed so that will need to be edited and re-binded but I will need to test this more. I hope not otherwise EPO will be a nightmare.
I have installed the 10.13.1 Beta on a test machine. I can confirm that it did fix the issue with not changing the password in AD, but that is the only thing that it changed apparently. FileVault password and Keychain password did not change. I tried on multiple occasions changing the password on a test AD account and saw the same results each time. I have to turn off FileVault and turn back on in order for the new password to be set. I also have to create a new KeyChain in order to prevent annoying pop-ups asking for old password.
AD bound computers having issues with users not being able to log back in if they do the upgrade off site?
We've had one so far. User returned to campus with laptop, plugged in, and within 30 seconds, account authenticated.
Not everyone will be this close....
Odd, when running the High Sierra Beta versions, no issues whatsoever. Just upgraded off-site and could not log into AD account. But logged into local admin account, connected to VPN, fast user switched and all was fine. Really odd. but its seemingly clear Apple really has no interest in AD (not that I ever cared), but it will definitely trip up a lot of unsuspecting users.
On 10.13.1 GM we are still seeing issues with FV passwords for mobile AD accounts not getting updated.
Users changes their password, on next reboot the FV password is the old password but the user account is the new password.
Is this still a known issue with 10.13.1?
Found on Slack:
We were see more issue in 10.13.1 with AD accounts and FV password sync issues. Apple have informed me: “it appears there is an issue in 10.13.0 and10.13.1 where as long as the password is only updated from the Users & Groups pane, the FileVault password will get updated after rebooting and unlocking the volume with the old FileVault password ... but if the AD password is ever changed away from the client from the AD server, from a website, etc), the passwords do not get synced again, even after changing it again from the Users & Groups pane. This behavior has been reported to Apple and is being targeted for a future update."
I'm running 10.3.2. I cannot enable fileVault as a domain account. I receive an error. Account "username" cannot be used to manage encryption on this Mac. Click lock to prevent further changes, then select another administrator account, and try again.
I have a test Mac here that I was running 10.13.1 on and I experienced the problem of the FileVault Password not syncing up with Active Directory after a password change no matter how long I let it sit. I just updated it to 10.13.2. After the update, I let it sit for a few minutes at the desktop then I restarted it. It now takes the password I changed it to a couple weeks ago.
It sucks that these really stoopid bugs are surfacing in High Sierra, but I am glad Apple is making progress on fixing them.