Forum Discussion
First Teams Call in a Teams Machine-Wide Install Causes Windows Defender Firewall Popup in WVD
- Jun 06, 2020
MarkF26 To use Teams machine-wide installer you need to install it in a certain way - see here - https://docs.microsoft.com/en-us/azure/virtual-desktop/teams-on-wvd The most important one is "msiexec /i <path_to_msi> /l*v <install_logfile_name> ALLUSER=1 ALLUSERS=1" The ALLUSER command tells it to install the machine wide installer, and places it into C:\Program Files(x86) instead of APPDATA
Hi MarkF26
You may wont take a look a this blog post https://msendpointmgr.com/2020/03/29/managing-microsoft-teams-firewall-requirements-with-intune/
Pete
Hi blindpete ,
Thanks for the tip. I didnt know InTune can do that. That's great !
I still question why Teams machine-wide install is adding Teams.exe per user %appdata% ?
Mark
- virtualmancJun 06, 2020Iron Contributor
MarkF26 To use Teams machine-wide installer you need to install it in a certain way - see here - https://docs.microsoft.com/en-us/azure/virtual-desktop/teams-on-wvd The most important one is "msiexec /i <path_to_msi> /l*v <install_logfile_name> ALLUSER=1 ALLUSERS=1" The ALLUSER command tells it to install the machine wide installer, and places it into C:\Program Files(x86) instead of APPDATA
- MarkF26Jun 19, 2020Brass Contributor
Hi virtualmanc ,
Thanks for the reply. It took me a while to find time to uninstall Teams, and try the referenced KB. I first ran into a message that said "Cannot Install for all Users when a VDI environment is not detected". It turned out to be I needed the version of Team_windows_X64.msi with the Content Created @ 5/14/2020 (Version 1.3.0.13565) to make it work.
Thank you so much.
Mark