I discovered this bug a while ago and of course Apple enterprise support was 0 help(what a surprise) but a colleague today didn't heed my warning about not using the GUI to add a user and passwordservice crashed. Afterwards, nobody could log on to any machines besides the server itself and instead of restarting the server, the person in question began resetting passwords.
They were able to log in until we did a reboot. Now it seems that everyone who didn't change their passwords after the crash can log in, but the user who changed his today cannot. On top of it all, I am getting tons of "UNKNOWN_SERVER" messages coming from the clients I had bound to the directory. They started right after the password service crashed.
Is there any way to allow the users who logged in today to continue to use the passwords they set today, or do I have to have them all reset their passwords again? How do I get rid of the "UNKNOWN_SERVER" messages?
They were able to log in until we did a reboot. Now it seems that everyone who didn't change their passwords after the crash can log in, but the user who changed his today cannot. On top of it all, I am getting tons of "UNKNOWN_SERVER" messages coming from the clients I had bound to the directory. They started right after the password service crashed.
Is there any way to allow the users who logged in today to continue to use the passwords they set today, or do I have to have them all reset their passwords again? How do I get rid of the "UNKNOWN_SERVER" messages?