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.

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.

Thanks ​@AJPinto , that’s super helpful.

​@sparrowhawk I got you on the edits! Have a great day and thank you again ​@AJPinto for the solution here!!