Posted on 09-17-2013 09:38 AM
Hey fellas..
I've setup a custom trigger in JSS 9.01 called "Q3Updates"
I've tried manually triggering it from the terminal using the following commands
jamf policy Q3Updates
jamf policy -trigger Q3Updates
Each time it says there are "no policies triggered by recurring check-in"
problem is...1. recurring checkin is not enabled in the policy, and 2...that's not the policy I typed in.
Any thoughts on what I'm missing?
Posted on 09-17-2013 10:12 AM
I noticed that in the second command you are typing in "poilcy" instead of "policy". Not sure if you made the typo just in this post or if that is your problem, but I thought I'd point it out since that would cause this behavior.
Posted on 09-17-2013 10:18 AM
just a typo in post here. I shall fix. thanks for pointing it out.
Posted on 09-17-2013 10:21 AM
I think the command now is jamf policy -event <customtrigger> but I also notice in the jamf help guide that "-trigger" is still supported as a legacy option, so I'd imagine that should also work.
I'll test it out on my dev 9.01 setup shortly and see if I can figure out the correct syntax.
Edit: Just tested it out and I was able to get one of our policies triggered by custom trigger to run by using the syntax
sudo jamf policy -event <triggername>
So it works for me doing it that way. As a test, I switched that out to
sudo jamf policy -trigger <triggername>
And it also worked. So as I assumed, if you use the legacy option it still works. If that's not what you're seeing, I would go back and double check everything in the policy as a start.