machine installer - NO MORE INSTALLS IN APPDATA!
Your "completion" of the most upvoted request: "improve Install options - Install for all users and install location" is a complete joke. Having an MSI install in Program Files that just turns around and installs another executable in every user's AppData is hack-kneed at best. It's a band-aid over a dumpster fire. Get the exe out of AppData. APPS BELONG IN PROGRAM FILES. You haven't addressed the dozens or hundreds of redundant copies made in every profile on a shared workspace. USERS DON'T GET TO INSTALL EXE's IN APPDATA! PERIOD! We will not install Teams until you fix this garbage for real.
michael m commented
When it updates it puts a new copy and an old copy in every users' appdata folder on every RDS.
200 users, 5 RDS, local appdata.. 488 gigs of cloud storage we're paying for monthly.
Ray Davis commented
Microsoft Teams developers. Many of us run RDSH/VDI, the teams installing in a user profile in the word is a not ideal. Yea, I know you guys have the machine installer. Which thank you for, however that still doesn’t stop the user from actually going and downloading the team (user installer)
User A could click a links and say download team today, then follow the instructions. All the hard work many of us put into our environments around RDSH/VDI will then be for nothing. This will lead into many hours of troubleshooting and just can’t be avoided all together.
Some of us even go down to the level to stop it.
1. Uninstall user context teams, Delete the folders in appdata\local\ms\teams and programdata\user\ms\teams
2. Then Stage the folder in appdata\local\ms\teams and programdata\user\ms\teams
3. Then run ICACLS to remove permissions so the user can’t install it, however the user could just take ownership of the folders in question, and reset the permissions as it was pointed out to me
4. Redirect the teams download page to a dead site. (Stop the user from trying to install the user profile version) But that just clunky as well.
5. Block the user teams hash. Hopefully it's not the same for the machine one. Not sure if app locker can stop it better. (could lead into more issues)
6. Block the Teams installer with Software Restrictions, but they could rename the Teams.exe or teams_installer*.exe to another name to get around this.
Would the solution to end all the user install profile stuff nightmare, is to detect if its in a VM/VDI/RDSH environment and put a message denying the installer “consult with your Administration for the Teams Installer for EUC environment? Detect if its not a actual physical PC and don’t allow the user install.
Glenn Turner commented
Suggest that you vote for this one instead: