Install Hangs, Never Reboots 2nd Time

[yellow]

All of a sudden I appear to have issues with the 2nd reboot (post Temporary Adobe Installer (TAI) finishing) not happening. The whole imaging process appears to go normally, but the "please wait whilst I install" splash screen just stays up for far too long, we've waited more than an hour (normally we're done in 20 minutes max end to end).

I quit the splash screen and manually restart the Mac and it boots back into the TAI. But it's already fully enrolled in Casper since I can then logout and log in as our management account. This means the FirstRun stuff is gone, deleted, which also means whatever is supposed to remove the TAI is gone.. but the TAI isn't gone. It's still the default account the Mac is set to log into. Not sure where this suddenly started coming from, but it just happened on a MacBookPro12,1 & MacBookPro11,3.

JSS (et al) 9.65...

EDIT: Info from the /var/log/jamf.log on the failed imaged device:

Tue Apr 14 11:44:15 MQBA385 jamf[3243]: Informing the JSS about login for user adobeinstall
Tue Apr 14 11:44:16 MQBA385 jamf[3257]: Checking for policies triggered by "enrollmentComplete"...
Tue Apr 14 11:44:16 MQBA385 jamf[3243]: Failed to load launchAgent for user adobeinstall
Tue Apr 14 11:44:18 MQBA385 jamf[3257]: Upgrading JAMF notification service...
Tue Apr 14 11:44:18 MQBA385 jamf[3257]: Upgrading Self Service.app...
[snip]
Tue Apr 14 11:51:30 MQBA385 jamf[3257]:     A reboot was required with one or more of the installed updates.
Tue Apr 14 11:52:10 MQBA385 jamf[3257]:     Blessing i386 OS X System on /...
Tue Apr 14 11:52:10 MQBA385 jamf[8056]: Background Restart
Tue Apr 14 11:52:10 MQBA385 jamf[8056]: Possible issue unloading existing reboot daemon.
Tue Apr 14 11:52:11 MQBA385 jamf[8060]: Regular Restart
[snip]
Tue Apr 14 12:15:37 MQBA385 jamf[9203]: Checking for policies triggered by "recurring check-in"...
Tue Apr 14 12:15:41 MQBA385 jamf[9203]: Executing Policy Hide Migration Assistant...
Tue Apr 14 12:15:42 MQBA385 jamf[9203]: Executing Policy Policy - Bypass Managed Prefs Script...
Tue Apr 14 12:15:42 MQBA385 jamf[9203]: Executing Policy Policy - Fill Username in Casper...
Tue Apr 14 12:15:43 MQBA385 jamf[9203]: Executing Policy Policy - Fix Permissions...
Tue Apr 14 12:15:43 MQBA385 jamf[9203]:     Fixing Permissions...
Tue Apr 14 12:16:52 MQBA385 jamf[9203]: Executing Policy Policy - Power Management...
Tue Apr 14 12:16:53 MQBA385 jamf[9203]: Executing Policy Policy - Update Inventory [recon]...
Tue Apr 14 13:15:58 MQBA385 jamf[11863]: Checking for policies triggered by "logout" for user "adobeinstall"...
Tue Apr 14 13:16:00 MQBA385 jamf[8060]: Error Domain=com.jamfsoftware.core.errors Code=15 "The operation couldn’t be completed. (com.jamfsoftware.core.errors error 15.)"
Tue Apr 14 13:16:00 MQBA385 jamf[8060]: An Error Occurred.  Unable to complete reboot command as requested.
Tue Apr 14 13:16:00 MQBA385 jamf[8060]: Exception: Restart Failed.  Unable to notify User

Notice that the latter "An Error Occurred. Unable to complete reboot command as requested." happens a significant amount of time after.

[yellow]

Hmm.. Maybe this is why?

https://jamfnation.jamfsoftware.com/discussion.html?id=14066

I have an enrollment policy that installs outstanding patches from our ASUS. And since the 2 devices I've been having issues with both came with 10.10.2, and now have 10.10.3 on manual reboot, that might explain what I'm seeing.