AVD Media Not Connected

[Vanbogie1200]

We have a number of AVDs that are showing 'Media Not Connected'. It's not a universal issue in our environment by any means. We have tried our current packaged version as well as current versions downloaded directly from MS.

Test device: Windows 10 21H1
Remote Desktop WebRTC Redirector Service installed: 1.1.2106.14001 (Reinstalled for testing)
For troubleshooting:
Zscaler: Disabled
McAfee ENS: Uninstalled

Windows Advanced Firewall: Disabled (Azure firewall is up)

Teams Uninstalled
Dirs removed or verified to have been removed:

• C:\Program Files (x86)\Microsoft\TeamsPresenceAddin
• C:\Program Files (x86)\Microsoft\TeamsMeetingAddin
• C:\Program Files (x86)\Microsoft\Teams
• C:\Users\VanbogK\AppData\Local\Microsoft\Teams
• C:\Users\VanbogK\AppData\Local\Microsoft\TeamsPresenceAddin
• C:\Users\VanbogK\AppData\Local\Microsoft\TeamsMeetingAddin
• C:\Users\VanbogK\AppData\Roaming\Teams
• C:\Users\VanbogK\AppData\Roaming\Microsoft\Teams
• C:\Users\VanbogK\AppData\Roaming\Microsoft Teams\logs

Teams Reinstalled:

• Relevant parameters used: ALLUSERS=1 /qn ALLUSER=1
• (Get-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\Teams' -ErrorAction SilentlyContinue).IsWVDEnvironment = 1
• (get-ItemProperty -Path 'HKLM:SOFTWARE\WOW6432Node\Microsoft\Teams' -erroraction SilentlyContinue).Alluser = 1
• Verified no VMWare Keys present in registry

Results after all that:
"You have Microsoft Teams Version 1.4.00.32771 (64-bit). AVD Media Not Connected."
Once again, installing the current version from MS results in the same problem. Our package's media is due for a media update.
 
Am I missing something that might be preventing Teams from showing 'AVD Media Optimized'?

[#2]

We had the same issue - it was WebRTC timing out before the client hardware got connected. Install the latest WebRTC (1.4.2111.18001 as of writing) - this has a longer timeout (and also you can increase the timeout if necessary). Resolved 99% of our redirection issues.

[#3]

I've updated the WebRTC client and reinstalled Teams to no effect. How do you increase the timeout for WebRTC, is it a registry value that needs to be added?

[#4]

when we were using a specific version of the client before the public release, the regkey was:
• [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\AddIns\WebRTC Redirector]
Set "HandshakeTimeout" to something greater than 10000 (decimal) as below.


please note I'm not taking any responsibility for this and haven't tested this setting out (because the latest release sorted the issue out for us anyway) and if you're getting the issue on only a small number of users you may end up making things worse.

[#5]

@pcluskey 

I added the new property:

New-ItemProperty -Path 'hklm:\SYSTEM\CurrentControlSet\Control\Terminal Server\AddIns\WebRTC Redirector' -Name 'HandshakeTimeout' -Value 20000 -PropertyType DWORD

It didn't seem to correct the issue, I even increased it to 100000 just to see with no luck. Thank you very much for your suggestion though. Maybe it wil have an effect on some of the other devices with this issue.

[#6 · Accepted solution]

We are investigating this issue as some other customers are having this issue as well. If updating the WebSocket service (1.4.2111.18001) didn't solve the issue, we need more info to troubleshoot. Please file a support ticket and we will contact you for more information.