Casper has a lot of tricks to help the learning process as well as troubleshoot deployment issues. Some are client side tricks and others are JSS side. You can also read the [Casper Documentation] for general Casper information.
Client Side Tips
- Can't find a machine in your site? Just reinstall your site specific Casper client from Dropbox. This ensures the machine is in the correct site.
- To ensure inventory is up to date in the JSS, run "sudo jamf recon" from terminal. This will do an inventory scan and send it to the JSS immediately. That way you can be sure the machine you are working on has up to date information in the JSS.
- To run policies that are set to "Recurring Check-in" in the JSS, run "sudo jamf policy" from terminal. Those policies will then apply immediately. There is no way to force a policy "push" from the server, so this is your best bet.
- Want to track a policy as it applies? From terminal run "sudo fs_usage | grep JAMF" (this is case sensitive).
- If you want to test software deployments without waiting for policies, do not use a trigger. Instead use Self Service. Self Service applies immediately, you do not even have to log out of Self Service. Just click the "home" icon at the top of Self Service and you will see any new policies.
- Want to change all of your computer names? This can be done directly from Casper without physically visiting machines.
- Click on each individual machine you want to change the name of.
- On the general tab click edit. Change the computer name as desired. Click save. Note that this step only changes the name in Casper, not on the actual machine.
- Go to Policies and then create a new policy. Give it a name, category, trigger, and a scope.
- Select Maintenance, then Configure. Check the box for "Reset Computer Names."
- Click save. The next time the policy applies the computer name will be updated!
- Need to upload a package or script? Ensure you are in the "Full JSS" and not your individual site. Switch back to your site once you are ready to create a deployment.
- You can see what policies are in scope and which policies have ran on an individual machine. First, select the machine in the JSS.
- To see what policies are in scope, click on the Management tab. You should already be in the policies tab on the left. You can see what policies are set to run, as well as what triggers they are set to.
- To see what policies have already applied, click on the History tab, the Policy Logs on the left. You will see what policies have already ran on the machine, and whether they succeeded or failed.
- Also note that on this tab you can "flush" a policy. This is a great way to have a policy run again on the machine that has already been applied.
Questions? Have a tip to add? Contact us at email@example.com.