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.
Daniel Kingdon commented
Please can this be given some thought. We run several computer labs with over 300 students. Even with profile clean up based on 30 days our C:\Users directories are now ballooning to over 100gb in some cases. 100 copies of 700mb of teams application on the same pc cannot be efficient. Just let us install to program files like every other application on the planet. We love teams but this could force us to temporarily disable as we are running out of disk space.
Still no word from MS, other than to add the msi wrapper into the latest office 365 installer.
Also worthy of note is that not only is the executable in appdata, when is should be in program files. The cache IS in appdata when it should be in appdatalocal.
Can we accept that programs should go in programfiles, application data (settings etc) should go in appdata (allowing us to redirect/roam) and cache files should be appdatalocal so they can get destroyed after log off. This not only work in an education settings, but enterprise and VDI.
It is really not that hard a concept. Even Adobe can get this right!
Closing the previous request, and being extremely quiet on this request is exceptionally frustrating when we are the people pushing this product to millions of end users and these limitations are making our job in-necessarily hard.
We don't need 2 weekly updates, as said previously this is production grade software now time to do things properly.
And at least confirm that you have heard this UserVoice and recognize we want something that is not available.
Hi Microsoft Team
I would like you to ask to improve Microsoft Teams app.
Please find a way of installing it per machine rather than per local user profile.
Installing this app per user local profile is not very convenient, as people can move desks or use hotdesks.
It is beyond stupid to not provide this! Allow regular users to install apps in user-writable app-data? Has MS been aware of this new ransomware thing? If they want enterprise adoption, get with it.
Sticking with Slack until Microsoft pull their finger out, will also need to look at alternatives for Skype for Business as it gets phased out. We simply cannot allow this software in our organisation.
Steven M commented
Same here!!!!! I would also like a proper per machine install for the company I work for. Would like to install this in a non persistent Citrix VDI where I don't have to roam the profile location of the Teams user install.
Microsoft pull your finger out and offer an alternative install based on true per machine.
David Kosik commented
Please allow proper per machine installs. You argue that the updates are too frequent for admins to handle. Well I have a solution for this. Do not update that often. Nobody wants updates twice a week. This is no longer beta software.
As already said, users should not be allowed to run programs from areas where they are permitted to write files.
I guess I will switch to Slack if no proper installation process (into ProgramFiles) process can be given by Microsoft for Teams.
Still hoping to hear from you...
Still waiting for a proper installer for my citrix environment! I refuse to have all citrix profiles bloat with several hundred MBs of Teams ****.
Nick J commented
Please sort out your Teams installer or we cannot roll this out to our Citrix/RDS users, until you fix this our users will have to make do with the web version instead.
I found this suggestions for Microsoft to improve install options on teams: https://www.masterpackager.com/blog/how-microsoft-teams-installer-should-have-looked-like-from-the-beginning .
So Please Microsoft, is it available tomorrow?
Please just use the O365 C2R / Standalone Setup set and stop with the open source, security and enterprise nightmare updater. This would put it in C:\Program Files\ where it belongs, not in App Data where everyone should never let executable code run and it also makes it a total nightmare to manage and report on version updates. There is more than one reason for this - we have security policies to follow and validate and verify that software is indeed at the correct version - when its installed per user it could have 30 different versions of the software, and has to install 30 times when each user logs in, and it is not efficient or effective. It also makes troubleshooting and central management nearly impossible.
We would love to use Teams on computers in a training lab, but installing to each user's APPDATA folder is a terrible means to accomplish this. It's not a useful tool if all of my users lose access to it if they need to use a different machine.
Wait they still seriously haven't fixed this yet
Ditto MS, ditto
Eliot Sinclair & Partners commented
Pretty Average effort MS. Didn't you guys come up with the whole Program Files deal?
Asmus Georgi commented
I agree. At least for enterprise/institutional environments, please allow installation of Teams for all users, in Program Files. Use functionality such as is employed by Windows, Office, or Google Chrome and other software, for updates in such a scenario.
You now allow installation for all users in a VDI environment, but provide no update mechanism in that case, and you block the alluser install in non-VDI cases.
This is all very frustrating, and will limit adoption of Teams. We have decided not to deploy it in new university labs and VMs that we are setting up, despite heavily using Teams otherwise and being quite happy.
Please change the install directory to program files instead of dumping it APPDATA.
John Babbitt commented
Microsoft finally made it enterprise-friendly. I have the full Remote Desktop Server package (RDG, RDCB, RDSH), including User Profile Disk (UPD) and Software Restriction Policies (SRP) yet I got this to work today with the enterprise-friendly installation. You can read about it at https://docs.microsoft.com/en-us/microsoftteams/teams-for-vdi. There are a few items to tweak, though:
1. Installation will fail unless you create a registry key, if one doesn't already exists, for either:
a. HKLM\SOFTWARE\VMware, Inc.\VMware VDM\Agent, or
If you do not want to auto-start this for everyone (I had another group that doesn't use it at all and it annoys them every time they log in):
2. After installation, delete the registry value Teams from HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Run. Do not delete the other two TeamsMachineUninstaller* values.
3. If the user wants it to auto-start (unfortunately, Teams didn't have its own auto-start option), do these:
a. Right-click Start Menu (Windows logo key) and select "Run".
b. Enter "shell:startup" and press Enter. This opens up you your Startup folder.
c. Click Start Menu, scroll down to Microsoft Corporation, drag Teams to your Startup folder.