If you need to redeploy the Jamf management framework to client computers, the official method is to write or use a script that calls the Jamf API (see Redeploying the Jamf Management Framework Using the Jamf Pro API). There are two downsides to this:
- You have to write, find, or adapt a script to call the Jamf API.
- Redeploying the Jamf management framework like this also re-runs all policies like a new enrollment.
I’ve found that creating a Jamf policy to retrieve the Jamf binary, create a client configuration file, and run the “jamf enroll -prompt” command has several benefits:
- A policy can be scoped and re-scoped easily (instead of using a script to parse API query results).
- Previously executed policies do not re-run.
- Some computers may be too broken to retrieve the pending management command created by the API (the command just sits in the pending queue). This policy will work even on those broken computers (so long as they can still run policies provided by Jamf).
- You can also run this script from the command line (using sudo to execute the script as root).