Microsoft Teams

We still have Teams available as a ConfigMgr or Intune App, we have not changed this product recently.

Hi Adam,

I cannot find Teams under Microsoft anymore. Could you please put it back? Thanks.

Hi Adam,

this doesn't work the detection method says it is conform, when i change this method from script to "check teams.exe fileversion" i got the error, that there is "teams machine wide installer" already installed.

Best Regards

strauch

You can update the machine-wide installer by deploying the Application as required. Note that this will only update the machine-wide installer, and not Teams itself already in each user's profile.

Hi Adam,

is it possible to get updates for the mashine wide installer. i have computers with version 1.3.0 and 1.4.0 and 1.50 and some installer has problems with the user installation. So i would prever to get the newest teams installer on alle mashines. So i can manual uninstall the old version and install the new version, but it would be nice to get updates for the mashine wide installer (and not the user isntallation).

And maybe the mashine wide installer will get too old, so that it doesnt work anymore. We had this with another application, were the certificate was expired and the installer didnt work anymore.

thank you

strauch

This product exists in our catalogue today as an application, however not as an update. The reason for not supplying it as an update today is detailed below.

The process of updating Teams for all users on a system would involve a scripted action to recursively remove it from all user profiles on the system before running the MSI, as detailed here. Once all copies are deleted in all user profiles, then we need to run the new MSI to update the system-wide component in Program Files.

This is because when a user first launches Teams, it copies the binaries from Program Files into the user's AppData. The user's copy in AppData is automatically updated by itself, independently of the copy in Program Files. This is detailed herein the first paragraph.

Microsoft's recommendation is clear on this,detail here in the second paragraph and pasted below:

Do not use the MSI to deploy updates, because the client will auto update when it detects a new version is available from the service. To re-deploy the latest installer use the process of redeploying MSI described below. If you deploy an older version of the MSI package, the client will auto-update (except in VDI environments) when possible for the user. If a very old version gets deployed, the MSI will trigger an app update before the user is able to use Teams.

If we ignored all of this and added Teams as an update anyway, you will more than likely see patch compliance reports telling you there's a mismatch for the version of Teams users' are running versus the one stored in Program Files. In my view, this provides little value and adds more confusion.

However, there is value in wanting to make sure the copy in Program Files is up-to-date in the scenario of shared computers. We have seen reports from customers where Teams is blocked from launching by Microsoft if the copy in Program Files has not been patched in ~1 year. This causes problems for users logging on to a device for the first time where the copy in Program Files is old. In that scenario it doesn't matter whether you deploy the update or application for Teams, so we may as well recommend deploying Teams as a required application.

@Casey do you have a document you can link to about the stand-alone installer being deprecated? The MSI is needed still for machine-wide Installing, for use within VDI environments, where the Teams will not update automatically.

https://docs.microsoft.com/en-us/microsoftteams/teams-for-vdi#install-or-update-the-teams-desktop-app-on-vdi

Microsoft Teams is going to be built into the Office 365 Click-to-Run installer packages and the standalone installer will eventually be deprecated. You will be able to manage updates for Teams directly in SCCM Current Branch via Office Updates without needing PatchMyPC.