In the midst of testing and we have a Mac at the client site that was not properly assigned to a department when DEP enrollment completed (and the department being blank meant that the computer was out of scope). Since Enrollment is the only trigger, I'm trying to figure out another way to push all of the policies that should have fired under normal circumstances. Due to the lack of mass-editing functionality in Jamf, I'm not really excited about the thought of creating Self-service versions of the same policies or making dupe policies with only that machine in scope. Is there any non-destructive way to make JSS think that the device just completed enrollment so all of these policies will fire?
Solved
Option to manually kick off Enrollment-triggered policies?
+6Best answer by ljcacioppo
You can add a custom trigger for the policies and then call them via terminal
sudo jamf policy -event $customTriggerName
Since the device would be in scope, it gives you the option to run manually but wont have any adverse affects and you don't need to create new policies, you just add that as an additional trigger option alongside enrollment
+17You can add a custom trigger for the policies and then call them via terminal
sudo jamf policy -event $customTriggerName
Since the device would be in scope, it gives you the option to run manually but wont have any adverse affects and you don't need to create new policies, you just add that as an additional trigger option alongside enrollment
+8sudo jamf policy -event enrollmentComplete
sudo jamf policy -event enrollmentComplete
worked for me without having to create custom triggers.
Thank you, Scottlepp
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.