Jamf Policies Stuck in Pending

The erase policy will have to run after the policy that caches the Big Sur installer. You can try running them manually from your test Mac in the correct order and see if something shows the problem.

1. View each policy as you're showing in your screenshots. Then locate the ID in the URL of each policy. It will look something like "id=28".
2. On your test Mac, open the Terminal application and first trying checking for policies. If your Mac is in scope for any policies to run, you'll see each one running. Verify you see both policies running in the correct order.
   
   sudo jamf policy
   
   
3. You can also call each policy by its ID to run it. Be sure to include the correct policy ID in your command. Call the Install macOS Big Sur policy first. Verify you see the installer appear in the Applications folder.
   
   sudo jamf policy -id 28

If Terminal reports no policies are found, then verify the Scopes for each policy. You may need to adjust the criteria of your group if you're scoping to a group.

Well part of it started working. The installer/erase policy failed but makes sense because the download hadn't completed. I'm waiting for this policy to try again. 

Has anyone ever run into these two policies creating three Macintosh HD's? Two show the standard contents and one is blank. This is on the desktop which has "show disk" enabled. 

Hello @MBlank,

I am having the same problem, but not necessarily have access to the user's machine so re-enrolling might not be an option now.
Btw, where can I find a policy's ID so I can run sudo jamf policy -id xxx ?
Cheers

My Balance Now

..

I found the Policy ID in the URL (https://xxxxxx.jamfcloud.com/policies.html?id=7&o=l)

Yeah, this kind of issue pops up now and then. When a policy just sits in "Pending," even after a log purge and check-in, it usually means something’s out of sync. I’d start by forcing a full recon on the machine using sudo jamf recon just to be sure the inventory is fully updated. Also, double-check how the trigger is set—if it’s on "Recurring Check-In" and nothing’s happening, try changing it to something like "Custom" and run it directly with sudo jamf policy -id [policyID] to see if that kicks it off. If it’s scoped to just one test machine, you might want to un-scope and re-scope it to kind of “refresh” the link. I’ve also seen cases where moving the Mac to a new static group helped the policy fire properly again. And if nothing works, removing the Jamf framework (sudo jamf removeFramework) and re-enrolling the Mac tends to fix weird behavior like this. Sometimes the policy database on the client just needs a hard reset.

Yeah, this kind of issue pops up now and then. When a policy just sits in "Pending," even after a log purge and check-in, it usually means something’s out of sync. I’d start by forcing a full recon on the machine using sudo jamf recon just to be sure the inventory is fully updated. Also, double-check how the trigger is set, if it’s on "Recurring Check-In" and nothing’s happening, try changing it to something like "Custom" and run it directly with sudo jamf policy -id [policyID] to see if that kicks it off.

If it’s scoped to just one test machine, you might want to un-scope and re-scope it to kind of “refresh” the link. I’ve also seen cases where moving the Mac to a new static group helped the policy fire properly again. And if nothing works, removing the Jamf framework (sudo jamf removeFramework) and re-enrolling the Mac tends to fix weird behavior like this. Sometimes the policy database on the client just needs a hard reset.

mymilestonecard

mybalancenow