Solved

Cancelling pending commands for multiple computers

Forum|Forum|3 months ago
August 6, 2025
5 replies
107 views

+4

sparrowhawk
Contributor

Hi all,

I’ve been unable to find the answer to this one so I’m hoping the experts here will know the answer.

I accidentally scoped a policy to all computers with the recurring check-in box ticked rather than just the enrollment complete option. I realised my mistake and rectified it, but now there are multiple pending commands in the policy log. How can I cancel these?

Thanks

Best answer by AJPinto

Thanks for your reply @AJPinto . Let me check I’ve understood you.

So even though these devices have already been enrolled, the fact they are in scope will mean the policy is still pending? And there’s no danger my previous choice will mean the command is operated on the devices? It would cause me some pain if that happened, that’s all. Sorry if I’m being a bit thick 😁

Thanks

Correct, they will stay pending until the trigger causes the policy to run on the devices. If the only trigger is enrollment, then the devices should neve have a trigger run the policy. Also keep in mind every policy will always have a CLI trigger (sudo jamf policy -id ###) if you ever wanted to manually run it.

+26

AJPinto
Legendary Contributor
Forum|Forum|3 months ago
August 6, 2025

The pending devices in the policy logs, are devices that are scoped for the policy but have not run it. You have it scoped to all devices, with an enrollment trigger, so its normal to see all your devices in there as pending. If you want to remove them, you will need to narrow the scope.

P

Like

S

+4

sparrowhawk
Author
Contributor
Forum|Forum|3 months ago
August 6, 2025

Thanks for your reply @AJPinto . Let me check I’ve understood you.

So even though these devices have already been enrolled, the fact they are in scope will mean the policy is still pending? And there’s no danger my previous choice will mean the command is operated on the devices? It would cause me some pain if that happened, that’s all. Sorry if I’m being a bit thick 😁

Thanks

Like

+26

AJPinto
Legendary Contributor
Answer
Forum|Forum|3 months ago
August 6, 2025

Thanks for your reply @AJPinto . Let me check I’ve understood you.

So even though these devices have already been enrolled, the fact they are in scope will mean the policy is still pending? And there’s no danger my previous choice will mean the command is operated on the devices? It would cause me some pain if that happened, that’s all. Sorry if I’m being a bit thick 😁

Thanks

Correct, they will stay pending until the trigger causes the policy to run on the devices. If the only trigger is enrollment, then the devices should neve have a trigger run the policy. Also keep in mind every policy will always have a CLI trigger (sudo jamf policy -id ###) if you ever wanted to manually run it.