Thin Client Considerations for Supporting Virtual Desktops in Azure

Written by Tony Cai
September 27, 2021

Consider specs such as wireless and connectivity options in choosing a thin client.

Tony Cai

When adopting or adjusting virtual desktop solutions and services, many managed service providers seek advice on what brands, and types of clients, to invest in to accompany deployments. And given the evolution of desktop-as-a-service (DaaS) and the recent general availability of Windows 365, a new set of criteria have emerged when it comes to selecting the right hardware to efficiently operate virtual desktop environments.

To answer these questions, below is a breakdown of how zero and thin clients stack up when it comes to supporting virtual desktops in Microsoft Azure, along with the pros and cons of each and a few need-to-know considerations.

Laying the Foundation: Azure Virtual Desktop Considerations

When it comes to virtual desktop offerings, Microsoft has established itself as an industry leader committed to bringing out new market innovations. With that in mind, there are a few current key considerations below to be aware of when evaluating thin clients to run on Azure Virtual Desktop (AVD) and Windows 365, which also runs on top of the AVD service.

If using AVD and/or Windows 365, you’ll need a Windows 10 IoT thin client or a Linux thin client that supports AVD.

Both AVD and Windows 365 use a technology called Reverse Connect, which does not expose your typical Remote Desktop Protocol (RDP) port (3389) to the internet.

Although both AVD and Windows 365 use RDP; a traditional RDS-only compatible thin client will not work.

Additionally, there are currently no known zero clients that support AVD or Windows 365.

But just like a PC, there are many options to consider when it comes to thin client specs and buyers still must consider a variety of factors per client, such as the number of USB ports, how many monitors it supports, wireless and connectivity options, if the device is Windows- or Linux-based and the form factor.

Zero Clients

Zero clients have gained traction in recent years because of their security benefits, ease of management and cost. They have a specific function: to boot right into the VMWare Horizon, Citrix or remote desktop session (RDS) session. This is usually accomplished in seconds.

As previously mentioned in the technical bullets above, there are currently no known zero clients that support Azure Virtual Desktop or Windows 365. So, for MSP partners, when investing in zero clients to support virtual desktop offerings across cloud vendors, keep in mind that most zero clients only support certain virtual desktop infrastructure (VDI) protocols.

Pros of a Zero Client

Optimized. Hardware is optimized for specific connection protocol (mostly for Citrix and VMware Horizon, but some support remote desktop services (RDS), but make sure the one you pick supports your desired connection type.
Setup / upkeep is a breeze. There are just a few settings and you’ll be connected to your VDI.
Security. Firmware is embedded and does not have to be updated frequently. In general, zero clients are less prone to viruses.
Fast and simple. Since there isn’t an operating system, it boots up within seconds from being powered on.
Centralized management. Many manufacturers have developed software to help manage an organization’s fleet of zero clients.
Low cost. A zero client is as simple as it gets, so the costs are bare bones as well.

Cons of a Zero Client

Flexibility. Since a zero client typically doesn’t support all protocols, you’ll have to pick which one to go with and you’re likely stuck using that specific protocol for the life of the unit. Some manufacturers allow you to switch protocols, but will require a firmware flash to do so.
Lack of OS. Since there’s no operating system, you can only manage zero clients through the manufacturer software, not with an RMM solution.

No AVD/Windows 365 Support. At this time, there is no zero-client solution for AVD and/or Windows 365