Teams should not be installed under %userprofile% but %program files% instead
Teams should not be installed under %userprofile% but %program files% instead
Anonymous
shared this idea
5 comments
-
Anonymous
commented
i strongly agree with that. We have deployed Teams at all our company but, what about the computers in the meeting rooms? Every user is going to have a meeting, every installation of teams that is needed. And we can't have up to 100 profiles at every computer only for the remote possibility that a determinated user could do meetings with teams in the future...
-
Alan Birch
commented
Wow, this is from 2017 and still in 2019 it's installing inside the user profile. Might be fine for a corporate but a school with shared desktops needs to have user profiles deleted or all I'd be doing is cleaning hard drives as they fill up with them. It's even worse now as it installs as part of Click to Run so every day on multiple PCs for multiple logins, 500MB is being downloaded and installed.
-
Aaron
commented
Completely agree. Installing to appdata is going to kill our RDS rollout userdisks. Every user who logs in is going to have another copy of the program stored in the profile for no reason.
@Andreas - You are completely right and as an IT admin, I know that access rights are created for a reason and thus should not be undermined by a software dev who created the ability to place said access rights.
-
Bob
commented
I am finding that when an error comes up, like "Yikes, someone pulled the plug", and the user is remote, it's difficult to troubleshoot. If I need to uninstall, I can't because it's in their profile.
I've also noticed that the program is installed in multiple locations under each user profile. Under AppData\Local and AppData\Roaming. C'mon, please.
-
Andreas
commented
Should? There are likely arguments for both, probably installed at that location because of different access rights. So if something should be changed an option to change the location might be better.