Patch Management - Installed Microsoft Teams 2.x "Version Unknown"

[JevermannNG]

Hi,

we ran into an issue during the Jamf Pro Patch Management.

I ran a Patch Management Policy for Microsoft Teams 2.x with the Option to patch "Unknown Versions", too.

The issue on some Mac Clients, all an macOS 15.3.2, that they were randomly quitting the Teams App.

It turned out that their Inventory in Jamf Pro did not include the installed Microsoft Teams Version in the Patch Management section. In the Inventory view, the installed Microsoft Teams Version was recorded.

A Jamf Recon didnt fix the issue, no MDM or DDM commands have failed on those Clients ...

Did someone else run into a similar issue?

[mvu]

Do you happen to have MAU Setup in Configuration Profiles?

I saw it where when you set up the com.microsoft.autoupdate Application Domain, if you have the channel to update Beta or Preview, the Patch management might fight with you, especially if you check off patch "Unknown Versions."

I saw this with OneDrive and Defender.

[JevermannNG]

Yes, we use MAU and it is set to "Current Channel".

I know that at least one Mac has a Beta Version of Teams installed (yes they do have local Admin Rights), but there are 20 more Macs who have a similar issue and no Beta or Pre-Released Version of Teams installed ...

It is strange that the Jamf Inventory shows the correct version of the installed Teams App but the Patch Management does not get it ... Bug or Feature?

[mvu]

What if you deleted your Teams Patch Management and recreated it?

[JevermannNG]

Hi @mvu 

I did that yesterday, today only 16 Clients (20 Clients yesterday) show a "Unknown Version" for Teams.

The strange thing is, some of those Clients havent run a Recon for days ... looks like that Jamf uses outdated data in the Patch Management?

[mschlosser]

I’ve found patch management to be notoriously unreliable, with a lot of points of failure, along the way; if the goal with teams and other frequently patched apps like browsers is to just be on the latest version in a timely fashion, i would recommend that your use the Jamf App Catalog or the open source installomator zsh shell script, both achieve this goal for me by patching apps like this with minimal intervention. Way more reliable than patch management. I only use patch management if i must to stay on a certain version and i don’t want the latest until after testing. Just a few alternatives that work better in my opinion

[JevermannNG]

Hi @mschlosser 

thank you for the info, we have a self hosted Jamf Pro Instance, so no App Catalog possible ...

For the Browser Updates I use a "Intune" Script that I found here:

https://github.com/microsoft/shell-intune-samples/tree/master/macOS/Apps

I will take a look at Installomator ... Thanks!

[mschlosser]

sure, glad to help, i'll take a look at the scripts you posted. thanks. Installomator can be found here, I think you will enjoy it, it's very powerful and reliable in my usage. It can be found here: https://github.com/Installomator/Installomator