Enrollment after imaging is not happening

[AVmcclint]

I've noticed a problem with imaging and enrollment but because I image so infrequently I can't pinpoint when it started. When I image a Mac using the same configuration I've always used, the imaging will go fine and the computer will restart. When it restarts and sits at the login screen, it's supposed to start all enrollment tasks within a minute or two. Instead it just sits there and does absolutely nothing. When I monitor it in JSS, nothing happens until 15 minutes after that restart and it does a normal check-in and it will process check-in tasks. The only way I can get it to do any enrollment tasks at all is to manually run jamf policy -event enrollmentComplete
and then it does what it's supposed to do. It is possible that this all started when I upgraded to JSS 9.92, but I couldn't swear to it. Does anyone have any ideas for why post-imaging enrollment isn't happening?

[apizz]

@AVmcclint Do you use Autorun Imaging? For whatever reason if you use Autorun Imaging it does not automatically throw up an enrollmentComplete status to kickoff those post enrollment policies.

[AVmcclint]

Nope. I don't use Autorun at all.

[apizz]

@AVmcclint rats. Do you have any post enrollment items that are copied to the local machine and then installed after rebooting - the black "Casper Imaging is Finishing ..." screen?

I know there's a known bug where, for whatever reason, the jamfHelper is not triggered properly by Casper Imaging after reboot to install these locally copied install items. The workaround has been to configure an empty installer PKG with a postinstall script which simply manually calls the jamfHelper.

[mpermann]

@AVmcclint I was speaking with my TAM the other day about a DEP workflow that relied on the enrollment complete trigger and he indicated the enrollment complete trigger isn't working reliably and that I would be better off not relying on that trigger. He didn't give me a PI number or anything so you might want to reach out to your TAM about the issue. Maybe they can help track down what the issue is for you.

[grecopj]

I've had this happen as well. Very sporadic. If I have a machine that does not enroll, I can image another and it will enroll right away.

Are these machines that were already in the JSS and you are just re-imaging them? I thought that was my issue at first. I would delete them first from the JSS and then image. However I can't say that was the reason they were not enrolling.

[AVmcclint]

@aporlebeke I did at one point have a script set to run post-imaging (Casper Imaging is Finishing...) but I removed that during my troubleshooting so it is no longer part of the process.

@grecopj So far this has happened on every computer I've imaged in the past couple months. Every machine is fresh, out of the box from Apple - NOT DEP - never been setup before.

I did notice one thing a little bit ago, the NetBoot image I'm using to do the imaging from has Casper Imaging 9.81 while the JSS is 9.92. That shouldn't matter, should it? I've had mismatched Imaging app and JSS on several occasions as it takes me a while to get around to making a new NetBoot image after every upgrade and i've never had this problem before. I guess i'll need to bump this up on my To Do list soon to eliminate it as a factor.

[apizz]

@AVmcclint That may be the issue here ... I know I've also been told that it doesn't matter, but of course it doesn't matter until it does ...

I'd make another Netboot set with whatever OS you've been using for Netboot images and the same version of Casper Imaging that your JSS is running. See if that changes anything.

[ToriAnneke]

Hi all,

I posted on another thread because I didn't find this one in the JN search field. Thank you @AVmcclint

To add. I am not imaging, no Autorun, no DEP.
Existing user macs (however: previously enrolled with another JSS) that are being now being enrolled using QuickAdd into our corp jamfcloud.
The .pkg are not ticked to be installed on boot drive.
The script is set to After.