Forum Discussion
AVD Media Not Connected
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'?
- 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.
- 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.
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?
- 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.
- Yun_Liu
Microsoft
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.- Yun_Liu
Have you tried updating both the host WebRTC redirector service and the Remote Desktop client to the latest version?
We learn't the following using a Microsoft Support Case.
MSRDC versions 1.2.3667, 1.2.3770 and 1.2.3918 have inherited a dependency on msvcp140.dll and client machines without this binary installed will cause optimizations to fail. Upcoming MSRDC release (2/28) will have a fix to address this,
Installing the latest VC++ redistributable - Latest supported Visual C++ Redistributable downloads | Microsoft Learn resolves the problem.
