Log show -info -debug -predicate 'subsystem = "" AND category = "ManagedApps"' -last 1hĪnd just to clarify, there are requirements for this functionality to work for you:
To check for the installation of the QuickAdd locally on a device, you can filter log events like so: If you're not confident you can pass that information securely when running this command, just use the API endpoint outlined in the steps above and avoid running the command locally on a device.
Be careful where and how you invoke commands like the above. Passing tokens or user:password auth in plaintext is dangerous business. It would look something like this (where 3 is the computer ID in this scenario):Ĭurl -X POST "" -H "accept: application/json" -H "Authorization: Bearer bigLOngTOkEnTHiNghEre" ⚠️ You can also use a curl command with POST to redeploy the Jamf management framework. (This will honor re-enrollment settings as defined by the Jamf Pro re-enrollment settings on the server.) You can see it in the URL of the computer record or in the attribute Jamf Pro Computer ID on a computer record in Jamf Pro.Īs long as the computer is online you should see the command run and the computer will go through re-enrollment once the QuickAdd installs.
Reynolds outlines how to create a new patch title, add packages, create patch policies and promote packages. He also shows how these subcommands can be filtered and introduces jumpstarting with jctl packages. James Reynolds discusses, in detail and with examples, subcommands for specific object types. Naduald shows a few examples in detail, including how to: list all computers, list computers with a specific name, handle policies with logout triggers, review all Self Service descriptions and remove computers that haven’t checked in since the previous year. Topher Naduald covers jctl Functions: a simple tool to perform actions that would take many actions to perform such as GUI-based searches modifying policies, scopes, or computer groups and updating patch policies. This easily-adapted tool is available on PyPi. This simple but powerful tool updates Jamf records in less than 15 lines, converts XML to Python (and visa versa) and supports all Legacy API calls.įorster discusses configuration, additional object support for Jamf server objects and ideas for using the tool in a variety of ways. Sam Forster discusses the fundamental structure for handling the API in Python3, which uses: Under the hood: how python-jamf works internally Richard Glaser also discusses the development history of the tool, which originated as a patch management tool.