Microsoft Teams version number has decreased, how do I fix this in Munki

[dave.hil...@displaylink.com]

Hi

Microsoft Teams has changed its version number from "1.00.033451" to "1.00.1253" and this has confused Munki because the new version has a lower release number B-(

I could bump the version number to be greater than the old version but then I will have to do that for every new version that comes out.

How do I fix this in Munki such that I don't have to keep changing it for each new release?

I have googled this (tm) several times and not found a solution in Munki (or maybe I missed it)

Currently running munkitools 2 but I can upgrade B-))

Dave

[Gregory Neagle]

Here's what I'd do, assuming CFBundleVersion isn't helpful/useful in the application's Info.plist:

1) Send a nasty-gram to Microsoft, reminding them that versions must always go UP.

2) Remove all older versions of Teams from my Munki repo (or at least from the catalogs my clients are using)

3) Add an installs array to the 1.00.1253 item that will cause Munki to detect it needs to be installed, even if 1.00.033451 is currently installed. There are several possibilities for this; one that is almost certain to work is a file item pointing at the executable (and including the file hash).  But you might find other files or plists or bundles you can check for.

-Greg

--
You received this message because you are subscribed to the Google Groups "munki-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to munki-discus...@googlegroups.com.
To post to this group, send email to munki-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/munki-discuss/3534e873-70c9-4821-a702-cc425664b503%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[dave.hil...@displaylink.com]

Thanks, that sounds like a plan B-))

Dave

[dave.hil...@displaylink.com]

That fixed it, I added an entry pointing to the "MacOS/Teams" executable with the MD5.

Thanks for your help.

Dave

[dave.hil...@displaylink.com]

Guess what - Microsoft have done it again. The CFBundleVersion has changed from 1.00.131953 to 1.00.21761!

I have managed to work out what's happening though: If you ask Teams what its version is, it will tell you 1.2.00.1761, but all the OSX packaging says that it is 1.00.21761.

I am guessing that 1.00.131953 corresponds to Teams version 1.1.00.31953.

They seem to be incapable of actually setting the packaging version numbers correctly B-((

Sigh,

Dave

[Gregory Neagle]

It's actually worse than it appears. CFBundleVersion is supposed to be a monotonically increasing _integer_...

CFBundleShortVersionString can be the "ww.xx.yy.zz" style version "number".

-Greg

To view this discussion on the web visit https://groups.google.com/d/msgid/munki-discuss/d2d4129e-f281-4a9e-b835-7f476f7c4aca%40googlegroups.com.

[Gregory Neagle]

Looks like Apple has changed the definition:

https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html#//apple_ref/doc/uid/TP40009249-102364-TPXREF106

-Greg

To view this discussion on the web visit https://groups.google.com/d/msgid/munki-discuss/4B5EF54E-8A88-4AE7-96C4-5567DFD82FD8%40mac.com.

[David Ross]

I ran into the current O365 Business Pro keeps re-installing into the first office I put it in. But not until they started to use some bit of it. I suspect Teams is the bad guy and it might be doing a behind the back update on it's own as the install loop didn't start for everyone right away. Haven't had time to deal with it so I told people to ignore the update, made sure it was on all the systems, then removed it from the Munki manifests. Office with only about 30 computers so it wasn't insane.

To view this discussion on the web visit https://groups.google.com/d/msgid/munki-discuss/d2d4129e-f281-4a9e-b835-7f476f7c4aca%40googlegroups.com.

[dave.hil...@displaylink.com]

Yes, the new versions of teams seem to have an auto-updater built in. That's what caused the problems for me as version 1.00.131953 "updated" itself to version "1.00.21761" so Munki promptly popped up the "update available" dialogue. When the user chose "update" it reinstalled the original version which then auto-updated to 1.00.21761 which triggered Munki again (and so on in a loop). It's located at: "Microsoft Teams.app/Contents/TeamsUpdaterDaemon.xpc".

Dave