Policies and Scripts Flashcards

Where in Jamf Pro can you view the policy execution logs for a specific computer?

Answer: In the computer's inventory record under the History tab

Policy execution logs for a specific computer are found in that computer's inventory record under the History tab, showing which policies ran and whether they succeeded or failed.

What does 'Flush Policy Logs' accomplish in Jamf Pro?

Answer: Removes execution history records so a policy can run again on devices that already completed it

Flushing policy logs removes the record of a policy having run on a device, allowing policies with restrictive execution frequencies like 'Once per computer' to execute again.

How does Jamf Pro determine whether a script within a policy succeeded or failed?

Answer: A non-zero exit code from the script causes the policy to be marked as failed in the logs

Jamf Pro follows the standard Unix convention: a non-zero exit code from a script marks the policy run as failed in the policy logs, alerting administrators to investigate.

What is Jamf Self Service?

Answer: An app that allows users to install approved software and run policies on demand

Self Service is a Jamf-provided application that presents admin-approved software, configurations, and policies to end users, empowering them to manage their own device within admin-defined boundaries.

In Jamf Pro, how do you make a policy available for users to run on demand through the Self Service app?

Answer: Enable the Self Service payload in the policy and configure it to appear in Self Service

Adding and configuring the Self Service payload within a policy, including a display name and icon, makes the policy visible and runnable by users in the Self Service app.

What does the 'Once per user' execution frequency do in a Jamf Pro policy?

Answer: The policy runs one time for each unique user who logs in, across any managed computer in the fleet

'Once per user' tracks by username across the entire fleet, so the policy runs one time for each unique user regardless of which managed computer they log into.

What is the recommended best practice for testing a new script in Jamf Pro before deploying it broadly?

Answer: Scope the policy to a small test group, verify results in the policy logs, then expand scope gradually

Best practice is to scope the policy to a small test group first, verify execution results in the policy logs, and then gradually broaden the scope to limit risk during deployment.