Hey all,
So since the upgrade to 9 I have had nothing but imaging nightmares and wanted to see how others were approaching this issue.
In the past our imaging process looked like this:
Multiple smart configurations based on building and defined by student or teacher use machines.
A base OS of either 10.7.5, 10.8.5 or 10.9.2(rarely).
Many apps and package installs.
Scripts to install at reboot and 2 packages to install at reboot (which creates the temp Adobe User and calls the JAMF helper to lock the screen).
It used to work where after imaging the unit would go to the JAMF helper screen and then reboot after all policies and scripts have finished running. Now it gets hung up at the JAMF helper screen and never recovers.
It all started out with us getting device signature errors which stopped the enrollment process dead during the 1st reboot. We have a ticket with JAMF currently about this issue although 9.3 seems to fix this.
We now are getting past the signature error but have encountered a new error "failed to launch launch agent for user
101" which happens to be the temporary Adobe User that the "install at reboot" creates. I have been working with JAMF on this for weeks now and just wanted to reach out to see if others have had this issue as well.
No matter what I've tried, the enrollment process needs to be jumpstarted with extra commands and anything that adds extra touches to machines is not ideal.
Going to try to add a sudo jamf policy -trigger enrollmentComplete at the end of my scripts to run at reboot and then add a hard reboot at the end of my last policy triggered by enrollmentComplete since this is what I would have to do to fix the hang.
Gabe Shackney
Princeton Public Schools