Configuring Microsoft Teams for Windows Virtual Desktop (WVD)


Introduction

Microsoft announced the General Release (GA) of Microsoft Teams on Windows Virtual Desktop (with media optimisation) on Monday the 27th of July 2020. A/V Redirection for Microsoft Teams is one of the GA features that many have been waiting for. Read more here from KamVedBrat on the announcement https://azure.microsoft.com/en-us/blog/new-windows-virtual-desktop-capabilities-now-generally-available/

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. 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. The link and video for this is provided at the end of this article.

High level configuration Steps:

  1. Prepare
  2. Apply the WVD required registry key
  3. Install the C++ Runtime requirement
  4. Install the Remote Desktop WebRTC Service.
  5. Install the Teams desktop App
  6. Configure RDP Properties (configure device redirection for Teams)
  7. Restart
  8. Check the version for “WVD Media Optimised” status
  9. Test

What is WebRTC-based P2P:

So previously, MS Teams’s Audio and Video on WVD was encoded and decoded multiple times before reaching the other end of the call. This method creates latency, that then impacts the performance and quality of the video and possibly the underlining host performance. 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 does not mean all the problems go away when using a GPU…

AV redirection for Teams essentially offloads (bypasses) the Window Virtual Desktop Virtual Machine and sends the A/V data directly to the call clients. This provides a better user experience for the WVD users on the Teams call. This method uses the client hardware to encode and decode.

Key points:

  • Peer to peer (P2P) – traffic will flow from the user to user device and rendering is completed at the physical endpoint.
  • It is also important to note that devices will be redirected using the same hardware device to support better hardware redirection support.
  • One key benefit of using a Windows 10 client is the benefits of using the modern media stack including HW video decoding. It has been suggested that you would achieve the best experience using a Windows 10 Client.

WebRTC Diagram for Teams

The diagram below depicts how WebRTC for Teams works using Windows Virtual Desktop.

Preparation for Microsoft teams

The first step (step 1.) is to ensure that all the client devices, firewalls and other security devices do not restrict the following:

PortsUDP ports 3478 through 3481
IP addresses13.107.64.0/1852.112.0.0/14, and 52.120.0.0/14

Bandwidth Requirements:

As with most things these days, ensure that you check, yours’s or your customers network before deploying or using Microsoft Teams.

Bandwidth(up/down)Scenarios
30 kbpsPeer-to-peer audio calling
130 kbpsPeer-to-peer audio calling and screen sharing
500 kbpsPeer-to-peer quality video calling 360p at 30fps
1.2 MbpsPeer-to-peer HD quality video calling with resolution of HD 720p at 30fps
1.5 MbpsPeer-to-peer HD quality video calling with resolution of HD 1080p at 30fps
500kbps/1MbpsGroup Video calling
1Mbps/2MbpsHD Group video calling (540p videos on 1080p screen)

Microsoft Official Article covers the various different recommendations.

*Ensure that you use the Teams Desktop App version 1.3.00.4461 or later.

Install pre-requisites

Step 2. Creating the Registry Key:

reg add "HKLM\SOFTWARE\Microsoft\Teams" /v IsWVDEnvironment /t REG_DWORD /d 1 /f

The following can be run using the Command line or PowerShell. This will add a entry into “HKLM\SOFTWARE\Microsoft\Teams” to identify the host as running in Windows Virtual Desktop.

Step 3. Install the latest Visual C++ runtime

You need to ensure that you have the latest (supported) Visual C++ runtime version. you can download this here: Microsoft Visual C++ Redistribute

screenshot showing C++ Runtime has been installed Successfully

Check to ensure the runtime has been installed. As shown in the screenshot below, you can see this is now installed on my lab.

Screenshot showing installed C++ runtime.

Step 4. Install Remote Desktop WebRTC redirector Service.

The next step is to install the Remote Desktop WebRTC redirector service. This can be downloaded here: WebSocket Service .

Ensure you use version 1.0.2006.11001 or above.

Once the install has completed, check “Programs and Features” or “add and remove programs” to ensure The RD WebRTC redirector service has been installed.

Then check to ensure that the service is shown and is in a running state.

You should also see the “Remote Desktop Services WebRTC Redirector” within “Services”.

Step 5. Installing Microsoft Teams:

Download Microsoft Teams MSI package here: https://docs.microsoft.com/en-us/microsoftteams/teams-for-vdi#deploy-the-teams-desktop-app-to-the-vm/

Then use the following msiexec commands to install a per-machine installation:

