Thin Clients OS?
Thin Clients OS?
Look for guidance on utilizing your server's hardware for processing tasks. Consider how computing resources can be centralized while maintaining flexibility across different environments. Explore options that allow local peripherals and remote access without requiring dedicated machines at every site.
The server is operating on a specific operating system and software. You can connect via RDP, though each solution typically uses its own protocol for client interactions. This setup is likely intended for home use, as thin clients are generally impractical at the residential level due to the extensive configuration needed and minimal benefit compared to traditional systems.
I work with several CAD programs and other tools. The expense of constantly upgrading multiple machines is becoming unsustainable compared to using a single system across multiple locations. I have six separate machines, and I update my server periodically. My interest in thin clients stemmed from the need to boot a system and connect via RDP, which feels more suited for home use. However, it’s not typical for a home setup. I operate two systems in my shop, an office, and two remote machines at an offsite garage. I have access to all Windows versions, Server 03, and Server 08. The primary server is a dual e2660 with 96GB storage on spinning disks (~96TB). We discussed this on a different thread. If no one has any advice, I’d suggest looking elsewhere.
I focus on standard workstations instead of complex clients. It’s budget-friendly with less patience required and lower software expenses. For strong thin client performance, tools like VMware Horizon are ideal—though they demand new servers, extensive licensing, and significant setup. Investing in quality workstations per site is more cost-effective and reliable. Avoid outdated Windows server setups unless upgrades aren’t possible, and limit network access as much as feasible.
Thin client computing is either Citirix/RDS, or VDI. Not much in between. With one you are just stacking remote desktop sessions on a single OS, and the later you are running a virtual OS for each session (Horizons). Thin clients are fine for business apps or browser based apps. They return their costs via centralized application management. They do not save costs from a hardware perspective. That argument went out the window in 2004. Xeon E2660 is outdated junk. My near 10yr old quad-core i7 2600 has double the single thread performance. Some CAD apps work ok over RDS connections. Some don't. Depends on your pain threshold.
I often hear this, but it still works well in bench tests, outperforming the 7700k during all my program runs. It saves you about 87 USD, and it costs just 35 USD for the 2680v2 setup—though it's not the absolute top system, balancing cost and performance is challenging.