Microsoft Windows Server 2003 Deployment Kit [Electronic resources] : Planning Server Deployments نسخه متنی

Overview of the Terminal Server Deployment Process

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.

Process for Planning and Deploying Terminal Server

Figure 4.1 illustrates the high-level process for planning and deploying Terminal Server for hosting applications. Although the primary tasks remain the same for anyone planning to deploy Terminal Server, the steps differ depending on the solution you want to provide. Those differences are described in context throughout the chapter.

Figure 4.1: Planning and Deploying Terminal Server

For a job aid to assist you in recording your design decisions, see "Terminal Server Planning and Design Worksheet" (SDCTS_1.xls) on the Microsoft Windows Server 2003 Deployment Kit companion CD (or see "Terminal Server Planning and Design Worksheet" on the Web at SDCTS_2.xls) on the Windows Server 2003 Deployment Kit companion CD (or see "Group Policy Configuration Worksheet" on the Web at http://www.microsoft.com/reskit).

Basic Terminal Server Concepts

The Terminal Server component of Windows Server 2003, which was called Terminal Services in Application Server Mode in the Microsoft Windows 2000 operating system, can deliver the Windows desktop, in addition to Windows-based applications, from a centralized server to virtually any desktop computing device, including those that cannot run Windows.

Terminal Server uses the Remote Desktop Protocol (RDP) to communicate between client and server. After you deploy an application on a terminal server, clients can connect over a remote access connection, local area network (LAN), wide area network (WAN), or the Internet. The client computers can run Windows (including the Microsoft Windows CE operating system) or run on other operating systems such as the Apple Macintosh or even UNIX (using a third-party add-on). When a user accesses an application on a terminal server that is running Windows Server 2003, all of the work of the application takes place on the server and only the keyboard, mouse, and display information are transmitted over the network to the user desktop. Each user sees only their individual session, which is managed transparently by the server operating system and is independent of any other client session.

Windows Server 2003 Terminal Server offers the following new features and improvements:

For improved load-balancing performance, the new Session Directory feature automatically reconnects users to an existing session within a load-balanced server farm, rather than just being directed to the least loaded server when they reconnect.

For improved logon security, you can use a smart card to log on to a terminal server running Windows Server 2003 and run applications from client computers with a smart card subsystem (including computers running the Microsoft Windows XP operating system, Windows 2000, and the Windows CE operating system). This provides an additional level of physical security to your network environment.

For a better user experience, Terminal Services supports a wider variety of data redirection types (including file system, serial port, printer, audio, and time zone) and supports connections in up to 24-bit color.

For improved management, there is an expanded set of Group Policy settings for Terminal Server and a full Windows Management Instrumentation (WMI) provider allowing for scripted configuration of Terminal Server settings.

For improved license management, you can install Terminal Services Enterprise Licensing on either a domain controller or a member server. Terminal Services Licensing wizards have been improved to reduce the complexity of activating a terminal server and assigning it licenses. There is also a new security group that allows only specific terminal servers to request licenses from a license server in a domain.

For more information about improvements in Windows Server 2003 Terminal Server, see the "What's New in Terminal Server" white paper at the Terminal Services: Community Center link on the Web Resources page at http://www.microsoft.com/windows/reskits/webresources and "Using Terminal Server to host applications centrally" in Help and Support Center for Windows Server 2003.