4/7/2023 0 Comments Jamf pro mac![]() ![]() Read access to Jamf Pro Server Objects > External Patch Sources.The Jamf Pro API user that is configured for AutoPkg will need two additional permissions: I used homebrew to accomplish this with: brew install jq The next prerequisite is to install jq so that we can easily parse JSON data. If that is not true in your environment, you can add something like the following to each recipe override:Īfter adding the processor, running the recipe again should generate the latest_version.json file in your AutoPkg cache. This means that all of our recipes already include the PATCH_SOFTWARE_TITLE_ID key. In our environment we have recipes configured to upload new packages to Jamf Pro, then add those new updates to patch management policies. ![]() ![]() This script assumes that you are using AutoPkg with Graham Pugh’s Jamf Upload processors. To make this work there is bit of setup involved. So I created a workflow to automate updating that smart group. My only issue with implementing Thom’s workflow is that when using AutoPkg (and Jamf Upload), updating the smart group that identities out of date apps can become cumbersome rather quickly. Thom goes into some detail in that post about why this might be needed/preferred vs using the built-in notifications. In it, Thom discusses using a custom alert that directs users to the “Notifications” section of Self Service where they can apply pending updates. I was inspired by the Jamf Tech Thoughts post, “ Custom Self Service Patch Notifications” by ThomM. This post will outline a method to get app versions from AutoPkg and apply those version numbers to a single smart group in Jamf Pro. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |