Teams Optimization and Thin Client/Zero Client requirements

[HPU-ADM]

We've been struggling to get great/quality user experience with Teams on Horizon for some time now.  This Tech Zone document gives me a good direction in what the minimum requirements i should be shooting for with thin and zero clients.

Microsoft Teams Optimization with VMware Horizon | VMware

But I would like some clarification:

1. Media Optimization is only for Windows Clients. The Horizon Linux Client is installed on most thin clients and zero clients.  It's not explicitly pointed out, so am I correct to say that thin clients/zero client based on Linux OS, running the Horizon Linux Client will not have Media Optimization?

2. The minimum requirement on a client system (thin client or zero client)

a. Windows 10.  

Does that include windows 10 IoT Enterprise? Again, it's not specifically state, but it also doesn't state ALL windows 10.

b. 2.4 GHz dual core. 

Most thin/zero clients are dual or quad core but usually have a base 1.0-1.5 Ghz, and can burst to 2.4 Ghz and higher.  Burst means "for a short period of time".  So does that mean Teams will only have a good user experience for "a short period of time".  Would it be better to get a thin client/zero client with a base speed of 2.4Ghz?

[DCasota]

Hi,

Start with the MS Teams features of Horizon Client 2006, see https://docs.vmware.com/en/VMware-Horizon-Client-for-Windows/2006/rn/horizon-client-windows-2006-rel....

The thin client compatibility list filtered by Horizon Client release is a good starting point, too.

https://www.vmware.com/resources/compatibility/search.php?deviceCategory=vdm&details=1&releases_filt...

Afterwards it is good to double check the device firmware release notes (Linux /Windows IoT/.) if there are any footnotes about MS Teams features.

Hope this helps. Daniel

[FredericLOUKA]

Hello,

I'm working on vdi project and try as you, to have a clear answer about the teams optimization support with Horizon + Thinclient running under ThinOS.

We had an answer telling us that the optimization did not work with ThinOS and that we should go with Thinclient running under Windows iOT. Did you experience this in a real situation ?
Thank you for your answer,

Fred

[DCasota]

Hi,

Imho a managed vdi chain including optimizations for teams application(s) isn't legacy at all. There are feature differences between teams application types, between teams desktop full client, vdi optimized client (if any) and web client, and there are architecture, os and hardware prerequisites.

I don't think the value lies in an os consideration. 

The following practitioner vdi prod environment for 200++ concurrent users worked in the past.
VMware Horizon onprem + x86_64 W10 1909 + Skype for Business + Igel UD3 with Linux os + wired Jabra headset + usb-attached Logitech webcam + 1920x1080 dual monitor support

Working from home increased within a year, and all users got preprovisioned laptops. That said, the demand for solving wlan bandwidth issues, usb(-c) connectivity issues, (multi-)monitor issues, login issues and MS patches issues increased rapidly.
To move forward with thinclients might be important though because the "old" working set provides a great user experience - much more than the first instant set of laptop&bring-your-own-homematerial.
Collaboration with MS teams+M365 internally and enabling collaboration using any teams application type for some users was/is an additional use case to solve.

That said, from a vdi project perspective I suggest the following recipe.

1) Know your Horizon platform
Perpetual+subscription based Horizon editions:
https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/products/horizon/vmware-horizon-pe...
https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/products/horizon/vmw-horizon-subsc...
See entries especially for optimized video and audio experience for Microsoft Teams
Horizon configuration helpers: https://techzone.vmware.com/reference-architecture

2) Increase client IT engineering
VMware Workspace ONE managed laptops meet user expectations. Users don't care about software plugin internals at all, it just has to run flawlessly. That's it. That's the message.

So, from a client IT engineering perspective better integrate&test teams full client applications as soon as possible and care intensively about installation (and workflow!) issues. Teams client applications are Microsoft Teams client, Zoom VDI plugin, Cisco Webex Teams client, etc. Choosing Thinclient Igel Linux OS again is a safe match because the vendor maintains various client applications as well. Newer firmware usually means newer client applications versions. In addition, there IS a way to make use of a teams client application on Igel's Linux. See https://kb.igel.com/igelos-11.04/en/custom-partition-tutorial-32868832.html.

A learning curve often reflects individual progress of your own. Today I wouldn't reconsider reevaluating hardware/software with respect to the whole chain with VMware Horizon client version + protocol (PCoIP, Blast Extreme, RDP) + Real-Time Audio-Video (RTAV) + teams client application type/version + webcams&microphones model + additional optional/mandatory hardware/software features.

However, keep yourself up-to-date with Horizon client related information helps.
Compatibility guide for supported thinclient devices with RTAV on the Horizon platform
Release Notes entries specific to Horizon Client for Windows installation
Release Notes entries specific to Horizon Client for Linux installation
Typically have a look to release information / new features / platform restrictions / system requirements for Real-Time Audio-Video, and for using webcams and microphones.

Hope this helps. Daniel