Skip to main content
Solved

Forcing checkin

  • August 20, 2015
  • 9 replies
  • 703 views

Forum|alt.badge.img+8

I am doing testing and I don't want to wait for the recurring checkin trigger to time out. Is there a command that forces a checkin right now?

Best answer by kyoung

Good stuff. Thanks loads for the foundational clarification.

9 replies

mm2270
Forum|alt.badge.img+24
  • Legendary Contributor
  • 7886 replies
  • August 20, 2015

Yes.

sudo jamf policy

Edit: You might also want to set up your test policy to use a manual trigger in addition to the check-in trigger. Just click the "Custom" box in the General pane of the policy and add a unique string there. In Terminal, you can run

sudo jamf policy -trigger "somestring"

to call the policy manually.
But either way works.


Forum|alt.badge.img+8
  • Author
  • Contributor
  • 50 replies
  • August 20, 2015

I wondered if that was the one. Thanks much.

OK. If I have a policy set to run weekly at checkin a "sudo jamf policy" will force an immediate run of the policy? If the policy does not run I have another problem. It's not an issue of frequency timing?


acodega
Forum|alt.badge.img+15
  • Valued Contributor
  • 383 replies
  • August 20, 2015

Running jamf policy will make a check in occur immediately instead of at its next scheduled time. However this does not force policies to run. The policies that run will still depend on their schedule. So your weekly policy will only run if it's due to run at that time.

If you want to run policies on demand you should set a manual trigger as well as a regularly scheduled time.


mm2270
Forum|alt.badge.img+24
  • Legendary Contributor
  • 7886 replies
  • August 20, 2015

Like what @adamcodega stated. Scope overalls everything else, so if the Mac is not in scope to run your policy based on the execution frequency (or any other condition), then no, simply running sudo jamf policy won't make it run. Same would be true if the execution frequency is set to Once per computer. Once it runs once, calling sudo jamf policy isn't going to make it run again until you flush the policy log.

I suggest setting up test policies to run with a manual trigger plus Execution Frequency set to Ongoing. That way you can run it as often as you need to manually fro Terminal. Of course, in some cases its not going to make sense to set the frequency to Ongoing. For ex, if its installing an OS update. For that, you would need to revert your test Mac to effectively test it again, or scope several test Macs to the policy.


Forum|alt.badge.img+8
  • Author
  • Contributor
  • 50 replies
  • Answer
  • August 20, 2015

Good stuff. Thanks loads for the foundational clarification.


Forum|alt.badge.img+9
  • Contributor
  • 39 replies
  • August 20, 2015

I will say that I am a big fan of setting up Self Service policies for testing instead of forcing myself to launch an elevate a terminal session.


Forum|alt.badge.img+13
  • Honored Contributor
  • 365 replies
  • August 20, 2015

I agree with @Marker.43. When I'm testing an app I usually just change the frequency to Ongoing and enable it in Self Service until I'm ready to finalize its recurrence schedule.


bentoms
Forum|alt.badge.img+35
  • Hall of Fame
  • 4331 replies
  • August 22, 2015

Just 3rding what @Marker.43 & @andrew.nicholas suggested. :)


walkeri3rd
Forum|alt.badge.img+7
  • Contributor
  • 16 replies
  • January 25, 2023

Does anyone know of a why to make the computer check into Jamf and notify the user that their device has not checkin?