Add a detect if in RDSH/VDI/VM and deny user profile installer
Microsoft Teams developers. Many of us run RDSH/VDI, the team's installer in a user profile in the word of VDI/RDSH is 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). I can understand at times why it’s a Click to Run application. It makes sense for a PC, but not a VDI/RDSH setup. You guys have made a lot of progress around our needs so thank you for this. Please consider this as well.
User A could click a link and it states download teams 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 to many hours of troubleshooting and just can’t be avoided altogether.
Some of us even go down to the level to stop it.
- Uninstall user context teams, Delete the folders in appdata\local\ms\teams and programdata\user\ms\teams
Then Stage the folder in appdata\local\ms\teams and programdata\user\ms\teams
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
Redirect the team's download page to a dead site. (Stop the user from trying to install the user profile version) But that just clunky as well.
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 to more issues)
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 end all the user install profile stuff nightmare, be to detect if it's 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 it's not an actual physical PC and doesn’t allow the user install.
Remove the Teams installer for the WEB related setup as well would be nice.
Thank you for the time to present this, I hope you consider this for many of us in this situation.
Thank you again.
It could be as easy as detecting if the machine-wide version has been installed, then don't install the user-version (I guess?)
Leee Jeffries commented
Great idea Ray, my only caveat. Have a regkey on the machine side that is checked if this is allowed to run. If it exists and is set correctly then the installer can proceed. I've seen a few places rollout vdi with optimisations in place and allow users to install it directly.
Ryan Gallier commented
Great idea. Yes, please do this!