AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
What is jamf self service11/12/2022 WHAT IS JAMF SELF SERVICE HOW TOAutomation with AutoPkg - enter VersionRegexGeneratorĪfter William’s talk I started thinking about how to automate the creation of the regex strings as part of an AutoPkg workflow. WHAT IS JAMF SELF SERVICE UPDATEManually running this script for each application in your Jamf portfolio every time there is an update is not very scalable. Unfortunately, we need to recalculate the regex string each time the version is bumped for an app. This properly mimics Munki’s criteria for installing the Firefox package. This policy is only in scope if Firefox is either not installed, or an older version of Firefox is installed (and if the computer is in the Testing static group). Here is an example for Firefox based on an “update-smart” Smart Groups similar to that used in standard AutoPkg. The outputted version string can be pasted into a Smart Group, so that if installed Application Version does not match the regex string, the policy is in scope. William also gave an excellent video conference talk as part of the 2020 MacAdmins Campfire Sessions about regex which touches on this script at the end: you should watch this now if you haven’t already!.Īs an example, the regex for version 80.0.1 of Firefox is: This complicated and impressive script is available as a gist file: check it out here!. Though not as simple as “greater than” / “less than” options, it does open up the possibility of constructing a regex string which matches the current version plus any feasible higher version.īack in the summer of 2020, William Smith of Jamf Professional Services shared a script which, when provided with a version string from the command line, outputs a regex string which matches the inputted version and anything higher. Recent versions of Jamf Pro have added the ability to do a regex match of Application Version. Jamf Patch was supposed to address this issue, but rather than adding “greater than”/”less than” functionality to regular policies, the Patch project became an over-engineered nightmare, necessitating compiling lists of versions in a separate server not included in Jamf Pro, and creating different Patch Policy objects in Jamf Pro which can only be scoped to computers that already have some version of the app installed, meaning you still have to maintain policies for computers that don’t have the app installed. At next check-in, the policy will try and fail again, and this will repeat over and over… Patch? WHAT IS JAMF SELF SERVICE INSTALLBut what if the user managed to install a newer version of the app than you are currently offering via Jamf? Either the older version will overwrite the newer version or, as often happens, the installation of the older version will fail, since many package installers include checks to prevent downgrading. When you scope an ongoing, recurring check-in Policy based on Smart Group criteria that an Application is installed and the installed Application Version is not equal to a given version, that policy will run so long as the installed version does not match the repo version. Jamf, on the other hand, can only determine whether the strings are equal or not. Munki can determine whether the installed version has a “lower”, “higher” or equal version string than the version in the repo, which means Munki will never try to install an older version of an app than what is currently installed. One of the major limitations of Jamf Pro in comparison to Munki when it comes to software deployment is the lack of ability to compare version strings between what is installed on a Mac client and what is available in the software repository.
0 Comments
Read More
Leave a Reply. |