

The diagram below depicts how WebRTC for Teams works using Windows Virtual Desktop. It has been suggested that you would achieve the best experience using a Windows 10 Client.

Peer to peer (P2P) – traffic will flow from the user to user device and rendering is completed at the physical endpoint.This method uses the client hardware to encode and decode. This provides a better user experience for the WVD users on the Teams call.

This does not mean all the problems go away when using a GPU…ĪV redirection for Teams essentially offloads (bypasses) the Window Virtual Desktop Virtual Machine and sends the A/V data directly to the call clients. It is also important to note, that re-encoding on a VM without a GPU is CPU intensive and most often impacts the host and other users logged using the desktop. This method creates latency, that then impacts the performance and quality of the video and possibly the underlining host performance. So previously, MS Teams’s Audio and Video on WVD was encoded and decoded multiple times before reaching the other end of the call.

Check the version for “ WVD Media Optimised” status.Configure RDP Properties (configure device redirection for Teams).Install the Remote Desktop WebRTC Service.The link and video for this is provided at the end of this article. The tool is a manual function however, I have also created a script for deploying using a Custom Script Extension though Azure’s ARM panel. In this article, I will run through the summary stages of preparing for MS Teams on Windows Virtual Desktop and discuss the tool I have created to streamline the whole process. Read more here from KamVedBrat on the announcement A/V Redirection for Microsoft Teams is one of the GA features that many have been waiting for. Microsoft announced the General Release (GA) of Microsoft Teams on Windows Virtual Desktop (with media optimisation) on Monday the 27th of July 2020.
