The Media Optimization for Microsoft teams leverages the (Web Real-Time Communication) WebRTC features and offloads the audio and video processing from the virtual desktop to the client machine.
I’ve summarized the steps below, which would help you to understand what is required from the VMware’s standpoint to configure Media Optimization for Microsoft teams.
The brief note from VMware TechZone article below explains how this is achieved using the Horizon Client for Windows 2006 and Horizon Agent 2006 version.
Therefore, for configuring media optimization for Microsoft teams, the Horizon client version should be minimum at Horizon Client for Wndows 2006 (compatible with Horizon 8/2006) or at Horizon Client for Windows 5.5 (compatible with Horizon 7.13)
High level steps to configure the Media Optimization for Microsoft teams
- Horizon platform should be running on Horizon version 7.13 or Horizon 8 (2006 – as per the new versioning standards)
- Download the Horizon Client for Windows 2006 or Horizon Client for Windows 5.5 and during the installation, select custom installation and scroll down to select “Media Optimization for Microsoft teams”
- After the installation, reboot the Windows Client
- The code in the Horizon Agent is also installed by default, but it is controlled with a GPO, which is not enabled by default. As stated in the email below, the media optimization for Microsoft teams is not supported in Horizon agent 7.12 or earlier. So, the Horizon agent version should be minimum at 7.13 or Horizon Agent 2006
- Download the Horizon GPO bundle and use the ADM template files to enable the relevant GPO.
- The GPO can be enabled using the Group Policy Editor by navigating to Computer Configuration > Administrative Templates > VMware View Agent Configuration > VMware HTML5 Features > VMware WebRTC Redirection Features > Enable Media Optimization for Microsoft Teams. After setting this policy, you must log off from the Horizon desktop for the GPO policy to take effect.
- Besides, the below GPOs under the VMware WebRTC Redirection Features can be configured based on the requirement.
Keys points from the Microsoft Article Microsoft Teams for Virtual Desktop Infrastructure
- You can deploy the Teams desktop app for VDI using a per-machine installation or per-user installation using the MSI package. Deciding on which approach to use depends on whether you use a persistent or non-persistent setup and the associated functionality needs of your organization
- In a dedicated persistent setup, users’ local operating system changes are retained after users log off. For persistent setup, Teams supports both per-user and per-machine installation.
- In a non-persistent setup, users’ local operating system changes are not retained after users log off. Such setups are commonly shared multi-user sessions. VM configuration varies based on the number of users and available physical box resources.
- With per-machine installation, automatic updates is disabled. This means that to update the Teams app, you must uninstall the current version to update to a newer version. With per-user installation, automatic updates is enabled. For most VDI deployments, Microsoft recommends to deploy Teams using per-machine installation.
- To update to the latest Teams version, start with the uninstall procedure followed by latest Teams version deployment.
- For Teams AV optimization in VDI environments to work properly, the thin client endpoint must have access to the internet. If internet access isn’t available at the thin client endpoint, optimization startup won’t be successful. This means that the user is in a non-optimized media state.
High level steps to install Teams on VDI
- Download the Teams MSI package that matches your VDI VM operating system using one of the following links:
- The minimum version of the Teams desktop app that’s required is version 1.3.00.4461. (PSTN hold isn’t supported in earlier versions.)
- Install the MSI to the VDI VM by running one of the following commands:
- Per-user installation (default)
msiexec /i <path_to_msi> /l*v <install_logfile_name> ALLUSERS=1
This process is the default installation, which installs Teams to the %AppData% user folder. At this point, the golden image setup is complete. Teams won't work properly with per-user installation on a non-persistent setup.
- Per-machine installation
msiexec /i <path_to_msi> /l*v <install_logfile_name> ALLUSER=1 ALLUSERS=1
This process installs Teams to the Program Files (x86) folder on a 64-bit operating system and to the Program Files folder on a 32-bit operating system. At this point, the golden image setup is complete. Installing Teams per-machine is required for non-persistent setups.
IMP NOTE – For beta testing, VMware built support for Microsoft Teams into the Horizon Client for Windows versions 5.3, 5.4, 5.4.1, 5.4.2, and 5.4.3. If you enable the optimization GPO in the virtual desktop, these clients, although not officially supported, will begin implementing offload. The bugs we found in these clients during beta testing are fixed in Horizon Client for Windows version 2006 or later, which is officially supported and which VMware recommends using.
Procedure to check if Microsoft teams is running in optimized mode
A user can check if Microsoft Teams is running in optimized mode, fallback mode, or natively (no optimization) in the virtual desktop. In the top-right corner of the Microsoft Teams interface, click the user icon and navigate to About > Version to see a banner under the user icon describing the Microsoft Teams version and pairing modes:
· Optimized – If the banner shows VMware Media Optimized, the Enable Media Optimization for Microsoft Teams GPO is enabled, Microsoft Teams is running in the virtual desktop, and audio and video have been offloaded to the client machine.
· Fallback – If the banner shows VMware Media Not Connected, then Microsoft Teams is running in fallback mode. In this mode, the Enable Media Optimization for Microsoft Teams GPO is enabled, and Microsoft Teams has tried to start in optimized mode, but the version of Horizon Client being used does not support Microsoft Teams optimization. Audio and video from Microsoft Teams is not offloaded to the client machine. Fallback mode has the same limitations as optimized mode. When you make a call in fallback mode, you see a warning message on the call:
Your device doesn’t support connection via VMware. Audio and video quality may be reduced
· No optimization – If the banner does not show VMware text in the message, the Enable Media Optimization for Microsoft Teams GPO is not enabled. Audio and video from Microsoft Teams is not offloaded to the client machine.
The VMware TechZone article Microsoft Teams Optimization with VMware Horizon covers the detailed procedure to configure Media Optimization for Microsoft teams and Microsoft article Microsoft Teams on VDI covers important considerations and procedures from Microsoft’s standpoint