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
6 comments
-
Teams Installer Sucks
commented
This needs to be merged with https://microsoftteams.uservoice.com/forums/555103-public/suggestions/34768153-improve-install-options-install-for-all-users-an
Microsoft pointing people to separate threads makes this a lower priority, helping them justify their poor decisions.
-
Sylvester
commented
We also have the same problem. There is no way to control the application from company-wide policy perspective when installed in the AppData folder, so it is not secure and deviating from Microsoft best practices! The lack of installing it in a enterprise controlled folder is not helping the user adoption as on an IT level we already get tons of resistance (and with good reason) on deploying the application in the first place..
-
Anonymous
commented
Until we have this, we will not deploy teams and hang on to "legacy" Skype for as long as possible (should apply to OS X too). We have 8,500 devices. 4500 of these are shared by 17,000 users who get a fresh profile every time they login! There needs to be a device based installation!
-
CAT-hs
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've seen the response from the feature team that it is not installed in Program Files to ensure users get the newest features and fixes quickly and ensure all users are getting the best experience possible from MS Teams, and that they feel that their updates and features are being released too quickly to provide a god experience if admin credentials are required to install and update. This is lazy, short-sighted, and unfriendly to (what seems to be) the primary audience for the Teams application (enterprise).
Many applications exist that are installed in the proper location (program files) and still automatically update themselves without additional administrator prompts, and there are many methods to do this. For example, you can publish updates as frequently as you want to Microsoft Store or Windows update (granted the later will still update most users weekly at best with default config). There are also options like the Google Chrome for enterprise MSI model with an updater installed and configured during the initial install so that admin rights are not needed after the first install.
This design choice is driving my company away from Office 365 and towards Slack. Yes, they are basing the decision to go to subscription model for office vs keeping stand alone install and internally managed servers heavily on the the collaboration tool they decide on, and they figure that if either tool will be difficult to control properly (compared to normal office apps) then they might as well NOT pay the huge user subscription fee.
-
Andrzej Demski
commented
This is the first time when someone used security as a level of insanity :)
Program files copied to program files folder solve the issue, but wont be supported by MS.
I am optimistic, there are worse ways to make fun of users. -
Aaron
commented
Security aside, access rules are created by management and IT admins for a reason and should not be undermined by the company that developed the access rules. Also, this has big ramifications for RDS rollouts. Every user who installs will have the same program placed in their profile. I am demoing and that's ~350MB in my profile. So, using that for a benchmark, for every 3 users who install the program, that's over a gig of completely redundant files.