Improve Install options - Install for all users and install location
Raising this again as Microsoft closed the previous request, saying it was complete even though it was not. (link below)
Teams should install to the program files directory, not the users AppData.
And NO, the answer is not to put a copy of the MSI in Pogram Files and deploy to the users AppData when they login.
Anonymous
shared this idea
8 comments
-
Anonymous
commented
Agree, on a Remote desktop server this is not ideal.
-
misterQ
commented
They have marked this as fixed but are not addressing the fact that it has to be installed via appdata for every user. I think this is there way of pushing updates.
-
misterQ
commented
What are other doing in Education. We have to lock down appdata and this a huge problem.
-
Anonymous
commented
https://docs.microsoft.com/en-us/microsoftteams/msi-deployment
".... Teams application will be installed in that user's appdata folder."
"We don't recommended that you change the default install locations, as this could break the update flow. Having too old a version will eventually block users from accessing the service. "
Teams will not replace Skype for Business until this failure is fixed.
-
Brad
commented
Cannot believe this feedback from Warren..... if they're expecting Teams to ultimately replace Skype for Business they're going to have to change their mind on this strategy. Forcing decisions on businesses is not how you win customers.
"Thank you for the feedback and our Microsoft Teams feature team have seen your feedback. Allow me to provide a response from the feature team.
Why Teams App is NOT installed in Program Files (aka per Machine)?
The goal was to ensure we provide our users with newest features and fixes as quickly as possible and ensure all users are getting the best experience possible from Microsoft Teams.
Therefore, we don’t limit the ability to update the software by requiring only IT Admin credentials. Unfortunately, if the product were installed under Program Files, that is exactly what would happen. Software under Program Files requires IT admin credentials and the updates would need to be managed per user which in turn would be a lot of overhead due to the frequency of updates to Microsoft Teams.Why Not follow Office Installation Practice?
All Office apps require admin credentials to install & update. Office products are updated at a much slower rate than Teams. We are actively creating updates and new features as quickly as possible and having an admin prompt pop due to updates either several times a week or sometimes daily when in Teams would be frustrating for users.
Also, most managed deployments of Office happen via SCCM (msi based) which is handled by IT admins. The process is a system service and an install would not prompt the user for admin credentials. Once the installation is complete all future updates are handled by SCCM. If IT admins were required to handle weekly SCCM for various updates, this too would be frustrating/annoying.The overall goal is to try and make the installation as painless as possible while enabling our ability to keep Teams updated in a timely fashion without placing undo burden on IT admins within organizations."
-
Tom S
commented
While its great that they did implement an MSI installer it does not only "install once" its puts the application in Program Files but still creates a ton of per user garbage. Please fix this broken architecture so it truly is only installed once per machine.
-
Anonymous
commented
agree, please reopen and fix the application so it installs for all users on the machine and stores data only (not executables) in the appdata folder
-
Anonymous
commented
Thank you for raising this again. Closing the last issue and ignoring the problem is not a solution!