Jamf Pro Policy Not Running on One Mac? Start With Scope and Trigger

A software task works on most Macs, but one computer appears untouched. Recreating the policy may hide the original cause and affect devices that were already working.

Start by finding out whether the policy did not run, ran and failed, or completed without producing the expected outcome.

Compare the intended settings

Jamf’s policy documentation describes scope, trigger, and execution frequency as separate policy settings. Have an administrator compare each against the affected Mac and the expected workflow.

For example, confirm whether the computer is actually included in the intended audience. Being managed by Jamf does not mean every policy targets it.

Read the history before retrying

Review the policy’s record for the affected computer. Jamf provides policy-log viewing instructions. Capture the relevant outcome before clearing history or changing execution behavior.

Check a working Mac for comparison. Record the difference, including the policy version, timing, and any returned error.

Test one change

Agree on a targeted correction with the deployment owner. Before rerunning a script or installer, confirm what it does if executed again. A repeated action can have consequences beyond making an app appear.

Verify the business outcome after the test, such as the intended software launching successfully. Document any remaining gap instead of marking the issue resolved solely because a policy completed.

Full Metal Architect can help review MDM deployments and repeatable device workflows. Request a project with the task, affected-device count, and observed result.