Recurring Check-In and Enrollment Complete trigger together?

[tcandela]

I had a printer driver install setup in Self-Service it worked as expected.

I then removed it from Self-Service and set the trigger for Recurring Check-In. Looks like recurring-checkin is set at 1 hour by JSS administrator.

to test this policy trigger change
I deleted One test machine (originally installed the driver via self-service) from the JSS and also ran jamf -removeFramework from that machine, and the re-enrolled that same mac using QuickAdd package. Re-curring check-in has past and the driver did not re-install. Should it re-install? The logs for this policy says 'Pending' for this mac. I did a sudo jamf recon command and still nothing.

I have recently also checked the trigger for 'Enrollment Complete' because when macs get enrolled we want them to immediately get these drivers installed.

I have never before setup 2 triggers on the same policy, is this a problem?

even after setting the additional trigger to enrollment complete, it still has not run.

I did a 'flush all' of the policy, so even though the drivers installed on computers already won't it install again on all those computers ?

[brandonusher]

Have you tried running the following

sudo jamf policy

[bentoms · Accepted solution]

@tcandela, 2 triggers on a policy is fine.

As to flushing the ramifications of flushing the policy logs.. It depends on how the policy is setup.

If it's assigned to a a smart group that's membership changes based on the policies success, you should be fine.

Else the JSS may re-run the policy on clients it already had.

[davidacland]

A common issue is the Mac being out of scope (smart group membership as Ben mentioned). As your computer policy log says pending this should mean its in scope.

The other possibility is the triggers not running. I would check the /var/log/jamf.log for any errors or try running ```
sudo jamf policy
``` as @usher.br said. It will give you a bit more feedback.

[tcandela]

That policy was for all computers in my site. It finally ran the policy on the computer.