Use VMWare to display XP Desktops out to Thin Clients without even using a Windows Terminal Server!
As best I can tell, Tim Negris is the man who coined the term Thin Client when he was with Oracle. It originally described scaled down applications that ran in conjunction with a full version of an application that was loaded on a server.
When Windows OS versions that allowed multiple users came on the scene, one of the first hardware companies to start selling client hardware was Wyse with the introduction of their WinTerm in 1995. This made sense – Wyse was already a huge seller of “dumb” terminals for mainframes and providing a Windows Terminal was logical.
Question: We would like to put together a Thin Client system that will have a total of seven Thin Clients. While some of these clients will be standard Thin Client hardware, we would also like to use some of our PCs as clients as well. We also need to allow for some spare capacity for the future.
Can you please specify the hardware and software (ACP and Microsoft) requirements for a reliable system?
Answer: There are multiple ways to build this system. I will start by specifying the basic system (the minimum required) and then work up to a system with redundancy that will guarantee uninterrupted operation in almost every case. Each system will have the following four parts – the Thin Clients, the hosting Windows Terminal Server, the Microsoft software and the ACP software.
A Thin Client computer runs what looks like a full Windows NT 4.0 operating system on each Client installed in a factory. This is accomplished by having a powerful server running a version of Microsoft’s NT 4.0 designed for Thin Clients, NT Terminal Server 4.0. This version of Windows allows multiple users to log in and establish a full Windows session running on the server. Each user gets a dedicated share of memory, some slices of CPU time, and access to the server’s disks and applications.
Since its introduction in 1999 ThinManager has undergone a number of improvements. But the most significant changes have come with the latest releases.
Here is a look at the most important features added and enhanced since ThinManager 2.3.
Introduced in ThinManager 2.4
Here is the Elevator Pitch – the 15 second version of our product that you could lay out during an elevator ride:
ACP provides management tools and software for Thin Clients and Terminal Servers. Thin Clients allow you to run standard Windows applications like a mainframe, with multiple users running at the same time on a single server, dramatically reducing costs.
If the person is interested, I normally hear a number of follow-up questions. Here are some of the most common ones with my answers:
There are two methods for getting data into a Thin Client system – through the Server, or through the Clients.
Getting data through the Server
For small installations, where input/output devices are not very far from the Server, and there are not many devices to read, this can be a very good solution. It is certainly the most traditional, with I/O devices being connected to serial ports or special hardware installed in the Server. As all Thin Client software runs on the Server anyway, there is no problem with each client identifying its input or output devices with physical addresses on the Server. This is also very efficient, as data doesn’t have to travel through the Client, to the Server, and back to the Client. However, it is very limited – a Server can only handle so much I/O, and if devices are far removed there will be difficulties in moving data (especially serial data) over the distance.