Export (0) Print
Expand All

Overview of the Terminal Server Deployment Process

Updated: March 28, 2003

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

Hosting applications from a central location with Terminal Server enables centralized management of those applications. You also gain added security because data is stored on the server, rather than on local computers. The following examples illustrate the kinds of business solutions that Terminal Server can provide.

Bandwidth-constrained locations   In areas where high bandwidth is not available or cost-effective, deploying applications on a terminal server can improve performance for remote users because large amounts of data are not being transmitted over the connection.

Applications in development or transition   You can simplify administration of crucial line-of-business applications that are in development or require frequent updating by deploying these applications on a terminal server. You can ensure that all users have access to the latest version by updating the application on the server rather than on individual client computers, reducing the total number of updates required.

Use of third-party platforms   You can reduce desktop hardware costs for users who have a primary line-of-business application that is available only on a desktop running an operating system other than a Microsoft® Windows® operating system, but who still require access to Windows-based applications. Users can connect to a terminal server to run the Windows-based applications.

Use of thin clients   Data-entry workers can access their primary application from a Windows-based terminal (or thin client) rather than a personal computer, reducing total cost of ownership. Using thin clients also minimizes work disruption for task workers. If a terminal stops running, you can replace it quickly, with minimal setup.

For more details about the solutions that Terminal Server provides, see "Identifying the Role of Terminal Server in Your Organization" later in this chapter.

Before you plan your deployment of Terminal Server, you need to design your domain infrastructure. After you complete the tasks outlined in this chapter, you can conduct a pilot test of your Terminal Server solution, adjust your design if necessary, and deploy the completed solution to the production environment. For more information about pilot testing, see Planning for Deployment in Planning. Testing, and Piloting Deployment Projects of this kit. For more information about implementing your Terminal Server solution, see "Terminal server role: Configuring a terminal server" in the Configure Your Server Wizard and "Checklists: Setting up Terminal Server" in Help and Support Center for the Microsoft® Windows® Server 2003 operating system.

Terminal Server is available with the Microsoft® Windows® Server 2003, Standard Edition; Windows® Server 2003, Enterprise Edition; and Windows® Server 2003, Datacenter Edition operating systems.

Community Additions

© 2016 Microsoft