2 weeks ago
In our Mac fleet are Clients who have Microsft Teams 1.x and 2.x installed.
It turned out that "Microsoft Teams (work or school)" in Version 24231.x changed its Name back to "Microsott Teams".
Does this mean that it will remove a installed "Microsoft Teams" in Version 1.x ?
How does this effect Jamfs Patch Management for Microsoft Teams?
Solved! Go to Solution.
2 weeks ago
The installer for new Teams was meant to remove Teams Classic in the update process, but it looks like they have stopped this process as I just noticed this warning message the below Microsoft page, which explains why we it still see it remaining install on 25% of our devices that are already running the latest version
Important
A rare issue with the uninstall of classic Teams has been detected and to be cautious Microsoft has paused the automatic uninstallation of classic Teams for customers who haven't already completed this step. This issue could result in the Teams Meeting Addin in Outlook failing to schedule or join Teams meetings. We are actively investigating this issue and will update once it's resolved. If your users are experiencing this issue, a workaround is to use Teams to schedule or join meetings.
https://learn.microsoft.com/en-gb/microsoftteams/teams-classic-client-end-of-availability#what-happe...
2 weeks ago
Once your Mac is updated to the "new" Microsoft Teams, the classic version (1.x) is automatically removed. But in my experience, the classic version gets removed randomly and sparse.
You'll have two patch management policies: One for Microsoft Teams (24231.x) and one for Microsoft Classic (1.x). You can update accordingly and/or add a script to remove the Classic version.
https://learn.microsoft.com/en-us/microsoftteams/teams-classic-client-end-of-availability
2 weeks ago - last edited 2 weeks ago
But do you have any experience how Jamfs Patch Management does handle this? Can I stop the Patch Management for MS Teams 1.x ?
Thanks in advance!
2 weeks ago
If your Macs still have the older classic versions, and you're not removing it yourself, then I would continue patching it to the latest (1.7.00.15956).
2 weeks ago
The installer for new Teams was meant to remove Teams Classic in the update process, but it looks like they have stopped this process as I just noticed this warning message the below Microsoft page, which explains why we it still see it remaining install on 25% of our devices that are already running the latest version
Important
A rare issue with the uninstall of classic Teams has been detected and to be cautious Microsoft has paused the automatic uninstallation of classic Teams for customers who haven't already completed this step. This issue could result in the Teams Meeting Addin in Outlook failing to schedule or join Teams meetings. We are actively investigating this issue and will update once it's resolved. If your users are experiencing this issue, a workaround is to use Teams to schedule or join meetings.
https://learn.microsoft.com/en-gb/microsoftteams/teams-classic-client-end-of-availability#what-happe...
2 weeks ago
Thank you for the important info, I have forwarded it to our help desk ...
Friday
Unfortunately, this has been like this since June. We created a script that uses checks to determine things like if Teams is open, If they are on a call, if they are in a meeting, etc. You can pull those status codes and then use them to notify users of a required upgrade without interupting calls and meetings. Then we uninstall Teams Classic so we can give them Teams Pro Max (Really Teams (work or school))
2 weeks ago
Thanks @garybidwell