Forum Discussion

Brass Contributor

Jun 04, 2020

Solved

First Teams Call in a Teams Machine-Wide Install Causes Windows Defender Firewall Popup in WVD

When a Teams user in WVD issues first time call, he is presented with the attached sample popup to allow access via the Inbound Firewall ports. According to MS document: https://docs.microsoft.com/en-us/microsoftteams/get-clients the behavior is known issue. However, I was under the impression that a machine-wide install should not be putting teams in %Appdata% folder.

Please advise.

virtualmanc
Jun 05, 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

4 Replies

blindpete
Brass Contributor
Jun 05, 2020
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
- MarkF26
  Brass Contributor
  Jun 05, 2020
  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
  - virtualmanc
    Iron Contributor
    Jun 05, 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