msiexec /i <path_to_msi> /l*v <install_logfile_name> ALLUSER=1 ALLUSERS=1
Example:
msiexec /i "C:\temp\Teams_windows_x64.msi" /l*v teamsinstall.txt ALLUSER=1 ALLUSERS=1 

Here is a screenshot showing the cmd I used to install the per-machine install.

You now need to ensure that Microsoft Teams has been installed as machine based.

Step 6. RDP Properties (configure device redirection for Teams)

Ensure redirection has been configured on the WVD Host pool:

  • audiocapturemode:i:1 (enables audio capture from the local device and redirects audio applications in the remote session.)
  • audiomode:i:0 (plays audio on the local computer.)
  • camerastoredirect:s:* (redirects all cameras.)

You can navigate to your host pools using this link, to add these redirection properties: https://portal.azure.com/#blade/Microsoft_Azure_WVD/WvdManagerMenuBlade/hostpools

You can also use Group Policy to enforce redirection:

Step 7. Reboot WVD Host……

…………… …………. ……….. ……….. ……………….. ………. ………….. ……..

Step 8. Check the version for “WVD Media Optimised” status

If configured correctly and you have rebooted the host….. (see above) you should now see “WVD Media Optimised”

Screenshot showing “WVD Media Not Connected”

To check if you have configured correctly, click on your Profile icon, then About, and finally Version. This will then show the required information.

Step 9. Test WVD Teams redirection

As a quick test, I setup a quick join call and as you can see……….

WVD_TEAMSDEPLOY App

To speed up the process of preparing and deploying teams on Windows Virtual Desktop. I have written a tool that completes all the pre-requests, downloads the installers and installs all the required components. All you need to do is ensure you run the application as a admin and you remember to reboot once the install has completed.

https://github.com/RMITBLOG/WVD_TeamsDeploy

Automate using Custom Script Extension

Also see my other blog post that automates the full teams process using a Custom Script Extension. https://ryanmangansitblog.com/2020/08/07/automate-wvd-teams-deployment-including-webrtc/

7 thoughts on “Configuring Microsoft Teams for Windows Virtual Desktop (WVD)

Add yours

  1. What do you think about using redirection to lower the size of profiles? Another person recommends something like this in a file then redirect via GPO call to the file.

    <FrxProfileFolderRedirection ExcludeCommonFolders="”>

    AppData\Roaming\Microsoft\Teams\Service Worker
    AppData\Roaming\Microsoft\Teams\Cache
    AppData\Roaming\Microsoft\Teams\Logs
    AppData\Roaming\Microsoft\Teams\media-stack

    1. This is my opinion of course:

      Intro:

      By default, the FSLogix profile container will contain the entire windows profile for the user, a part from the (TMP) folder and the IE Cache folder.

      The concept of a profile stored in a virtual disk, is to facilitate the ability to detach the user profile data from the underlining OS. As users typically connect to a different session host on each new session, Would you want to keep the profile data containerised / centralised for that user ? In most cases, yes. This enables the flexibility of this data roaming with the user in the format of a mountable vDisk.

      Challenges and risks:

      Yes redirecting reduces the profile size, but for what reason ? an inadequate designed storage solution to house these disks? Moving the data to the local profile (local disk). What would be the impact….. ?Reduction of disk space on the OS local disk possibly performance issues ?

      Noted, the Local_ folder is deleted by the FSlogix service on log off. Meaning the data stored locally is temporary as long as you have configured the XML file correctly.

      Conclusion and summary:

      Redirection is useful for redirecting caches, log files and none essential profile data.

      Design and sizing of the local disk is important, as well as understanding what would be beneficial for redirection.

      When you look at the significate reduction in profile size by redirecting teams to a temporary local profile. its suggested that redirection should be applied as a smaller profile could offer performance and login experience improvements. This should be tested as there may be user experience changes due to the teams data being temporary.

  2. I Ryan,
    in your opinion, this configuration could be used with classic RDP as well?
    We have people at home connected to their pc in the office.
    With A/V redirection they could avoid using Teams by their local client but using the one at the office site.

    Thanks

  3. Hi,

    I have implemented MSTeams via RemoteApps and having issues when receiving calls.
    Voice / video media works fine for meetings and PC to PC calling is fine.

    But when a call is made via a PSTN line, the call is received in Teams remoteapp but when answered, there is no call media (as in no voice is heard).
    Is there any additional configuration that is required for voice call over PSTN?
    Many thanks in advance.

    RD

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Create a website or blog at WordPress.com

Up ↑

%d bloggers like this: