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

Brass Contributor

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: 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.


4 Replies

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% ?



best response confirmed by MarkF26 (Brass Contributor)

@MarkF26 To use Teams machine-wide installer you need to install it in a certain way - see here - 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 @Neil McLoughlin , 


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 to make it work. 


Thank you so much.