Citrix Virtual Apps and Desktops

Optimization for Microsoft Teams (New)

Microsoft has launched a new version of Microsoft Teams (Teams 2.x) for VDI environments. Citrix now supports optimization for this new version of Teams. This documentation primarily focuses on Citrix HDX Optimization with the new Teams and offers essential information for transitioning to Microsoft SlimCore Optimization.

Terminology and transition

Microsoft Teams transition

There are currently two transitions in the Microsoft Teams space:

  • Transition from Classic Teams to New Teams: This transition is for both native and VDI clients

  • Transition from Citrix HDX Optimization to Microsoft SlimCore Optimization: This transition is specific to VDI environments.

    • We introduce the terms VDI 1.0 and VDI 2.0 to differentiate between existing optimization with Citrix HDX and the new VDI solution from Microsoft.

    • Colloquially VDI 1.0 refers to Citrix HDX Optimization and VDI 2.0 refers to the new VDI solution for Teams (Microsoft SlimCore Optimization).

Timelines

Key distinctions

Citrix HDX Optimization Microsoft SlimCore Optimization
Optimization is a combined solution of Citrix and Microsoft and uses a Virtual Channel created by Citrix. Optimization solution is owned and managed by Microsoft and uses Virtual Channels created by Microsoft.
Media offloading is handled by HdxRtcEngine which resides in Citrix Workspace app. Media offloading is handled by Microsoft SlimCore media engine.
No additional components needed on the endpoint except installation of Citrix Workspace app. Additional component - Teams VDI Plugin needs to be deployed on the endpoint through various means. This plug-in manages the download and updates of SlimCore engine.
Available on endpoint platforms - Windows, MacOS, Linux, and ChromeOS. Available on endpoint platforms - Windows as of date.
New features are managed in conjunction between Citrix and Microsoft. New features are managed by Microsoft.Users have access to some new features unavailable with Citrix HDX Optimization.

Interoperability and roaming

Citrix HDX (WebRTC) optimization and Microsoft SlimCore optimization can exist in parallel however the new Teams client can be optimized with only one of the ways at a time.

  • New Teams loads WebRTC or SlimCore at runtime. At runtime, a decision is made in the following order – SlimCore > WebRTC > Standard audio/video redirection.

  • The selection process is not dynamic. For example: In case New Teams has started optimizing with SlimCore and then an issue happens, it falls back to standard audio/video redirection. A Teams app restart is needed to then go through the decision making process and optimize with WebRTC.

  • The same scenario applies in the roaming scenarios. For example: If a user connects from an endpoint with SlimCore optimization and roams to an endpoint either without the plug-in (or) a Mac /Linux endpoint, Teams operates standard audio/video redirection. A Teams app restart is necessary to fallback to WebRTC optimization.

  • Roaming scenarios between endpoints which are already SlimCore optimized is seamless.

Optimization for Microsoft Teams (New)