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.
Make it a PWA, now you have a chromium compatible browser (Edgium) and put us out of our misery.
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!!!
Rob Nicholson commented
Totally flabbergasted this uservoice exists. Whilst the world has moved on, there are still billions of standalone Windows installations out there. I wondered why on a test Windows 2019 RDS server that Teams kept prompting to logon each time you logged off and back on. That's because with user profile disks (not the best idea but ho hum), the user's profile is deleted when you log off, inc. local and localnow. So bang - all local, localnow installs are a no-no. Long time before we can get rid of machine wide installs...
Some IT Guy commented
I found a workaround but its a manual one, Install teams on an admin account, copy teams shortcut to public\desktop
Copy the teams install setup file to public\desktop
users are now able to use that shortcut and open teams.
It will ask for Update.exe file which the PC grabs over the next minute automatically.
I'm not entirely sure whether the install file is what did the trick. Further testing needed but so far it's working for me.
Stop being idiots and make the Teams MSI install per machine not user. You guys act like you've never worked in a large organization before and had to roll out software to staff. Please fix this ****.
[Deleted User] commented
If your going to add Teams into Office 365 atleast install it automatically into Program files so all users can run it from a central location. Their settings should be the only thing being saved into APPDATA. Why in the world would you install the application into the users Appdata?
It would be great to be able to deploy Teams as ANY standard product.
Installed for each existing or future users. Not multiplying installation files per users, and with no good way to find the app for a new user creating a windows session (except poping an unwanted windows at the start).
Found this thread from the old thread, which I found because we have SRP in place and can't have users running exe's off that appdata (that is writable).
When's the fix?
Reza Prawirasatya commented
Hi Microsoft Teams Support,
I wasn't aware of Microsoft Teams just installed per user!
I have been researching on how to install per machine (NOT per user) since we have a lot of Conference Room computers and also loaner laptops.
Looks like I am not the only one with this problem. Would someone from Microsoft Teams make it available to install per machine?
Would you people just please go away? We threw you a bone and you are still crying. We have serious stuff to do up here in the ivory tower and you people need to stare being happy for all the great things we are inventing that you need but don't know it yet!
Chris Beattie commented
Assumed we were doing something wrong. Checked the documentation and confirmed Teams is included in O365 ProPlus installer, rolled it out to 500 devices and then realised it isn't actually installed at all because it's only installing the installer which can't install the app because the user is restricted and so now every user gets an escalation prompt at every logon! What an epic fail.
Disturbed Customer commented
give us an easy way to prevent the desktop shortcut...this is a pathetic way to treat your customers and shove this down our throats
So annoyed that Microsoft closed the original request after delivering absolutely nothing.
If you combine the number of votes for those two we're well over 1000 votes.
Chris, to answer your question... you have to suck it up because Microsoft don't care.
This is the most stupid excuse for software I have seen in ages!
If you install it in program files using an MSI installer, that should be it, it shouldn't copy it to %appdata%!?
Our users have a 1GB quota for their redirected folders, which includes AppData. We can't give them Teams because it would mean that 350MB+ would go into their AppData, for every user! What are we supposed to do when we have 650 users all wasting 350MB on duplicate Teams installers!?
Can't believe this doesn't exist. Skype for Business Online shuts down July 31 next year. We need at least 6 months to test and roll out teams. If this isn't fixed soon we we need to look at a Skype replacement that is not teams.
Hatt Jarlin commented
Spent all day trying to figure out how to get Teams working in our RemoteApp environment with User Profile Disks and Software Restriction Policies. Literally can't do it without compromising security or letting Teams install to C:\ProgramData\ (which it seems to do for some inexplicable reason if %LocalAppData% can't be accessed).
Microsoft need to allow the entire application to be installed to %ProgramFiles% and only store user-specific data in AppData.
Edgy Boi commented
I agree we change our policies and we are nto allow to run programs from user profile and also issues with our deployment software exist cause team is not installing to users that are not already log in etc we need this installed to work on program files
Any progress on this? This is unbelievable
This is bad for busy meeting room computers where disks are small and constantly filling up.