Licensing feature in Jamf used with Office

jhuls
Contributor III

A little late on bringing this up but just curious if anyone even uses the licensing feature in Jamf and if they're using it now during a transition from Office 2011 to 2016.

Our situation is that updates simply don't get done as often as it should. I have a configuration that looks for the Office 2011 applications with a "like" set for "14."

The problem is that recently Office 2016 had a release that was 16.14.xxxxx so our license configuration picked up the Office 2016 versions.

In the end this turned out to be something harmless but it was an eye opener in that it could have kicked off a smart group and policy. This seems like a prime candidate for having a "Beings with" setting.

Does anyone else bother using this feature? If so, how would you or have addressed it? It would seem ridiculous to set it to "is" and then update it each time for a small update.

To be clear the conversation isn't really about Office but whether you feel the license feature is worth using and how you might deal with an issue like this.

1 REPLY 1

talkingmoose
Moderator
Moderator

The last version of Office 2011 for Mac was 14.7.7 released in October 2017.

You no longer need to use "like 14." in your Licensed Software definition if you've made sure your Macs are updated. You can say "is 14.7.7" and that will never change.

However, you have a valid point about the potential of matching something unexpected. Have a look at this feature request and vote it up if you think it matches your need:

https://www.jamf.com/jamf-nation/feature-requests/482/starts-with-criteria-type