Blog

What is a thin client? definition, how it works, and types

Learn what a thin client is, how it works with Windows 365 and Azure Virtual Desktop, and which type fits your deployment.

Table of Contents

What a thin client actually is
Thin client vs. thick client vs. zero client
How thin clients work
Types of thin clients for cloud desktop deployments
Thin clients in Windows 365 and Azure Virtual Desktop environments
When thin clients are the right choice, and when they aren't
How Nerdio Manager fits into thin client deployments
Frequently asked questions about thin clients

You're planning an endpoint refresh for your Windows 365, Microsoft Intune, and Azure Virtual Desktop deployment, and someone on the team asks whether you need full PCs at every desk.

The answer depends on understanding what a thin client is, how the architecture works, and which type fits your environment.

This guide is for IT leaders evaluating endpoint options for Windows 365, Microsoft Intune, and Azure Virtual Desktop deployments. If you're also comparing cloud desktop models, Windows 365 vs. AVD provides useful context.

What a thin client actually is

A thin client is a computing endpoint that relies on a central server for processing, storage, and application execution rather than handling most of those workloads locally. In Windows Cloud, which encompasses both Windows 365 and Azure Virtual Desktop, the device captures your keyboard and mouse input, sends it to the server, and displays the rendered output streamed back over a display protocol.

The hardware reflects this division of labor. A typical thin client uses a low-power processor, RAM specs, a small flash drive for the operating system, and no local hard disk for user data. Many are compact, fanless units that mount behind a monitor. Power draw varies by device and setup, and thin clients generally use less power than a standard PC-and-monitor setup.

A client is "thin" because applications, data, and the desktop OS primarily run on the server side. The endpoint primarily acts as an input/output device. The amount of work the endpoint handles depends on the protocol and deployment model connecting it to the server.

Thin client vs. thick client vs. zero client

Endpoints fall on a spectrum from zero clients, with no local OS and firmware only, through thin clients, with a lightweight OS and minimal hardware, to thick clients, which are full PCs with local storage and applications. Each maps to a different operational model.

Dimension	Zero client	Thin client	Thick client (PC)
Local OS	Firmware only	Lightweight embedded OS	Full Windows or macOS
Local storage	None	Small flash for OS only	Full hard drive or SSD
Application execution	Minimal local execution focused on protocol handling	Limited local execution depending on model and optimization	Full local capability
Protocol support	Single protocol, single platform	Multiple protocols	Any VDI client software
Security attack surface	Smallest	Reduced	Largest
Management model	Minimal; firmware updates only	Centralized; policies pushed to fleet	Per-device OS and app patching
Network dependency	Highly dependent on network connectivity	Highly dependent on network connectivity	Can operate offline
Hardware cost per device	Lowest	Lower than PC	Highest

The table highlights a few key tradeoffs worth calling out. Zero clients minimize cost and attack surface, but their protocol lock-in means switching VDI platforms may require replacing the hardware. Thick clients deliver full local compute and offline capability, at the cost of the largest attack surface and per-device patching overhead.

Thin clients sit in the middle, supporting multiple protocols while keeping user data off the device. Within the thin client category itself, several form factors and architectures serve different deployment needs.

How thin clients work

Thin clients connect to server-hosted desktops through remote display protocols. These protocols carry two simultaneous streams. One sends user input, keyboard and mouse, from the client to the server. The other returns encoded screen updates from the server back to the client. Remote protocols include RDP (Microsoft's protocol for Remote Desktop Services and Azure Virtual Desktop), HDX (Citrix), and PCoIP (Teradici/VMware).

Thin clients are commonly used as endpoints in remote desktop and virtual desktop environments. Common architectures include the following:

In a shared terminal service model, multiple thin clients connect to a shared server OS. Each user gets an isolated session on the same server instance. This is the traditional Remote Desktop Services model.
In desktop virtualization (VDI), users connect over the network to virtual desktop environments on centralized server hardware. VDI stands for Virtual Desktop Infrastructure. The operating system and applications run in the data center or cloud. Windows 365 and Azure Virtual Desktop are distinct Microsoft desktop products within Windows Cloud and are a common destination for organizations moving new deployments or migrations to the cloud. Readers comparing those delivery models can also review what is VDI for background.
In a browser-based model, applications run in a web browser on the thin client. The device handles some local rendering but retrieves software and data from the network. This model is common for SaaS-heavy workflows.

GPU offload can improve remote display performance. When H.264 encoding is offloaded to a local GPU via NVENC, achievable frame rates can increase for media-heavy workloads. Teams optimization runs locally on supported endpoint devices and clients. Audio and video processing stay off the server. The amount of local capability on the endpoint determines where it falls on the thin vs thick client spectrum.

Types of thin clients for cloud desktop deployments

Thin clients now span categories that cover the range of form factors and architectures available for Windows 365 and Azure Virtual Desktop environments.

Desktop as a Service (DaaS) is the cloud delivery model for desktops. At the broader market-category level, both Windows 365 and Azure Virtual Desktop can appear in DaaS discussions. In Microsoft's product positioning, Windows 365 is the DaaS Cloud PC offering, while Azure Virtual Desktop is a desktop and app virtualization service on Azure.

Hardware thin clients (x86 desktop)

Purpose-built devices running a lightweight OS like Dell ThinOS, HP ThinPro, 10ZiG OS, or Windows IoT. Typical specs can include an Intel Celeron or Pentium processor, 8 to 16 GB DDR4, 32 to 256 GB flash storage, and dual to quad display outputs. Vendors include Dell, HP, Lenovo, and 10ZiG. These devices are designed to be stateless, centrally managed, and long-lived, with some deployments citing replacement cycles of seven years.

Software-based thin clients (repurposed PCs)

Software that converts existing x86 hardware into a managed thin client endpoint by replacing the local OS. IGEL OS, NComputing LEAF OS, and 10ZiG RepurpOS all turn aging PCs and laptops into locked-down cloud desktop endpoints. No new hardware purchase is required. IGEL OS works with Azure Virtual Desktop. PC lifespan studies indicate existing hardware can run two to three additional years with IGEL OS compared to running Windows.

Software-based thin clients are particularly relevant for organizations facing Windows 10 end of life hardware refresh decisions. Nerdio partners with IGEL, 10ZiG, and NComputing to pair repurposed endpoints with cloud desktop management.

Mobile and laptop thin clients

These are laptops built specifically to function as thin clients. They run a lightweight thin client OS, are designed primarily for accessing VDI and DaaS environments, and can be managed centrally alongside the rest of an organization's thin client fleet. HP offers mobile clients, and 10ZiG offers TAA-compliant mobile zero client options for government procurement. These serve field workers, healthcare staff moving between wards, and hybrid employees who need a managed, secure endpoint at home and in the office.

All-in-one (AIO) thin clients

Thin client hardware integrated with a monitor into a single unit. 10ZiG AIO, for example, combines a thin client, monitor, webcam, and microphone in one device. Industrial variants from Siemens include touchscreens rated for factory and warehouse environments at temperatures up to 122°F.

ARM-based and Raspberry Pi thin clients

Thin clients built on ARM architecture rather than x86. Ncomputing's RX-series devices, built on Raspberry Pi platforms, support Azure Virtual Desktop, Windows 365, and RDS. The trade-off is a narrower OS ecosystem (IGEL OS is x86-only) and a lower performance ceiling. That limits suitability for multimedia-heavy or multi-monitor enterprise use.

Windows 365 Link

Microsoft's own entry into thin client hardware is Windows 365 Link. It is a compact, fanless device, designed to connect to Windows 365 Cloud PC. It includes security features such as passwordless authentication and secure boot. It is positioned as a purpose-built device for Windows 365 Cloud PC connections.

The OS running on a thin client matters as much as the hardware. Linux-based devices (IGEL OS, HP ThinPro, 10ZiG OS, NComputing LEAF OS) are often viewed as offering a smaller attack surface than Windows-based endpoints, but Windows IoT Enterprise LTSC offers broader compatibility and a familiar management model.

OS choice can significantly affect how IT administrators manage virtual desktops, so many teams choose the OS based on their existing management tooling and security requirements rather than hardware vendor alone.

Thin clients in Windows 365 and Azure Virtual Desktop environments

Microsoft's Azure Virtual Desktop documentation maintains an official list of approved thin client partners, including 10ZiG, Dell, HP, IGEL, NComputing, Stratodesk, and Unicon. When a connection issue cannot be reproduced using Windows App, Microsoft escalates to the thin client vendor. In Azure Virtual Desktop environments, Microsoft's approved thin client partner list shapes vendor choice, even though Azure Virtual Desktop can be accessed from a range of device types.

Both Windows 365 and Azure Virtual Desktop support thin client endpoints, but the management architecture differs:

Windows 365 is a flat-rate SaaS service that streams a personalized Windows desktop from the Microsoft Cloud. Microsoft manages the underlying infrastructure for Windows 365, including hosting and service provisioning, while customers manage their Cloud PCs through Intune and the Microsoft 365 admin center. Management runs through Intune.
Azure Virtual Desktop is a desktop and app virtualization offering on Azure, essentially Azure VMs running an agent that brokers user connections. Your team is responsible for managing compute, networking, storage, and scaling in your own Azure subscription. Thin clients connect to session hosts through RDP, and management primarily runs through the Azure Portal and PowerShell, with some endpoint and policy workflows extending into Microsoft Intune.

Many enterprises run both platforms. They use Windows 365 for standardized knowledge workers and Azure Virtual Desktop for specialized workloads that need custom host pool configurations.

In both cases, thin client endpoint management operates on a separate plane from cloud desktop management. Vendor-specific tools like IGEL UMS (scaling to 100,000+ endpoints) or 10ZiG Manager handle device configuration, firmware updates, and fleet policies. Windows 365 relies primarily on Intune as its management surface, while Azure Virtual Desktop management remains centered in Azure tools, with some thin client vendors also providing Intune-related compliance or management integrations.

When thin clients are the right choice, and when they aren't

Thin clients fit specific deployment patterns well and others poorly.

Thin clients excel in these scenarios:

Task workers, call center agents, and shift-based workforces benefit from standardized workflows with no local compute requirements. Stateless design means each session starts from a clean baseline.
Healthcare and regulated environments can benefit from data centralization, which can reduce breach exposure. The Azure Virtual Desktop framework provides guidance on security, data protection, compliance, and Azure landing zone design.
Large fleets can reduce management overhead. On read-only thin client OSes such as IGEL OS, administrators can replace the OS image centrally instead of applying traditional per-device patches. A 2024 Dell ESG study found a 62% reduction in IT administrator time for the Dell thin client deployments it analyzed.
Shared workstations, including nursing stations, manufacturing floors, retail back-office environments, and other devices used across shifts, align well with thin client deployments.

Traditional PCs are a better fit in these scenarios:

Power users, developers, and creative professionals who need local GPU, high RAM, or latency-sensitive local compute.
Offline work requirements. Cloud desktops require persistent network connectivity.
Complex peripheral requirements. PCs offer device redirection, including pen, touch, camera, and smart card redirection.
Small deployments where infrastructure investment is disproportionate. Licensing costs can exceed hardware savings at small scale.

Repurposed PCs offer a budget-conscious migration path. Converting existing hardware with IGEL OS or NComputing LEAF OS removes the need for new hardware CapEx and delivers many of the management and security benefits of thin clients. Repurposing PCs as thin clients with IGEL OS or NComputing LEAF OS can extend the life of existing hardware and provide centralized management.

If you're refreshing endpoints for Windows 365 or Azure Virtual Desktop, the right choice depends on how much local compute, offline access, peripheral support, and platform flexibility your users need.

How Nerdio Manager fits into thin client deployments

Endpoint choice and cloud desktop management need to fit together. For Windows 365 or Azure Virtual Desktop deployments, the practical choice is usually between full PCs, repurposed hardware, and purpose-built thin clients, and each option carries its own management model.

Nerdio's view is that endpoint management and cloud desktop management both matter in the same deployment. IGEL locks down the endpoint and enables device repurposing. 10ZiG provides fully managed thin client hardware. NComputing converts existing PCs into managed thin client endpoints. Nerdio Manager for Enterprise adds orchestration across Windows 365 provisioning, Azure Virtual Desktop host pools, and Microsoft Intune policies, while vendor-specific tools still handle endpoint configuration.

Partner integrations: IGEL, 10ZiG, and NComputing

The Nerdio and IGEL integration, announced at IGEL Now & Next 2026, connects Nerdio Manager directly to IGEL UMS. Scott Manchester, Nerdio's Chief Product & Technology Officer, described the goal:

"Nerdio Manager brings cloud intent and automation directly to the endpoint. Together with IGEL's secure OS, we're delivering a zero-touch, zero-trust model where endpoints are automatically enrolled, configured, and governed from the moment they're first used."

10ZiG and Nerdio position their products around Windows 365 and Azure Virtual Desktop deployments, with Nerdio highlighting Microsoft Intune policy management, application deployment, and Azure cost controls for these environments. 10ZiG positions RepurpOS on its product page as a PC repurposing solution for Windows 365 and Azure Virtual Desktop environments.

NComputing and Nerdio have been deployed together at enterprise scale. A large city in Oklahoma supported 3,000 employees who migrated to Azure Virtual Desktop using this combination: NComputing LEAF OS converted existing Dell and HP devices into Linux-based Azure Virtual Desktop endpoints, while Nerdio Manager handled the virtual desktop environment.

Windows 365 and Azure Virtual Desktop value, side by side

Nerdio Manager's value differs by platform, but the same console covers both.

For Windows 365 environments, Nerdio Manager is positioned around unified application management, Intune policy backup and restore, and Advisor recommendations rather than infrastructure cost reduction. Its unified application management centralizes application deployment and updates for Cloud PCs from a single console. It also extends Intune management with policy backup and restore, plus Advisor recommendations for Cloud PC right-sizing, alerts on underutilized licenses, and Microsoft Flex (formerly Frontline) conversion recommendations where usage patterns fit shared licensing.
For Azure Virtual Desktop environments, Nerdio Manager adds automation and cost controls on top of the native platform. TechTarget's Enterprise Strategy Group found that Nerdio Manager's patented auto-scaling can reduce Azure compute costs by up to 55% versus using Azure Virtual Desktop alone by stopping and deallocating VMs during off-peak hours.

Many enterprises run both platforms. Nerdio Manager is positioned as one management layer across both Windows 365 and Azure Virtual Desktop environments. It centralizes application management, policy control, automation, and optimization across the two Microsoft cloud desktop paths rather than treating endpoint choice as a separate management decision.

Teams evaluating the platform can get a demo to see how Nerdio Manager works across your Windows 365 and Azure Virtual Desktop environment, or try it free in their own Azure tenant.

Frequently asked questions about thin clients

What is a thin client used for?

A thin client is used to access virtual desktops, remote applications, and cloud-hosted computing environments without storing data or running applications locally. Common deployment scenarios include healthcare workstations requiring HIPAA-aligned data centralization, call centers with shift-based workers sharing devices, and financial services environments with strict data sovereignty requirements.

How does a thin client differ from a traditional PC?

A thin client offloads most application processing and primary data storage to a central server or cloud service, while a traditional PC runs applications and stores data locally. Thin clients often use lightweight embedded operating systems, typically keep primary data storage on the server or in the cloud rather than on the device, and are designed to use fewer local resources. PCs offer offline capability, broader peripheral support, and local compute for workloads like development or creative production that thin clients cannot handle.

What is the difference between a zero client and a thin client?

A zero client contains no operating system at all, running firmware only, optimized for a single connection broker and display protocol. A thin client runs a lightweight embedded OS (Linux-based or Windows IoT Enterprise) and supports multiple protocols and platforms. Zero clients are often described as offering a very small attack surface and can lock you into a single VDI platform or protocol ecosystem. Thin clients offer more flexibility at the cost of a slightly larger management footprint.

Can I convert my existing PC into a thin client?

Yes. IGEL OS, NComputing LEAF OS, and 10ZiG RepurpOS replace or overlay the existing OS on x86 hardware. This converts PCs and laptops into managed thin client endpoints. This approach eliminates new hardware CapEx and can extend hardware life by two to three years. IGEL OS integrates with Azure Virtual Desktop solutions. ARM-based devices are not compatible with IGEL OS; x86-64 architecture is required.

Do thin clients work with Azure Virtual Desktop and Windows 365?

Yes. Microsoft maintains an official list of approved thin client partners for Azure Virtual Desktop, including 10ZiG, Dell, HP, IGEL, NComputing, Stratodesk, and Unicon. Windows 365 supports thin client access through the web client and third-party clients from Dell, HP, and IGEL. Microsoft's own Windows 365 Link device is a purpose-built device for Windows 365 Cloud PC connections.

Resources

Learn more about Nerdio Manager