Install in Program Files directory
We simply can't fathom the idea that Microsoft allows for an Enterprise-level application like Teams to be installed on the user's AppData folder. As IT admins, we need the ability to install this in the Program Files directory. You recently released an MSI package, but that still copies the executable over to the user's %localappdata% directory. This is not secure!
Anonymous
shared this idea
27 comments
-
Jean-Sébastien Frenette
commented
Teams can be installed in program files. I'm not sure why you guys are not using this method. BTW, teams in appdata is to be able to have autoupdate for an app that update like each 2 weeks. It could be with a background service instead but they used this method.
To make a machine install, real one in program files, you must use the msi and use flags ALLUSER=1 ALLUSERS=1. You also have to add a registry key so it think it's in a VDI environment.
See: https://docs.microsoft.com/en-us/microsoftteams/teams-for-vdi#deploy-the-teams-desktop-app-to-the-vm
-
Gary Lee
commented
Echoing what other people are saying here, this is causing us no end of issues with our users who have redirected or roaming AppData folders. They don't understand why it breaks or disappears entirely when they log onto multiple workstations and end up blaming us. I'm not exactly cool with having to add a software restriction exception to let users execute the app from their profiles either! Clearly no thought has gone into how enterprises will deal with this.
Ease of automatic updates is not adequate justification for how this "feature" has been implemented. Chrome manages to allow users to update without admin rights while still having the app located in Program Files and thats not even a first party application!
-
Michael
commented
This is so frustrating and disappointing that it has gone on so long. We have weekly issues at one client or another because of teams in appdata, either it's filling up hard drives or it's broken because of profile redirection. There are what look like simple fixes online but the number of those fixes shows that there isn't really a simple fix.
The actual fix seems to be to run it out of program files like every other program.
-
Anonymous
commented
Hello to everyone facing(fighting) this poor choice made by Microsoft.
Due to restriction and user's profile limited size(about 500mb) installing the client as Microsoft intended was simply not feasible... My current solution:
1) install Teams as per usual;
2) copy AppData\Local\Microsoft\Teams to %PROGRAMFILES%;
3) in AppData\Local\Microsoft\Teams\ delete all but: app.ico, current, packages
4) create a link to AppData\Local\Microsoft\Teams\current\Teams.exe in your desired location(i use public desktop);
DONE
Now it takes about 20Mb in user's AppData, update is managed by you, each user has it's own
Survives sysprep and domain deploy
Hope it helps -
Sreve P
commented
I am looking to deploy Teams to Fire Stations, for which many people share desktop PCs. We already have (roaming) profile related issues with these PCs, so it would be good to have the ability to install the app to the device rather than individual profiles.
-
Brent Fanguy
commented
where are we on this? these comments are from 2018
-
Systems Administrator
commented
We have the same problem, please make a Program Files version of Teams. this is giving us so much problems. please give us a fix.
-
Eumaeus Barrowman
commented
This is causing a lot of issues. Why do i need to install in profile?!
-
Antonio Figueiredo
commented
Can we please get some type of response there are hundreds of admins who have to deal with this. Please implement something like onedrive has as mentioned below.
-
Robert
commented
"Frankly whoever at Microsoft thought installing software in the user's profile was a good idea should be fired and banned from using Windows for life."
i can only sign this. this behaviour is horrible at best. with teams installing (multiple times) in user directories, there is now no way to set firewall rules for "teams.exe" via group policy. which is a requirement if "Apply local firewall rules" is set to "No", which is a standard in our hardenend environments.
and i won't even start with application whitelisting.
this grave mistake needs to be fixed asap.
-
Daniel
commented
It should be possible to do, because with OneDrive Microsoft also added a "/alluser" parameter and now its possible to install it central in the Porgram Files Folder.
Much appreciated if that also comes for Teams. -
Tony Cozzolino
commented
Why doesn't Microsoft give the option to install to program files i.e. like chrome has a deployment .msi for Organisations?
-
Mister-X
commented
try this, it install teams in program folder
https://www.masterpackager.com/blog/how-microsoft-teams-installer-should-have-looked-like-from-the-beginning -
HB
commented
I agree with you.
Current install folder is not good for re-installation. I request to improve the install system to legacy style. eg: skype for business or office suites. -
Mark Hardisty
commented
Concur with every opinion on this thread.
-
Anonymous
commented
The opening of Teams alone generates around 800 files in% appdata%. We use roaming profiles with folder redirection to a NAS. We have been using this type of configuration for 15 years and it has never given us problems except with the use of Teams. We have had to choose Teams on the Web due to the impossibility of opening the desktop version without errors. After several open cases and so much log that it generates and is useless. The only solution I have found has been to install FSLogix to contain% appdata% on the NAS. Please optimize and redesign.
Thank you.
-
Simon Jackson
commented
Patching MS Office properly deploys the 'machine wide installer'.
Group Policy Software restriction policy prevents MSI files installing under %userprofile% - this includes %appdata% and %localappdata...
So then randomly microsoft installer extracts to %programdata%\%Username%\ and installs Teams there instead...WHY ??? Why not the good old %ProgramFiles% folder like every other MS Office Product?
It's a nightmare trying to script cleaning up old user installs, patching exes, keeping HDDs nice and clean etc.
The install command for teams installer has a switch for 'all users' but still installs in %programdata%\%username%... errr thats not right!
-
Christopher Holmes
commented
I can not wrap my head around this insanity. I just spent 12 hours trying to make my security product work with your product for this various reason.
Lets put this simply. Where do users get virus and spyware? One Guess... Right next to your install of Teams! So when a nefarious actor targets your software and all the users profiles, you are going to wish you had a better security posture.
Oh btw, I can not break security profile per cyber to install Teams. We have a process that blocks all .exe from running within the user profile... Including the craziness on how you update, then launch the product.
-
A Consultant left Alone
commented
Sorry for my english..
Apart that you are obviously a stupid team, but how can you pretend to have instructed people for more than 20y to use roaming, to redirect data, to keep profiles light as possible, bla bla bla... and now, you spread out a unbelivable abomination piece of software that, targeted to enterprise, is everithing except respectfull for all your own guidelines...Morons! it's time to work for enterprise not for your own lazyness!!!
-
C0rmang
commented
Another reason Teams should follow standards... https://social.technet.microsoft.com/Forums/en-US/1414d5a6-1ce8-4cf4-aaa5-a7d3172d5c36/microsoft-teams-excessive-bandwidth-usage-on-shared-computers?forum=msteams&prof=required