@L-plateAdmin Calling the Jamf binary via a LaunchAgent to run a policy isn't going to work because it won't be running as root, but it does from a LaunchDaemon.
On the issue of multiple policies triggered via the same Custom Event, this is working fine for me on Monterey with a Jamf Cloud hosted JSS 10.33 instance. That's both with some production policies, and a quick test with a policy using Custom Event duplicated several time, and doing a `sudo jamf policy -event CustomTrigger` does show all of the policies running in sequence. One thing to note, in my environment "Allow Network State Change Triggers" is disabled. In the past that tended to cause problems with Enrollment Complete triggers so it was common to disable it. I don't know if that's still the case, but I still leave it disabled.
It works in On-Prem Jamf Pro 10.34.1.
sudo jamf policy -event <trigger>
@L-plateAdmin Calling the Jamf binary via a LaunchAgent to run a policy isn't going to work because it won't be running as root, but it does from a LaunchDaemon.
On the issue of multiple policies triggered via the same Custom Event, this is working fine for me on Monterey with a Jamf Cloud hosted JSS 10.33 instance. That's both with some production policies, and a quick test with a policy using Custom Event duplicated several time, and doing a `sudo jamf policy -event CustomTrigger` does show all of the policies running in sequence. One thing to note, in my environment "Allow Network State Change Triggers" is disabled. In the past that tended to cause problems with Enrollment Complete triggers so it was common to disable it. I don't know if that's still the case, but I still leave it disabled.
thanks for checking, yeah i'm using a LaunchAgent to touch in a file that the LaunchDaemon is looking for it via a watchpath to run the script.. think i have that bit sorted now which is nice.
sounds like its an issue with our system then, it only runs the first policy we set with jamf policy -event "ourtrigger" via a root terminal or a script. then when we disable that one to see if it moves on to the second policy we have set with the same trigger it doesn't run anything at all.
we haven't had any problems with the network change trigger with our enrolment complete ones, i guess its pretty random..
