Apr 01 2021 09:51 AM
Apr 01 2021 09:51 AM
Now that Message Center # MC245996 is going into effect, users with new-to-them PCs with older install dates of Office are starting to see the update screen with the Teams Upgrade button. Since Office updates don't appear to keep the Teams Machine-Wide Installer updated, I'm wondering what solution you've come up with to keep the installer up to date.
The current method of relying on the user to update isn't very enterprise friendly for an organization that typically prohibits software downloads. Is anyone aware of anything on the roadmap for the Office updater to keep the Teams Machine-Wide Installer updated with a more recent version of Teams?
Apr 13 2021 10:03 AM
Apr 13 2021 10:13 AM
Apr 15 2021 12:21 PM
@David Phillips Any word on this?
I'm getting mixed results when running the latest Teams MSI to update it. Sometimes it's the x86 installer, other times it's the x64. Both of them live under the "C:\Program Files (x86)\Teams Installer" directory.
Apr 22 2021 08:38 AM
@David Phillips Also getting this issue. Any updates from Microsoft? Highly frustrating.
Currently looks as though we'll have to uninstall the machine wide installer and then re-install, as well as deleting user profiles. Really don't want to do this for several users as it's very counter-productive.
Apr 26 2021 07:12 AM
Apr 28 2021 05:58 AM
Jul 07 2021 08:52 AM
Jul 07 2021 08:59 AM
Jul 13 2021 11:24 PM
Oddly enough, at work we have been dealing with this very problem. we recently switched away from Chromebooks and Chromeboxes to full windows 10 endpoints. We are building MDT/WDS to maintain tight control over the OS/software stack on the endpoints. in working on deploying Teams we have been dealing with trying to create a start up script that automatically creates firewall rules for a couple of exes that need to run. Some of them run from appdata which is challenging to create a dynamic rule to account for the user appdata locations. This is part of the reason we are looking at the machine wide installer for teams.
We are a Citrix house so we end up on their support sites doing research. we already use the machine wide msi installer with the switches for: ALLUSER=1 and ALLUSERS=1 embedded in non-persistent VDAs. patching this way is pretty easy for us in this scenario. In prep for the further deployment of our windows endpoints we found this snippet over on the Citrix docs site:
"If You have Windows 10 dedicated persistent VDI environments. You want the Teams application to auto-update and would prefer Teams to install per-user under Appdata/Local, use the .exe installer or the MSI without ALLUSER=1 (I found the Citrix Doc under the title: Optimization for Microsoft Teams).
We built out our MDT application package with the command:
"msiexec /i Teams_windows_x64.msi OPTIONS="noAutoStart=true" ALLUSERS=1"
My hope is that all goes well and the UX would be:
1. Best case: automatic patching just happens user doesn't do anything.
2. The end user selects the 3 dots and then select "check for updates" from teams and the application updates on its own.
Jul 21 2021 02:24 AM
Has there been any update from MS on what the hell we are supposed to do here?
It's bonkers that they are now including the machine wide installer with Office, but then not keeping it up to date.
Almost all of our users are now being prompted to update Teams as soon as they log in for the first time, and there is no advice on MS's documentation page on how to keep the Office bundled machine wide installer up to date.
Why can't they do an ACTUAL machine wide install, and bundle it into C2R, so it can keep itself up to date in the same way Office does?