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.
180 comments
-
Anonymous
commented
teams is the biggest pile of installer **** in a really long time. Your ******* the people that can force a change to think of changing. Make MS Teams follow the rules - have a fix for all of the older versions.
Microsoft - fix this pile of **** installer for Teams. Have it follow YOUR rules.
for now, **** this, over to Zoom for my office.
-
Michael
commented
And you do realise that, increasingly, software restrictions policies are a thing, right? A really important corporate security thing...
Executing programs out of Appdata is a REALLY big no no in any corporation with any sort of security policy. -
Jim Dunn
commented
And this is ESPECIALLY important for those using a Citrix-based system... Teams is ALL OVER THE PLACE.
And yes, PLEASE... give us more Group Policy control.
-
Cosmo Kramer
commented
I'm probably not adding anything that hasn't already been said, but the amount of storage that gets taken up on local SSD's and on the file server (where we redirect %appdata%) is problematic. It's going to be a major issue when we migrate from Skype to Teams for voice calling. On top of that, installing .exe's and .dll's in %appdata% goes against everything Microsoft preaches with AppLocker. We really need to be able to install this in Program Files and let us manage updates using WSUS, SCCM, or any other enterprise patch management tool.
-
MakeTeamsLikeSkype_ASAP
commented
to add to this, if you're even at all aiming at enterprise customers of Teams, a must have is the ability to control the app using group policy, please create and add ADMX templates for this.
similar to one drive.
otherwise this app is useless in replacing skypefb. -
Nick Jones
commented
Microsoft please release a branch of Teams that is usable in enterprise with a local install.
If this design choice is due to allowing continual updating I'd much rather PDQ/SCCM out Teams updates frequently then continually struggle with 100s of desktops with full local storage due to bloated local user profiles and a file server brimming due to huge roaming profiles. 2-3GB consumed just by Teams cache alone, per user? Come on, storage isn't free.
-
Anonymous
commented
Come on MS think of our security, .exe's running in APPDATA? Really who's good idea was that!!
-
Katy
commented
With shared devices and relatively small (120GB) SSD drives you soon find the disk full of Teams installs at one per user AppData. Would love it to just run from Program Files, if it wants to cache user-specific stuff in AppData fine but we really need to cut down the disk space it is eating on devices that could potentially see 100 different users log on each week.
-
Jason Gould
commented
Those that say this was resolved with the "ALLUSER" options don't know what they are talking about. All that will do is place the MSI in the program files folder and then when a user logs in install the application in APPDATA. Again, the issue is that the software installs to the users APPDATA folder. That doesn't fix the problem.
They then released a "VDI" deployment solution. In this deployment you actually CAN get what we want. The software is installed once to the Program Files folder and that's it. Every user launches and RUNS the software from Program Files. Nothing gets installed to the users APPDATA folder.
There are 2 problems with this though.
First is that the MSI for the VDI deployment won't install PER MACHINE by default on a NON-VDI environment. You can try to run it on a regular Windows 10 desktop and it will fail. This can be solved by inserting some keys into your registry to "trick" the installer to thinking it's actually VDI. Not ideal, but does work and isn't that difficult through a GPO.Second minor issue is updates.They aren't and don't seem to have any plans to push updates through WSUS (windows update) or some other means like they do for THE REST OF OFFICE. So to update you have to keep up downloading and deploying the new MSI. It's not horrible, but it's unnecessary. It should be handled just like the rest of Office updates
-
g
commented
is really a bad bad idea to install team in the user profile, please provide a way to install to install it as a normal program
-
Dan Smith
commented
We need to have this as a per-computer install just like all other MS Office applications. Applications which are based on a "per-user" installation are not easily administered in an enterprise environment. We are having a great deal of trouble getting this consistently deployed for our users. Please, something needs to be done as soon as possible!
-
Anonymous
commented
total nightmare to administer and deploy to existing users, not VDI friendly
-
Mitchell Sergent
commented
This is incredibly bad in an enterprise environment, for many of the reasons others have already pointed out. Please resolve asap!
-
Chris Hill
commented
You did it for OneDrive - do it for Teams!
https://docs.microsoft.com/en-us/onedrive/per-machine-installation
-
Paul Shepherd
commented
Hi All,
Does anyone know if we are likely to get any response from Microsoft or from Alex who states UNDER REVIEW any time soon, only it does feel like we all have the same issues but no-one is listening or providing any updates on progress ?
Thanks
Paul
-
T
commented
It feels like Teams is just not Enterprise ready despite what Microsoft says.
There is almost no group policy support for it, the installer is terrible, it's not designed for virtualization, it uses a ton of desktop resources (CPU/Memory) for even basic usage, and the Outlook plugin out of the box after install works maybe 1 out 3 times at best.
-
LY
commented
Agree, as an IT pro I have a patching schedule for a reason. There's no need to bloat all my user profiles, mess up RDS/VDI setups and complicate mass uninstallation (if needed). Besides for running as a non standard context. All to make sure I do updates (which are already scheduled).
At least create an enterprise ver (not just for VDI). -
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...