The end of Window 10 Support on 14 October 2025 has given many Organisations the impetus to pause and evaluate if desktop and laptop devices running a full-stack of Windows applications is indeed the way forward. For a (considerable) number of years Thin Clients have provided an alternate approach for savvy Organisations who have embraced either a Cloud First, or hosted application and data model of Information Technology delivery.
With a large number of hardware devices potentially being consigned to the scrap heap, we set out to identify options to allow for extending the life of these devices as a "fat" thin client - this evolved into a what's next evaluation of readily available thin client hardware platforms enabling our team to provide a full journey from using Windows 10, to re-purposing non-Windows 11 hardware, and finally replacement of NLFFP (No Longer Fit For Purpose - ie: Dead/Old) devices with an appropriate platform.
The below article comes from real efforts (and some vendor conversations!) our team (led by Dinesh Gaire) have undertaken in the past 6 months as we have explored, considered, rejected and finally selected a "journey" that meets our rigorous standards and delivers value to our clients (both existing and future!).
In a fragmented vendor marketplace identify a single, centrally managed operating system capable of running on both new thin client hardware and legacy PCs no longer eligible for Windows 11, while supporting advanced security, deployment, and virtual desktop features.
For bonus points, while the various hardware platforms were available, identify a best fit platform for our client base.
The following features were identified as the minimal set of must haves to provide coverage for existing deployments and work pipeline (ie: this is entirely focussed on what OUR clients need now and may not suit everybody!):
While not explicitly excluded from the evaluation and testing process, the vendor deployed O/S options were at a considerable disadvantage as they are all made available for their respective hardware platforms.
The list of considered and tested Operating Systems is:
Each Thin Client hardware platform was tested in the following manner:
Desktop PC hardware was tested in the following manner:
Once each hardware platform + Operating System pairing was "available" (not as simple a process as one might hope), the testing sequence for the required functionality was undertaken. A number of the tests required SIGNIFICANT interaction with the relevant support vendor support (and in some cases, development) teams and for this we are very grateful to those individuals who assisted - it also highlighted that getting to the point of deploying these solutions is NOT something that can be trivialised or attempted as a "tactical" point solution. These changes are very much strategic and require high levels of understanding and integration with existing systems!
The two tables below are the summarised results from the testing - outcomes have been simplified into yes/no/partial - if more detail is required, there are piles of notes on the floor of the test area! We've split these results into two tables, as once we eliminated a hardware / Operating System pairing as non-functional, remaining results for the combination were self-evident.
Manufacture | Model | Firmware / Operating System | ||||||
Vendor Supplied | Vendor Latest | Win10IOT | ChromeOSFlex | FydeOS | Stratodesk No-Touch | iGel 11 | ||
Dell (Wyse) | 3040 | Yes | No | No | Yes | Yes | Yes | Yes |
Dell | Optiplex 3000 | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
HP | t550 | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
Lenovo | M75n | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
Centerm | F650 | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
PC Hardware | i5 5th Gen | Yes | No | Partial | Yes | Yes | Yes | Yes |
In simple terms, basic Operating System installations functioned across the majority of hardware platforms (using USB drives and manufacturer provided images) - the obvious exceptions were known in advance and called out by the vendors.
Operating System | Version | Tested Features |
|||||||||
Central Admin | Zero-touch Deploy | SAML Auth | Kiosk Mode | Citrix Session | Azure VDI | AWS Workspaces (SSO) | Local Browser | Desktop Branding | |||
Dell ThinOS | 9.4 | Yes | Yes | Partial | Yes | Yes | Yes | No | No | No | |
Dell ThinOS | 10.1 | Yes | Yes | Partial | Yes | Yes | Yes | Partial | No | No | |
HP | ThinPro 8 | Yes | Yes | Yes | Yes | Yes | Yes | Partial | Yes | Partial | |
Lenovo | LeTOS 2 | Yes | Partial | Partial | Yes | Yes | Yes | Partial | Yes | Partial | |
Centerm | TOS | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Partial | |
ChromeOSFlex | 133 | Yes | Yes | Yes | Yes* | Yes* | Yes* | Yes* | Yes | No | |
FydeOS | v19 | Yes | Yes | Yes | Yes* | Yes* | Yes* | Yes* | Yes | Yes | |
Win10IOT | LTSC 2021 | Yes | Partial | Partial | No | Yes | Yes | Yes | Yes | Yes | |
Stratodesk | No Touch | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | |
iGel | 11 | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
* "Kiosk" mode on ChromeOSFlex and FydeOS provides for the auto-launching of a single pre-defined application. The manner in which the auto-launch occurs.
From the summary table, two OS options gained all "Yes" responses - Stratodesk and iGel. However, there was a clear gap between these two solutions with respect to vendor engagement and ease of deployment - with the evaluation team giving a clear "best match" to iGel - the full results summarised in the following points:
For our existing "thin client" clients the approach is quite simple:
For once there was an obvious clear path that fits clients of all sizes that have implemented a Cloud First approach that is not reliant on a local Windows Operating System.