Posted on 12-17-2015 02:06 PM
Hi - we generate policies for various software titles predominately aimed at our non-admin users. An example of this is Google Chrome which doesn't self update for these users. While we're pretty good at packaging, testing and making available version updates, sometimes we might be a week or two behind. As a result, some of our admin users are complaining that they see and install an "update" made available through Self Service, which actually rolls them back to a previous version, when they have manually updated these.
Is there a method to use greater than or less than to drive the enrollment of a machine into a smart group? I'd like to only make a Google Chrome policy available if the user has a version below xxx. If not, how are other people handling this use case?
Thanks, JJ
Solved! Go to Solution.
Posted on 12-17-2015 02:18 PM
Nope, although there is a pretty popular feature request alreadyy submitted for it to do so.
Not sure how others are handling it but I did it with an overly complex script that checked the installed version against the version in the JSS and manually called the install policy if it needed to.
Others have developedscripted ways to check the actual vendors site and pull from there.
But yeah any kind of version checking needs to be done with a script basically, the simplest way would probably be with an EA that had a minimum allowed version and returned something like FAILED for machines below it and then scope machines to an install group based on that.
You can generally get a fairly reliable version number from
/Applications/Microsoft Word.app/Contents/Info.plist
But you might have to choose between these values depending on vendor.
CFBundleVersion
CFBundleShortVersionString
Posted on 12-17-2015 02:18 PM
Nope, although there is a pretty popular feature request alreadyy submitted for it to do so.
Not sure how others are handling it but I did it with an overly complex script that checked the installed version against the version in the JSS and manually called the install policy if it needed to.
Others have developedscripted ways to check the actual vendors site and pull from there.
But yeah any kind of version checking needs to be done with a script basically, the simplest way would probably be with an EA that had a minimum allowed version and returned something like FAILED for machines below it and then scope machines to an install group based on that.
You can generally get a fairly reliable version number from
/Applications/Microsoft Word.app/Contents/Info.plist
But you might have to choose between these values depending on vendor.
CFBundleVersion
CFBundleShortVersionString