Casper Suite Administrator's Guide v8.7 - JAMF Software

Policies
Policies allow you to automate remote management tasks on client computers by pre-configuring the
tasks and caching them in the JAMF Software Server (JSS). This reduces the time you spend configuring
individual tasks and pushing them out to computers by allowing clients to initiate the tasks when they
check in with the JSS.
The following tasks are commonly performed with a policy:
Install and uninstall packages.
Run scripts.
Add and remove printers.
Run Software Update.
Add and remove Dock items.
Bind clients to directory services.
Update computer inventory.
• Perform maintenance functions (Self Healing, fix permissions, update computer names, etc.).
Manage account passwords.
•
How Policies Work
Using policies to automate remote management tasks allows you to specify the task(s) you want to
perform, when and how often the task(s) should take place, and the clients that should execute the task(s).
After saving the policy, it is stored in the JSS. Each time clients check in with the JSS, they check to see if
any policies are available.
Clients execute policies based on three main criteria: trigger, scope, and execution frequency.
Trigger
A trigger is the action on a client that executes the policy. Clients can execute policies at the following
triggers:
None (Self Service only)—Users initiate the policy through the Self Service application
Any—The next time the client checks in with the JSS
Startup—When the client starts up
Login—When a user logs in on a client
Logout—When a users logs out on a client
• Check-In Frequency—This is one of the following intervals:
• 5 minutes
• 15 minutes
• 30 minutes
• Hour
169