Return of the Thin Client

Running applications across a network to terminals from a dedicated computer is an old idea. Ever since the mainframe and the PC began to share the IT environment, businesses have wrestled with different degrees of centralization and decentralization of their computing resources. But with Terminal Server this old idea has a new extension on life.

In simplest terms, Microsoft's Windows Terminal Server lets users run Windows-based applications on a remote computer. One of the main benefits is the ability of IT managers to roll out applications quickly and then maintain them from a centralized computer. So instead of having to install (and update) a Windows application at each desktop computer in the organization, an IT manager can instead deploy the app from the server and updated there as required.

Also, users can rest assured that they are running the most up-to-date version of their application. And support staff has less maintenance issues to worry about. Another benefit of Terminal Server: a reduction in computing power needed at the individual client machine. This directly translates into reduced equipment cost, since nearly any sub-$700 machine will do. It also delivers increased data security; since only the central server handles processing and data storage, there's only one machine to secure.

There are a few challenges to using Terminal Server. Chief among them: keeping up with the demands on the network and the server hardware, while continuing to capitalize on the scalability that the Terminal Server offers. Information security becomes a concern again, with data and applications being stored and run centrally. Also, the cost of licensing Terminal Services can be high, so a system builder should weigh their customers' needs carefully before urging the decision-maker to pursue a centralized model.

id
unit-1659132512259
type
Sponsored post

Ingredients: Hardware

Here are the hardware components you'll need for this Recipe:

Server: I recommend that you use a dedicated server for your Terminal Services; that way, the load is concentrated on your server when running applications for remote users. You'll want a totally separate machine to run your Terminal Services, apart from your other core business applications such as Web, e-mail or file/print servers. A machine designed for duty as a Terminal Services server should be configured for maximum up-time, with a lot of available CPU power and RAM, and a redundant high-speed network connection.

Here are some basic recommendations for your server:

These design parameters will give your customer everything they need to keep the Terminal Services machine up and running, even in the event of the most common types of hardware failures. The more client machines that depend on this server for their productivity, the more important this becomes.

Thin Client PCs: The nice thing about running Windows-based applications on a server via Terminal Services is that it's no longer necessary to run the typical Windows OS on the desktop. Without this resource hog, the client machines do not require much RAM. Also, since data storage and application processing are now handled by the server, it is no longer necessary to have permanent storage and a fast CPU chip in the client machines, either. This means the hardware resources required at the network client are dramatically reduced; hence the term "thin client."

For example, you can purchase thin client PC hardware from Hewlett-Packard for about $200 to $700 per system. These thin clients are configured for operating systems such as Windows XP Embedded, Windows CE and Linux.

Another well-known supplier of thin clients is Wyse. The company's hardware, for what it calls "scalable thin computing," covers a similar range of prices and capabilities. Ingredients: Software

Microsoft Terminal Server 2003: The software to run Microsoft Terminal Services is already included with the Windows Server 2003 OS software. If this component was not installed at the time the OS was originally set up, you can add it by following these four steps:

Licenses: Client Access Licenses (CALs) for Microsoft Windows Terminal Server 2003 come in two types: Device CALs and User CALs. Which type of license should the system builder recommend for their customer? To help you decide, here's my rule of thumb: If the customer's organization has more users than devices, then propose Device CALs. That scenario would exist if you have multiple shifts of employees in an office using the same computers, for instance, or maybe a factory floor with a handful of computers used by a group of workers (each with their own user ID). On the other hand, if your customer's organization has more devices than users, then go for User CALs.

System builders can get up-to-date pricing on CALs from their authorized Microsoft distributor. Also check with your distributor for information to help with preparing a quote for your customer.

Here's how to install both Device CALs and User CALs:

Technically speaking, the licenses for a Terminal Server are loaded onto what Microsoft calls a "License Server." In practical terms, it is generally OK to install the License Server service onto the same machine as the Terminal Services. But when the number of licenses installed becomes very large, you'll need a dedicated machine for the License Server.

Microsoft instructs users to install the License Server by performing the following four tasks:

Your License Server won't be ready until it is activated. You can activate it during the installation process, or you can go back and activate it later.

Here are the five steps for activating a License Server that's already been installed:

Make sure your Terminal Server can detect your License Server, especially if it's a separate machine on the network. Now you should be ready to go.

One nice feature included with Terminal Services 2003 is the ability to support licenses from Windows 2000 Terminal Server and Windows 2003 Terminal Server. This will help if you need to migrate a network from older software.

System builders can also offer consulting services to potential clients, delivering proposals outlining the benefits and requirements of deploying a centralized network with Microsoft Terminal Services. For customers that do not have appropriate dedicated IT staff, the system builder might also fill this void with personnel who can travel to the customer's site and log billable hours for periodic maintenance and administration tasks.

For More Help: Helpful Microsoft Resources

Here are some related links for additional reading, and some support resources from Microsoft in the event you have a problem:

DAVID GILBERT is the owner of Appalachian Computer Systems, a West Virginia system builder that specializes in multiprocessor SCSI RAID servers.