I haven't worked with thin clients in more than a decade. The few recent deployments I've seen were in medical clinics, and my earlier experiences were mostly frustrating: connectivity problems, frozen sessions, unreliable peripheral support, confused users, and plenty of general support headaches. Most of those organizations eventually moved back to regular PCs.
Thin clients are being discussed for our production systems, possibly running through Citrix, and I'm concerned about the administrative and support burden. Are thin clients still widely used, and have the hardware, virtualization platforms, networking, and user experience improved enough to make them worthwhile today?
4 Answers
They can be a headache when modern collaboration and peripheral requirements are involved. Teams or video meetings, Google Meet, scanners, specialty USB devices, printers, smart-card readers, and multiple monitors can expose limitations in the virtual desktop stack. Some of those problems became much more noticeable once remote work and video conferencing became standard.
Before committing, run a serious pilot with the actual applications and accessories your production users need. Test reconnects, host failures, network interruptions, printing, audio and video, updates, and user recovery. Don’t evaluate only whether a basic office session launches successfully.
There are still good use cases, but thin clients are not automatically simpler. One older deployment discovered that IT was effectively maintaining two operating systems: the endpoint OS and the virtual desktop OS. Dedicated hardware also has its own lifecycle and update requirements, and licensing for the virtualization platform can erase the expected savings.
For ordinary office workers using a browser and cloud applications, managed laptops or small PCs may be more practical. Thin clients make the most sense when you specifically need a locked-down workstation, centralized data, quick swaps, shared terminals, or strict security and compliance controls.
The technology is better than it was years ago. Products such as locked-down Linux-based clients and centralized management tools make the endpoints easier to configure and replace, and Citrix, AVD, and RDS environments are more mature. They’re especially useful in dusty manufacturing areas, operator stations, training rooms, and places where users should not be able to modify the machine.
For many deployments, though, inexpensive small-form-factor business PCs are cheaper and faster than purpose-built thin-client hardware. The important distinction is whether the desktop and data live centrally; the endpoint does not necessarily need to be a dedicated thin client.
They’re still very common in hospitals, clinics, call centers, banks, government, and other controlled environments. The advantages are centralized management, locked-down endpoints, easy replacements, and roaming users being able to reconnect to the same desktop. If the backend Citrix or RDS environment is healthy, swapping a failed endpoint can be nearly trivial.
The tradeoff is that the network and virtualization platform become critical dependencies. A bad WAN link, authentication outage, storage problem, or overloaded host can affect everyone at once. They work best when the infrastructure is designed with redundancy and proper monitoring rather than treating the endpoint as the whole solution.
That’s my main concern: if the desktops are reached through a WAN tunnel, the network becomes the weakest link. I’d want redundant connectivity and a tested fallback plan before deploying them broadly.
That’s what we found too. We kept the centralized virtual desktops but replaced dedicated thin-client hardware with small business PCs because they cost less and handled peripherals better.