Active Directory causes crash at reboot

So I've been testing High Sierra here at work and noticed that after imaging a machine, when the machine reboots it hangs on bootup. It shows the task bar inching along and then just hangs about 7/10 of the way in. I then created a VM to test it in and installed each component and rebooted. I foudn that it was the Active Directory binding that caused it lock up on startup. Anyone else having this issue? Anyone have a work around?


The way I've been able to keep testing is not to reboot after the imaging is done. What i've done is log the user out and log myself in. That way I can at least test, but eventually we'll have to reboot.

Try to change the binding from SMB to AFP and have a look whether it works.

I can varify this issue. Functionality of AD plugin is fine, Machine certificates, user login. Just stalls on boot.

The binding it self works fine. If I just log out as opposed to rebooting, I can log in and do my work. It just happens when you reboot.

FWIW I haven't had this issue at all. Bound and boots just fine albeit slowly.

I've found that prebound (before installing High Sierra) machines fail to boot, but I can manually bind and reboots are fine.


If you have a machine that won't boot you can boot into single user and delete the files in the folders of /Library/Preferences/OpenDirectory/...

You should be able to boot up and manually bind successfully. Previously cached AD accounts can still log in even if you don't rebind.

I'll try unbinding and then a scripted bind later. 😝

If I have an unbound machine its fine. When I bind to Active Directory and reboot the issue shows up. I've resorted to just logging out and then logging in with the AD name to do some testing. But eventually our testers forget and end up rebooting the machine. Will try your single user trick...although that might not be easy to do on a virtual machine.

They wrote me back for sysdiagnose and System Profiler files for the bug I filed. The files had been attached initially 😉 Anyway, the point is, at least they are responding to the issue.

This "appears" to be resolved in 17A315i, at least from a scripted bind perspective. I've only performed the one scripted bind in this version, but it went as planned, so...


Any remaining AD issues in 17A315i? Like upgrading a previously bound 10.12.x machine?

Upgrading a previouly bound machine reboots fine now. Thank God.

Active Directory causes crash at reboot
 
 
Q