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
The team is looking into this feature and considering solutions. We will update when there is more information to share.
163 comments
-
Michael Tech Support
commented
We just installed Teams for the first time as a few of our users needed it, but when I discovered this issue (it creates over 300MB in each user's personal directory?!?!), this is unacceptable. We have shared AllInOne PCs for our staff to use when they need to speak to a client, and we can't have 50 users using these PCs, that would create close to 30GB just with different copies of Teams in each user directory. On top of this, there would be dozens of different versions of Teams on the one computer, as each user's copy is only updated when they log in.
At this point, I will have to block users from using Teams as this is just totally against corporate policy. There is a reason we use WSUS to control updates (and to limit the bandwidth we have to pay for). -
Anonymous Coward
commented
Are you going to close this one too, saying that it's working perfectly and you've "listened to the community", and changed absolutely nothing?
-
Anonymous
commented
If this application had been designed and created in the Win98 era I could have understood the way it gets installed.
This is 2020. Today users have no administrator privileges for a reason. Application whitelisting is a must, people who do not use it must have lived under a rock for years. And I am sorry to say that but probably the MS-Teams creators did as well, from the way the application works.
Host-firewall rules based on APPDATA paths are ridiculous. And the desease is spreading (Onedrive, Yammer, what-next?)
Sorry for the rant... -
Anonymous
commented
If the the Installation of Teams for All Users happens, please update the Office 365 installer to also install Teams (and OneDrive) for All User - just like Office has been doing for years!!!
-
Jonyder
commented
We are really waiting for this to be fixed! This is holding us back on using Teams in our multi-user RDP environment. We are still using Skype because of this.
-
Paul Shepherd
commented
FE College here, we have tried deploying MS Teams Client to our desktops but because the AppData folder for each user is redirected to and stored in the users HomeFolder on their network file share the AppData folder size just increases continuously.
Users have storage quotas on their home areas which means MS Teams grind's to a stand still when the quota is near it's limit. This in turn means users can't save any of their files, MS Teams exhibits weird behaviour like meeting video slows down then speeds up, chat becomes unresponsive.
As soon as we increase a users storage quota it all starts to work perfectly again, all this could be so easily resolved by not having the MS Teams client using the AppData folder and using C:\Program Files\Microsoft\Teams\current\ instead.
Microsoft Teams programmers, please if your listening/reading our posts surely you can understand why we need this resolved, we have vast numbers of users all of which are going to need significant storage increases when they return in September.
-
mrcoparm
commented
Not just for VDI environment, we need per-machine installer in an Enterprise environment. At university with 1000's of students and shared machines using up 800MB-1GB storage in each user profile in Student Labs and Staff. AppLocker exceptions for %appdata% teams exe, nasty. Security issue. Firewall rules to %appdata% path painful. Default Shortcut upon install on User profile Desktop painful. Launches FullScreen on next login unless customise %appdata% desktop-config.json file with gpo .So much pain :(
-
Terry D
commented
This is ****... does anyone from MS have a clue what it is like in the enterprise world? Maybe hire some folks that have worked there.
-
Anonymous
commented
Hello, With the central installer we can finally fix the defender firewall to work with teams. Having to do a "registry" workaround to make a client think citrix is installed is just that a workaround. The same is true for the firewall startup script. As was mentioned below the onedrive team have realised this so it would be fantastic if you can follow suit.
-
Anonymous
commented
Installing with the MSI with the following string installs it into C:\Program Files\Microsoft\Teams\current\
All users launch the Teams client from that location.
msiexec /i <path_to_msi> /l*v <install_logfile_name> ALLUSER=1 ALLUSERS=1
SRC 1: https://docs.microsoft.com/en-us/MicrosoftTeams/msi-deployment - Updated Apr 2020
SRC 2: https://docs.microsoft.com/en-us/microsoftteams/teams-for-vdi - Update March 2020 -
Anonymous
commented
Correct, as per last comment..
Installing with the MSI with the following string installs it into C:\Program Files\Microsoft\Teams\current\
All users laucnh the Teams client from that location.
msiexec /i <path_to_msi> /l*v <install_logfile_name> ALLUSER=1 ALLUSERS=1
-
Guy Leech
commented
I thought this was resolved with the machine wide installer and its strange ALLUSERS=1 ALLUSER=1 property arguments that runs it out of "C:\Program Files (x86)\Microsoft\Teams\current" for users rather than their profile?
Download from https://docs.microsoft.com/en-us/MicrosoftTeams/msi-deployment
-
Anonymous
commented
🙌🙌🙌🙌🙌🙌
-
Javier Negro Dieste
commented
And please, stop putting your icon in the user desktop., or at least let the it admin control that behavior
-
David
commented
I sure hope the "information to share" isn't going to be: "nope, perfect as it is!" - we'll dump Teams in a hot minute. Trying to roll this out and expand our RDS footprint has been an absolute DUMPSTER FIRE. If Microsoft wants to lose market share, keep "developing" like this.
-
Ruben Castelein
commented
What about this: https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/multimedia/opt-ms-teams.html (using ALLUSER=1 option, not the same as the ALLUSERS=1 option)?
-
Jason Gould
commented
Just got a notice about Alex's comment for this being under review. Thank goodness for that at least. Only been YEARS of me posting about this all across the internet when nobody cared. Did the same with OneDrive and they eventually got it right. Hopefully teams does to so I can stop using regedit hacks designed for Citrix deployments to get it to work. This must be solved to get peopel to use the desktop application in secure Enterprise environments, and it SHOULD have never got to this point in the first place. Security is #1.
-
Daniel Stevens
commented
Up vote on this. we have a quite powerful terminal server that has 80 modern cores, NVMe, etc.
Teams hangs up the whole server with 100% CPU for a looooong time (20+ min) when more than 10 users login at once and there is a teams update.
I removed teams, problem solved. This is readily reproducible.
Please switch to the dropbox model - installs "normally", for all users if installed by admin, but installs to user profile if it can't get admin permissions.
-
Curt Martell
commented
MS Teams programmers. You say "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".
You obviously haven't ready any of the comments in this forum. You are creating a huge headache for IT Admins. Follow your own best practices.
I am trying to get onto O365 and not having to pay for Zoom anymore was one of my selling points. Now that I have learned that we can't use Teams, I've lost that argument.
-
M
commented
The Microsoft Teams (and OneDrive alike) installer is a CLOWN SHOW! Unnecessarily problematic for enterprise deployment management.