Skip to main content
Solved

Policy not executing with check-in or custom trigger


karthikeyan_mac
Forum|alt.badge.img+17

I have Ongoing policy with Recurring Check-in and Custom Trigger. Frequency is set to "Ongoing". Device is scoped to policy

 

 

 

sudo jamf policy sudo jamf policy -id <xxx> sudo jamf policy -trigger zoom_update sudo jamf policy -event zoom_update

 

 

 

Any of the above commands does not trigger the policy. It shows "No policies were found for the "zoom_update" trigger."  Any suggestions? Thank you

Best answer by karthikeyan_mac

I did not notice the Client-Side Limitations set to Do Not Run Between time range.  Thank you everyone for the input.

View original
Did this topic help you find an answer to your question?

gabe2385
Forum|alt.badge.img+10
  • Valued Contributor
  • January 18, 2022

Hey @karthikeyan_mac 

Im guessing your scopes are scoped to the computer you are running the command. I always forget to scope the policy that causes that issue. 


karthikeyan_mac
Forum|alt.badge.img+17
gabe2385 wrote:

Hey @karthikeyan_mac 

Im guessing your scopes are scoped to the computer you are running the command. I always forget to scope the policy that causes that issue. 


Yes the device is scoped. (Edited the post)


sdagley
Forum|alt.badge.img+25
  • Jamf Heroes
  • January 18, 2022
karthikeyan_mac wrote:

Yes the device is scoped. (Edited the post)


@karthikeyan_mac Your results would indicate something is wrong with your scoping. Try turning off the Recurring Check-in trigger, change the Scope Target to All Computers, and then see if 

sudo jamf policy -event zoom_update

 works


gabe2385
Forum|alt.badge.img+10
  • Valued Contributor
  • January 18, 2022
karthikeyan_mac wrote:

Yes the device is scoped. (Edited the post)


If it's all scope correctly I would check if there are any exclusions that is causing that issue. You can also check in the computer Inventory, and check the computer you are testing has the policy listed in the management section. 


karthikeyan_mac
Forum|alt.badge.img+17

I did not notice the Client-Side Limitations set to Do Not Run Between time range.  Thank you everyone for the input.


Forum|alt.badge.img+1
  • New Contributor
  • December 11, 2023

One specific issue I ran into was an AD Binding policy wasn't running.  The culprit was the client side limitation requiring me to change "Ethernet" to "Any".  We took Ethernet for granted in the past and never thought to check that setting, but as we've deployed new generations of wi-fi reliant macs in an environment where our AD server is accessible for the wi-fi network - I never thought to update that small setting.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings