@perryd84 Instead of a policy triggered via recurring check-in with a once every month frequency you could set it to just a custom trigger and use a LaunchDaemon running on your Macs to trigger that policy once a month by calling
/usr/local/bin/jamf policy -event YOURCUSTOMTRIGGER
@perryd84 Instead of a policy triggered via recurring check-in with a once every month frequency you could set it to just a custom trigger and use a LaunchDaemon running on your Macs to trigger that policy once a month by calling
/usr/local/bin/jamf policy -event YOURCUSTOMTRIGGER
Hmmm thats a pretty good idea actually!! Thanks for this, let me test it out see if the functionality does what I want.
Hmmm thats a pretty good idea actually!! Thanks for this, let me test it out see if the functionality does what I want.
In case you haven't seen it before here's a handy tool for creating the LaunchDaemon: https://launched.zerowidth.com/
You could also create 'nested' policies: the policy that actually Does Stuff, set to Ongoing with a custom event (trigger), then another policy set to once per month at check-in that calls the original's event.
@perryd84 Instead of a policy triggered via recurring check-in with a once every month frequency you could set it to just a custom trigger and use a LaunchDaemon running on your Macs to trigger that policy once a month by calling
/usr/local/bin/jamf policy -event YOURCUSTOMTRIGGER
You don't even need a launch daemon, you could use use two policies:
Policy 1 Does what you wanted to do in the first place, with a Custom event "Policy 1" checked and "Ongoing" and a filled-out Self Service tab.
Policy 0 Runs Files and Processes, Execute command above for custom trigger "Policy 1", and triggers on Recurring checkin with a Execution frequency of Once every month.
Policy 1 can be run at any time, but policy 0 will also trigger Policy 1 once per month, at recurring check-in.
...which is just what pete already said. Sorry! :)