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
137 comments
-
Andreas Norling
commented
So Microsoft, are you going to keep ignoring this suggestion?
-
Tony
commented
Please product an enterprise installer
-
Anonymous
commented
This is such a pain.
For now Teams is useless for corporate IT. Microsoft demands money for a product that is significantly worse then competitors offer. Slack has a normal .msi installer that just installs the app to program files...Please consider this
-
Peter
commented
Please, solve this
-
Neil Thomson
commented
Please make this run from a system location, as user writable areas make it hard for application whitelisting to work. Also the auto updating makes it hard as well.
-
Anonymous
commented
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.
Any suggestion? -
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.
-
Oliver Hunger
commented
This is a global security fail!
-
Oliver Hunger
commented
Maybe it is a possibility to remove the write Access on the Teams Appdata-Folder for each user..
-
Oliver Hunger
commented
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?
-
Sam
commented
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!?
-
Anonymous
commented
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.Best wishes
-
dandirk
commented
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.
-
Anonymous
commented
The value of MCP is now ZERO....as Microsoft themselves ignores the guidance in all those countless exam books and tests!
-
Anonymous
commented
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...
-
Anonymous
commented
@George - it does work, make sure you use the property ALLUSER=1 (NOT ALLUSERS=1 which is something entirely different).