Just had an upgrade from 9.81 to 9.92, I have now noticed that since the upgrade, policies that run on 'Enrollment' are not running.
looking at the /var/log/jamf.log shows 'checking for policies triggered by "enrollmentComplete" but none of the enrollment policies are listed to of executed.
JSS policy logs for the enrolled computer is blank
Has anybody else encountered this ?
Best answer by millersc
It appears you hit a bug..... D-009861.
I've also added this to the unofficial bug tracker:
https://jamfnation.jamfsoftware.com/featureRequest.html?id=1699#responseChild14176
To view defects peruse through here:
https://goo.gl/zTdvwT
To submit bugs:
http://goo.gl/forms/tEvpXJrZaj
+10It appears you hit a bug..... D-009861.
I've also added this to the unofficial bug tracker:
https://jamfnation.jamfsoftware.com/featureRequest.html?id=1699#responseChild14176
To view defects peruse through here:
https://goo.gl/zTdvwT
To submit bugs:
http://goo.gl/forms/tEvpXJrZaj
via https://goo.gl/zTdvwT it looks like the bug started in 9.82 and in 9.92 it still is not fixed ??
+17Hey @tcandela! You should be able to run a policy with a run command of 'jamf policy -trigger enrollmentComplete' on a different trigger to get around this for now.
@Kelly.Conrad i'll give your suggestion a shot.
Also, looks like the Jamf binary uses -event instead of -trigger
for this mac that i just enrolled i did both of the following commands
sudo jamf policy -id ###
sudo jamf policy
+18I found this to be a problem with having it install packages on reboot checked in its configuration. My giant workaround was to make a new image that auto logged into a user and then turn off the auto login. (I used to do this years ago). Now it seems to be working pretty well with enrollment complete policies.
Gabe Shackney
Princeton Public Schools
+10I am also experiencing this.
I have only one Policy that is triggered by Enrollment, once per computer.
It's payload is two .pkgs and one Script.
She is a JSS 9.93.1469132907.c hosted on JamfCloud and the client is Yosemite 10.10.5
In the Jamf log on the client machine I see:
Fri Oct 14 09:59:53 machine-name jamf[2744]: Checking for policies triggered by "enrollmentComplete" for user "bappity.boopity"...
I thought maybe I was being impatient so I waited it out for 5 hours.
Upon looking at Console, I see other policies triggered on Login, Logout, StartUp, NetworkChange and they have successfully run.
Then a whole bunch of re-occurring check-in since.
Afterwards, I ssh into the client mac and in Terminal jamf policy -trigger enrollmentComplete
Then, the above Policy runs successfully.
Just kicking in my experience.
w/ Luv & Flowers,
-me
+21I don't know why this post didn't turn up in my searches. I think I'm having the same problem.
https://jamfnation.jamfsoftware.com/discussion.html?id=21640
I am on 9.96 now, not sure if the enrollment trigger has been fixed in 9.96, haven't tried yet, does anyone know if 9.96 fixed this issue?
https://goo.gl/zTdvwT Still lists it as an open issue.
+8@tcandela I'm still having issues getting "Enrollment Complete" policies to fire at imaging time. I'll need to follow up with the support team to figure out why, as we'd like to move to reliable thin provisioning with better control over policy triggers. Behavior has been inconsistent - it appears policy history isn't always getting flushed at imaging, and when flushed, enrollment policies don't always execute on trigger.
On the advice of our JAMF buddy, I've moved our "Enrollment Complete" policies to "recurring check-in" to run once per computer, and it's been a decent work-around. Still, if there's a fix, I'd love to resolve this, too..
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.