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
69 comments
-
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
b. HKLM\Software\Citrix\PortICAIf 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.Enjoy!
-
CP
commented
BUMP!
-
Charity North
commented
Please Microsoft! Give users options not just what YOU think is best!
-
Anonymous
commented
Hi Microsoft, let some of YOUR Admins see before you publish your Software :-)
-
Anonymous
commented
So poo!
-
Rich Mawdsley
commented
Utterly ridiculous that this still hasnt been sorted. As per other comments, this has now been done with Onedrive, that team has seen the light and made a PROPER machine install which before you say it Mr Teams admin, SELF UPDATES. So you no longer have that excuse.
Just make it properly and you'd get such a HUGE uptick in users by enterprises across the world who hate this current method.
-
Rick Cobb
commented
Microsoft... please stop this insanity! Install your applications in "Program Files" and give us control of global settings in the registry! You (MS) are the one who created these protocols. Enterprise admins have lived by these protocols for years very successfully. Get control over your application developers and stop breaking your own rules!
-
Anonymous
commented
Hate to deal with Software Restriction Policy and Teams. Microsoft messed up!
-
CP
commented
How is this still only getting 400 votes?
Is there not a lot of VMware Horizon View + UEM admin that uses Teams in their environment?
@Microsoft,
I guess as a workaround we just need to tell our people to use Teams only on either web or mobile app, huh? -
Cam
commented
@James, the Office 365 ProPlus installs it in the exact same manner as the MSI (again, useless)
Found under "Additional Info":
"Teams is installed with Office 365 ProPlus in the same way that Teams is installed if you use the MSI-based installer for Teams. For each new user that signs into the device, the Teams installer runs and the Teams application is installed in the user's AppData folder." -
Cam
commented
We've been trying to roll out Teams for months, but with Teams needing admin rights to create a firewall rule to the AppData folder, it's impossible.
I've tried numerous scripts myself and others online have made, but this AppData location jams up everything. -
James Emanuelli
commented
Theyve done this with onedrive! Why not teams??
https://docs.microsoft.com/en-us/onedrive/per-machine-installation -
Anthony Harris
commented
What the heck, Microsoft. You make Enterprise software. How are we supposed to run this in a citrix environment that thousands of students access if they all have to install their own copy of teams?
-
Andy Owen
commented
I concur completely with Josh G's comment. Cannot roll this out to shared clinical workstations while this is still the only way to install Teams. C'mon MS, get this right!!!
-
Josh G
commented
The existing MSI solution is simply a more complicated method to do the same thing - install a copy of Teams to every user's AppData.
In an environment with systems that have dozens of users, this can cause significant disk space issues. In a clinical setting, you may have 50-100 individual user profiles on a single workstation, so a Teams install with an average size of ~500 MB (if updated), then you may be looking at 50GB just for Teams to be installed in each user profile.
-
Danny
commented
I would to be able to install this once per computer, & have it run for all authenticated users.
Please, Install once & forget! -
James
commented
Interested to see how Teams will be installed as a result of this upcoming change:
https://docs.microsoft.com/en-us/DeployOffice/teams-install -
Joe
commented
While we wait on MS to do something about this I found a third party solution that does exactly what we want.
These guys repackaged the MSI to install to Program Files. I've ran it on a test machine and it seems to work perfectly. Going third party is obviously not ideal but with MS pushing Teams so aggressively this is better than nothing at this point.
-
Anonymous
commented
Is there a fix for the Install Location yet?
-
Josh Gorciak
commented
Looks like there was a recent MSI update that supports an ALLUSER install that puts the app data in Program files: https://docs.microsoft.com/en-us/microsoftteams/teams-for-vdi