The document is archived and information here might be outdated
Published: February 25, 2008
This guide leads the reader step by step through the process of planning a Windows Server 2008 Terminal Services infrastructure. The guide addresses the following fundamental decisions and tasks:
Identifying which applications are to be delivered by Terminal Services and determining whether Terminal Services is the right approach to use.
Determining the resources needed to employ Terminal Services to serve the selected applications.
Designing the components, layout, security, and connectivity of the Terminal Services infrastructure
Before starting the technical design, it’s very important to fully understand the business objectives for the project:
What benefits does the business expect to achieve through the use of presentation virtualization? Presentation virtualization uses centralized systems to host multiple user sessions, and all processing is done on those host systems. The user sessions are isolated from each other. Only the presentation information, such as keyboard and mouse inputs, and video updates are sent between the client and the host system. The client can be a full Windows-based workstation or a Windows-based terminal device.
What is the value of those benefits and, therefore, the cost case for using Terminal Services to deliver those benefits?
Is the cost justification jointly entered into by more than one business group, and if so, do they depend on the success of the project for their relationship with each other?
The business objectives should be prioritized right at the start of the project so that they are clearly understood and agreed upon between IT and the business. This is because some applications will not likely be immediately suited to delivery by Terminal Services. Those changes will incur cost and, before embarking upon them, this should be fed back to the business so that the additional costs can be understood and the best business decision arrived at.
The content in this guide assumes that the reader is familiar with Terminal Services technology and is planning an implementation of servers, farms, or both in Windows Server 2008.