Updating hp thin clients
Even when the OS is stored on a read-only flash disk, you still need to apply the monthly security updates and virus scanner/firewall updates to ensure the client doesn't become a broadcast station for worms within your network.
In practice there are just too many examples of unmanaged XPe devices being the “source of all evil.” Remember Blaster and Sasser?
The problem is that it's not economic to neglect the management aspect of the remaining 10% (or whatever) of devices that are laptops or PCs.
You can't ignore patching them just because they're the minority.
This means that, many of the monthly security updates are also valid and important for Windows XP embedded clients.
Finally, the reality of XP Embedded management solutions that they're very similar to the management infrastructure for PCs and laptops.
Surely, traditional thin clients can be a very successful when the requirements are low, but when the latest and greatest is required, you have another option.
However, one single update already justifies the investment in a management infrastructure, as manual configuration of all your thin-clients is extremely expensive.And by the way, BYOL (Bring your own laptop) doesn't this fix this problem.BYOL is a cool concept, but the majority of organizations still require full management of the desktop/laptop for practical, legal, or security reasons. All the cool features, especially those which require client-side rendering, are first developed for Windows.You could argue that there are a far fewer security updates required for XP Embedded.
Unfortunately it's fairly common to use Internet Explorer to provide a web portal front-end to authenticate and access the SBC or VDI desktop.
They'll tell you from experience that a management infrastructure is required to deploy security fixes, client/application upgrades, root certificates, firmware updates, and configuration changes.