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.
The team is looking into this feature and considering solutions. We will update when there is more information to share.
I think it is relatively disrespectful that Microsoft does not respond to this inquiry with so many posts. Here they have chosen a useless method of installing software and then they think that people will give up complaining if they just fail to respond.
It should not be necessary to explain why Microsoft needs to change this. The way it is done now is just wrong.
James Smith commented
I'm trying to use RDS with Teams and camera is not showing.
Arjan Kop commented
You are quite right! I've had to spend about 20 hours figuring out how to unroll Teams in an RDS environment, with AppLocker enabled. After that finally worked, the initial request ('find a way to let users plan meetings in Teams from their Outlook Calendars') is still only partly resolved. Installing software in a user's AppData folder feels awkward to begin with, anyway.
This is a global security fail!
Maybe it is a possibility to remove the write Access on the Teams Appdata-Folder for each user..
WTF, Microsoft, WHAT ARE YOU DOING?
You suck you own best practice with this ******* install practice….
No executable files should allowed to run in Folders who the user has write acces!!!
Thats is your OWN RULE Microsoft! Why do you breake with your onw rules?
Absolutely ridiculous. This has the potential to scupper ongoing and future customer engagements looking to utilise Teams.
What is the justification for doing it any differently from all your other products!?
What an absolute joke Microsoft. Our users have started to install Teams through word of mouth meaning many user based installs, each showing Firewall prompts that the users cannot Allow as none are local admins.
In addition we have had a software restriction GPO in place preventing the running of executables from %APPDATA% thus all Teams installs have been put under %PROGRAMDATA% instead which is terrible for our Remote Desktop servers with bloated C drives plus Teams doesn't roam with the users' UPD! What a terrible, terrible mess.
Microsoft needs to release a proper machine-wide installer that works but more importantly provide a script that will completely remove all user-based installs of Teams accounting for both possible %APPDATA% and %PROGRAMDATA% install locations. It would be really helpful too if the full 365 installer includes the ability to do this clean up!
Nick Jones commented
In a site like ours that has several hundred profiles on each desktop dumping a 300mb install on limited local storage is not going to work.
Secondly, reinstalling the app is horrifically painful - we are experiencing the app failing to launch fairly frequently (process appears for a couple of seconds then disappears). Doing a reinstall per user per machine is a waste of time.
Minor point, because it's per user (non roaming) when the user moves to another desktop their icon is redirected and appears broken.
All of this would be solved if it was a normal per-machine install. Let's get this suggestion upvoted for a proper solution!
Bennett Blodinger commented
This goes against Microsoft's own suggestions and requirements.
%AppData% is not for storing program files.
AppLocker can't properly be used.
Windows Firewall becomes a mess.
Please follow the OneDrive team and make a scheduled task to update the software, put it in the correct location, and continue following software standards.
Cuneyt Ozturk commented
Dear Teams Developers,
Please consider developing Teams installation msi as a per machine installer.
The process of installing, updating and uninstalling Teams application is quite complicated currently.
I completely do not understand this situation. OneDrive went through this EXACT same cycle. They now have a system level installation that autoupdates without the need for local user admin rights. Many applications do this in different ways. Edge/OneDrive/Chrome... list goes on.
There are tons of solutions out there. For a team that is managing a collaborative tool, it is puzzling they don't at least collaborate with other MS teams that went through the exact same development cycle which HAVE a solution.
The value of MCP is now ZERO....as Microsoft themselves ignores the guidance in all those countless exam books and tests!
What a PoS!
We spent how much money and how many hours learning to adopt the Microsoft "best practices"....only for MS to ignore their own advice??? We cite Microsoft's own guidance and are told to "live with it???"
Suddenly Microsoft themselves is a MALWARE PROVIDER, like Dropbox, Slack, and Zoom! I guess if they couldn't beat them, Redmond just decided to join them...
@George - it does work, make sure you use the property ALLUSER=1 (NOT ALLUSERS=1 which is something entirely different).
George Perolli commented
John Babbit unless I read the wrong article that solution does not work for a Microsoft RDS environment because it does not resolve the root problem. Teams is still installed into APPDATA but the only difference is that APPDATA is then deleted when the user logs out.
John Babbitt commented
Hello! I understand you want a machine-install instead of user-install. If you had read further down, you would have found the answer. But, I'll post it here again so that it's showing up as a newer comment:
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.
George Perolli commented
While Microsoft might have unlimited storage space in its environment, we that live in the real world do not have that luxury. Please allow for single install and then it can be updated using Windows Updates.
Carl Green commented
agree there needs to be a per machine install to the program files directory. we have a RDS environment of 250 users and each user now as a 500MB minimum Teams folder under their AppData folder. as users roam between servers the space soon gets chewed up.
i have almost 27000 employees
within the domain my apps are allowed to communicate out
due to covid-19 they are now at home
just tell me how to create a firewall rule which is rolled out over GPO
do you really want us to create all out rules for the public firewall profile ?
fix this please asap