Has Dell Created the Perfect Thin Client?

Many have tried to create a marketable thin client, let alone a perfect one. So far, all have failed. But the Dell-Wyse Cloud Connect, announced this week, might be close.

By Rob Enderle
Fri, January 31, 2014

CIO — The thin clients' lack of success is hard to understand if you look at the market from the outside. Who wouldn't want a PC experience that worked like an appliance? After all, some of us do look back at certain aspects of the old terminal with fondness. You had to wait for the CRT to warm up, sure, but you didn't worry about viruses or software updates, and the whole thing was as reliable at that time as a TV.

There have been many efforts to replicate this experience. Oracle and Sun both tried to take out Microsoft — and failed. Clear Cube attempted to embrace Microsoft — and faired only slightly better. Wyse ended up with a far smaller market than it should have had, given that the potential demand for an appliance-like, virtual desktop experience was near universal.

Dell Logo

Dell, through its Wyse acquisition, has just launched Cloud Connect. Clouds have parted, and angels are singing. OK, maybe not, but this is by far the best attempt at a thin client ever made.

First Thin Clients Performed Poorly, Cost Too Much

When thin clients were created in the 1990s, they had two primary configurations: A shared server or a dedicated, PC-like back end. The server-based configuration could, mechanically speaking, scale easily, but performance degraded sharply. Users didn't like it. The PC back-end approach addressed the performance problem, but it cost more than just a PC. In the end, you had rack after rack of PCs being accessed remotely.

[ Analysis: Why Powerful Thin Clients May Be Alternative to PCs ]
[ News: $99 Android PC Maker Hopes to Set Off Industry Change]

The first thin client makers, Oracle and Sun, didn't understand PCs. Oracle was a mainframe company; Sun sold servers and workstations. PCs were toys to both companies and they couldn't embrace what they didn't understand. The PC back-end folks were PC guys, but they didn't understand servers and the need for shared resources. The solution, then, blended of server and PC technology. This required a very specialized server that just didn't exist — and the skills needed to create it didn't exist, either.

Continue Reading

Our Commenting Policies