Dec 12 2018 09:03 AM
Dec 12 2018 09:03 AM
A teams client that installs for the machine instead of the user has been a frequent request since the beginning. I understand that the logic behind a per user install was so that admin privileges are not required to install or update the app, but there are plenty of down sides to this method:
I'm sure you heard the significant backlash when you released the Teams per-machine installer msi package. It met the technical request of an MSI package which could be installed per machine, while completely avoiding the reasons people were asking for it. Once it became clear that this package didn't really meet the needs of IT admins, has there been any consideration to making an actual per-machine install version of the teams client?
Dec 12 2018 09:25 AM
I'm with Steve on this one.
The current MSI installer has gotten better (fixed problems with the -noautostart flag and missing shortcuts) but setting a runonce key to pull down a NuGet package per user is just not a great way to do this.
We really need a true system wide installer in an enterprise environment.
Dec 12 2018 09:35 AM
Thanks for your feedback, Steve! We'll look into this further and post back with updates on a per machine client! Hang tight :)
Dec 12 2018 09:41 AM
Dec 12 2018 09:45 AM - edited Dec 12 2018 09:45 AM
There are plans for Teams to be added to the Office installer so you'd be able to manage Teams the same way you manage your other office apps. This should roll out early next year!
Dec 12 2018 09:47 AM
That sounds promising. Will we have an avenue to clean up existing installs to keep everything aligned?
Dec 12 2018 10:02 AM
That's great news! When this happens, will it be a true 'per machine install' of teams?
Or is the Office installer just going to install the teams installer, which then installs teams for each user who logs in?
Dec 12 2018 01:37 PM
Can you comment on whether Teams inclusion with the office installer will be a true 'per machine' install of teams, or just another per-machine installer which installs a teams instance for every user who logs on?
Dec 12 2018 02:36 PM
Jan 31 2020 09:10 AM
Any update on the possibility of having a single machine install for the Windows 10 Teams client (possibly with config files per user)? The install footprint of Teams on a per user basis imposes a huge overhead for shared (e.g., school lab) machines.