@corpffhelpdesk2l You may be experiencing the following Product Issue:
PI-004775 Policies with an Enrollment Complete trigger do not run upon completion of enrollment under certain circumstances.
Have you tried disabling Settings > Computer Management > Check-In > Allow Network State Change Triggers ?
We have a Self Service policy scoped to TSRs which executes the following command:
/usr/local/bin/jamf policy -event enrollmentComplete -verbose
@dan-snelson
Have you tried disabling Settings > Computer Management > Check-In > Allow Network State Change Triggers ?
Do you feel the network state change might be what interrupts the beginning of "Enrollment Complete" policies..?
/usr/local/bin/jamf policy -event enrollmentComplete -verbose
What does it do exactly? I guess it calls the policy @enrollmentComplete to start..but I may be wrong
And..does it start the @enrollmentComplete flow only if it was not flown, or also if the policy @enrollmentComplete were already deployed..?
Till now, thank you for your support in any case..!
Really appreciated
@dan-snelson That Self Service policy is a good idea. I'm gonna steal it ;)
@corpffhelpdesk2l The network state change trigger doesn't work reliably to begin with, and it has been known to cause problems with the Enrollment Complete trigger. Disabling it increased the success rate of my Enrollment Complete policies, but didn't completely resolve the issue.
The /usr/local/bin/jamf policy -event enrollmentComplete -verbose command will trigger the Enrollment Complete policies as if the enrollment did just complete, regardless of whether or not it has already flown. Of course, execution frequency still applies, so if you have an Enrollment Complete policy set to execute once per computer or anything other than ongoing, that policy will not run again if it has already run on that computer.
...Does that all make sense and answer your questions?
Jamf specifically added the ability to disable network state change because of what it does to EnrollmentComplete. Disabling that helped quite a bit for us.
honestly that sucks and explains why trigger we had to ensure user signs into Enterprise Connect isnt working well. Is there a workaround you know of to still use network state change triggers?
Does the Enrollment Complete trigger actually work? All I am getting on policies with them is Pending
Barring the problems described above with network state changes the Enrollment Complete trigger does work. Try describing your environment and how you're enrolling and it might provide a clue as to what's going wrong for you.
