Configure Microsoft Teams offloading in VMware Horizon

With VMware Horizon 8 or the new naming format, Horizon 2006 (YYMM) Microsoft Teams offloading / media optimization is supported. Media Optimization for Microsoft Teams redirects audio calls, video calls, and viewing desktop shares for a seamless experience between the client system and the remote session without negatively affecting the virtual infrastructure and overloading the network.

What is supported

The Media Optimization for Microsoft Teams offers the following features:

  • Accepting and making audio and video calls
  • Multiparty audio and video conferencing
  • Transfer, forward, mute, hold, and resume a call
  • PSTN calls via dial pad
  • Desktop screen sharing
  • Multi monitor screen sharing and screen picker for screen sharing
  • Volume control from the remote desktop
  • Active speaker identification


Media Optimization for Microsoft Teams has the following limitations:

To enable this feature you need  to configure the following settings:

  • Install Horizon 2006 client and enable media optimization.
  • Import the Horizon 2006 GPOs and enable the Group Policy setting for Microsoft Teams
  • Perform a machine-wide installation of Microsoft Teams on the golden image

In this example, I will configure a Windows 10 client with a custom Horizon 2006 client installation, import and configure the GPO settings for Microsoft Teams on the Domain Controller and install Microsoft Teams on the Windows 10 Golden Image.

Horizon client

Install a custom installation of the Horizon client.

  • Download the Horizon 2006 client, link
  • Install the client and select “Customize installation”

  • Scroll down and select “Media Optimization for Microsoft Teams”
  • After the installation reboot the Windows client

VMware Horizon Group Policies

 Download and configure the Microsoft Teams GPO.

  • Download the GPO bundle from the VMware  download site

  • Extract the .zip file
  • Copy all the files to the %systemroot%\PolicyDefinitions folder on your Active Directory
  • Create a GPO and configure the Teams offloading settings:
    • Computer Configuration
      • Policies
        • Administrative Templates
          • VMware View Agent Configuration
            • VMware HTML5 Features
              • VMware WebRTC Redirection Features

  • Enable the Media Optimization for Microsoft Teams setting



VDI – Golden Image

Install the Microsoft Teams client on a Windows 10 32 or 64 bits OS.

  • Download the 32 or 64 bits Teams client, here is a link to the 64-bits version, link
  • Perform a machine-wide installation because Teams won’t work properly with a per-user installation on a non-persistent setup.
msiexec /i <path_to_msi> /l*v <install_logfile_name> ALLUSER=1 ALLUSERS=1

More information on installing Microsoft Teams can be found here, link. More information on installing VMware Teams can be found here, link.

Check session mode

To check if the Teams session is running in optimized, failback, or natively (without optimization) mode in the VDI session go the Teams client. In the Teams client go the the user account and navigate to about and select version. As you can see in the picture below, the session is optimized (VMware Media Optimized) which means offloading works.


After configuring these settings Microsoft Teams offloading is configured. For Microsoft Teams offloading you need at least an advanced Horizon license. Microsoft Teams offloading is now available in the Horizon standard subscription license, see link.

VMware Unified Access Gateway (UAG) 3.4 RADIUS license change

The VMware Unified Access Gateway (UAG) acts as reverse proxy and tunnels sessions (PCoIP and Blast) to desktops and remote apps. Besides Horizon support, new features are added for AirWatch and Identity Manager. With version 3.4, the VMware Unified Access Gateway is offered in three editions based on the Horizon or Workspace ONE licenses.

  • Standard
  • Advanced
  • Enterprise

Per edition the following features are supported:

One of the new features is high availability support for the Unified Access Gateway. Without the use of load balancers a UAG high availability environment can be created. This makes the environment less complex and is available as enterprise feature.

Another feature is RADIUS support. RADIUS is not a new feature and is available for a very long time. RADIUS offers two-factor authentication and is always a requirement for production environments. When looking at the editions table you see that this is now an advanced feature. Before version 3.4 of the UAG, with VMware Access Point and VMware Security Server, RADIUS was supported in all the editions!

In my opinion RADIUS is not a advance feature and belongs to all the editions of Horizon. This was always the case!

I’ll have a lot of customers who are using Horizon Standard with RADIUS support for two-factor authentication. Now they are stuck with the UAG 3.3.1 appliance or must heavily invest ($$$$$) in the advanced (or higher) edition of Horizon.

I’ll hope VMware will  judge again and make RADIUS support available in all the editions of Horizon.

Update: March 13, 2019: VMware Unified Access Gateway 3.5 is released. In this version there is no license requirement anymore based on the edition. All the features have been made available for all the Workspace ONE or Horizon editions. This is great news! RADIUS support is available for all editions in version 3.5 of the UAG.  More information: link.