SOLVED

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

%3CLINGO-SUB%20id%3D%22lingo-sub-1441871%22%20slang%3D%22en-US%22%3EFirst%20Teams%20Call%20in%20a%20Teams%20Machine-Wide%20Install%20Causes%20Windows%20Defender%20Firewall%20Popup%20in%20WVD%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1441871%22%20slang%3D%22en-US%22%3E%3CP%3EWhen%20a%20Teams%20user%20in%20WVD%20issues%20first%20time%20call%2C%20he%20is%20presented%20with%20the%20attached%20sample%20popup%20to%20allow%20access%20via%20the%20Inbound%20Firewall%20ports.%20According%20to%20MS%20document%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fget-clients%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fget-clients%3C%2FA%3E%26nbsp%3Bthe%20behavior%20is%20known%20issue.%20However%2C%20I%20was%20under%20the%20impression%20that%20a%20machine-wide%20install%20should%20not%20be%20putting%20teams%20in%20%25Appdata%25%20folder.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20advise.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1443448%22%20slang%3D%22en-US%22%3ERe%3A%20First%20Teams%20Call%20in%20a%20Teams%20Machine-Wide%20Install%20Causes%20Windows%20Defender%20Firewall%20Popup%20in%20WVD%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1443448%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F384632%22%20target%3D%22_blank%22%3E%40MarkF26%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3EYou%20may%20wont%20take%20a%20look%20a%20this%20blog%20post%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fmsendpointmgr.com%2F2020%2F03%2F29%2Fmanaging-microsoft-teams-firewall-requirements-with-intune%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fmsendpointmgr.com%2F2020%2F03%2F29%2Fmanaging-microsoft-teams-firewall-requirements-with-intune%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPete%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1443518%22%20slang%3D%22en-US%22%3ERe%3A%20First%20Teams%20Call%20in%20a%20Teams%20Machine-Wide%20Install%20Causes%20Windows%20Defender%20Firewall%20Popup%20in%20WVD%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1443518%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F521235%22%20target%3D%22_blank%22%3E%40blindpete%3C%2FA%3E%26nbsp%3B%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20the%20tip.%20I%20didnt%20know%20InTune%20can%20do%20that.%20That's%20great%20!%3C%2FP%3E%3CP%3EI%20still%20question%20why%20Teams%20machine-wide%20install%20is%20adding%20Teams.exe%20per%20user%20%25appdata%25%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMark%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1444586%22%20slang%3D%22en-US%22%3ERe%3A%20First%20Teams%20Call%20in%20a%20Teams%20Machine-Wide%20Install%20Causes%20Windows%20Defender%20Firewall%20Popup%20in%20WVD%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1444586%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F384632%22%20target%3D%22_blank%22%3E%40MarkF26%3C%2FA%3E%26nbsp%3BTo%20use%20Teams%20machine-wide%20installer%20you%20need%20to%20install%20it%20in%20a%20certain%20way%20-%20see%20here%20-%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fvirtual-desktop%2Fteams-on-wvd%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fvirtual-desktop%2Fteams-on-wvd%3C%2FA%3E%26nbsp%3BThe%20most%20important%20one%20is%20%22%3CSPAN%3Emsiexec%20%2Fi%20%3CPATH_TO_MSI%3E%20%2Fl*v%20%3CINSTALL_LOGFILE_NAME%3E%20ALLUSER%3D1%20ALLUSERS%3D1%22%26nbsp%3B%20The%20ALLUSER%20command%20tells%20it%20to%20install%20the%20machine%20wide%20installer%2C%20and%20places%20it%20into%20C%3A%5CProgram%20Files(x86)%20instead%20of%20APPDATA%3C%2FINSTALL_LOGFILE_NAME%3E%3C%2FPATH_TO_MSI%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1477973%22%20slang%3D%22en-US%22%3ERe%3A%20First%20Teams%20Call%20in%20a%20Teams%20Machine-Wide%20Install%20Causes%20Windows%20Defender%20Firewall%20Popup%20in%20WVD%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1477973%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F235785%22%20target%3D%22_blank%22%3E%40Neil%20McLoughlin%3C%2FA%3E%26nbsp%3B%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20the%20reply.%20It%20took%20me%20a%20while%20to%20find%20time%20to%20uninstall%20Teams%2C%20and%20try%20the%20referenced%20KB.%20I%20first%20ran%20into%20a%20message%20that%20said%20%22Cannot%20Install%20for%20all%20Users%20when%20a%20VDI%20environment%20is%20not%20detected%22.%20It%20turned%20out%20to%20be%20I%20needed%20the%20version%20of%20Team_windows_X64.msi%20with%20the%20Content%20Created%26nbsp%3B%40%205%2F14%2F2020%20(Version%201.3.0.13565)%20to%20make%20it%20work.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20so%20much.%3C%2FP%3E%3CP%3EMark%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional 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: 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.

 

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

 

Mark

best response confirmed by MarkF26 (Occasional Contributor)
Solution

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

 

Thank you so much.

Mark