Microsoft has released a public preview of a new optimization architecture for Microsoft Teams in Citrix Virtual Desktop Infrastructure (VDI). Guided by extensive customer feedback, Microsoft re-architected Teams in Citrix VDI with a focus on modularity, decoupling, performance improvements, and streamlined support. It better aligns the experiences between physical and virtual desktops.
Key Optimizations
- Advanced Features: The new SlimCore Media engine replaces WebRTC, enabling faster feature updates and parity between native Teams and Citrix VDI Teams
- Performance Improvements: Reduced call drops, faster meeting joins, and higher success rates
- Auto-Updates: SlimCore auto-updates without prompts or reboots, ensuring compatibility and high quality
- Streamlined Support: With minimal dependency on Citrix stacks, IT admins can contact Microsoft directly for support, reducing downtime
Benefits
- Support for AVD/Citrix with Horizon View/Omnissa to follow (still under development)
- No longer requires constant updates to CWA/RDP
- Hardware acceleration for GPU-enabled devices is available
- New features including noise suppression, location-based routing, QoS, and more
Simplified Deployment
The new architecture uses a new client-side plugin (MsTeamsPlugin.dll) to handle virtual channels and media engine downloads, simplifying updates and maintenance. Compatible with the latest Citrix Workspace apps, it ensures seamless updates without requiring reboots or admin privileges.
Enhanced Media Handling
The SlimCore engine replaces the legacy WebRTC engine. This new engine optimizes real-time media, supporting high-fidelity audio, 1080p video, and up to 30fps for video and content. New features include advanced meeting capabilities like gallery view, custom backgrounds, and presenter mode, along with enhanced telephony and voice capabilities.
Logging
Teams logs can be collected by selecting Ctrl+Alt+Shift+1 while running Teams on a VM. This action produces a ZIP folder in the Downloads folder. Inside the PROD-WebLogs-*.zip file, look for the Core folder.
Pre-requisites
- UDP 3478-3481 Out 13.107.64.0/18, 52.112.0.0/14, 52.122.0.0/15
- TCP 443,80 Out *.lync.com, *.teams.microsoft.com, teams.microsoft.com, *.office.net, *.skype.com, 13.107.64.0/18, 52.112.0.0/14, 52.122.0.0/15, 52.238.119.141/32, 52.244.160.207/32, 2603:1027::/48, 2603:1037::/48, 2603:1047::/48, 2603:1057::/48, 2603:1063::/38, 2620:1ec:6::/48, 2620:1ec:40::/42
- Citrix Policy to allow virtual channel establishment (VDA reboot required)
- Windows App 1.3.252+ | RDP for Windows 1.2.5405+ | CWA 2402+
- Read/Write access to user specific data stored in "C:\users\<user>\AppData\Roaming\Microsoft\TeamsVDI\" (more of an issue for locked down thin clients – not much detail as of yet around Linux-based TC’s such as IGEL)
- For best performance, exact Slimcore engine version should match on endpoint and VDA/Host VM
Get Started Today
For more information and detailed deployment instructions, please visit the official Microsoft website:
https://learn.microsoft.com/en-us/microsoftteams/teams-for-vdi
This blog post was co-authored by Timothy Karl and Ryan Lee. Click the links to read more.