List of Figures

Chapter 2: Terminal Server Architecture

Figure 2.1: Terminal Server 2003 components

Figure 2.2: Each Terminal Server maintains many separate user sessions

Figure 2.3: A Terminal Server with multiple connection ports

Figure 2.4: Terminal Server 2003's virtual channel architecture

Figure 2.5: A new session is established

Figure 2.6: 32-bit Windows Server 2003 Terminal Server features

Chapter 3: Terminal Server Network Architecture

Figure 3.1: Terminal Server network communication

Figure 3.2: Users in two offices need access to the same database application

Figure 3.3: A Terminal Server at the main office

Figure 3.4: Terminal Server placement at the remote office

Figure 3.5: Multiple Terminal Servers provide fast access to data

Figure 3.6: All Terminal Servers in one datacenter

Figure 3.7: Users often need to access multiple types of data from one session

Figure 3.8: A user in Europe needs to access data throughout the world

Figure 3.9: Application support from multiple people in multiple locations

Figure 3.10: The wrong way to implement the licensing service.

Figure 3.11: The proper way to implement the licensing service

Figure 3.12: A single AD forest with three down-level domains

Chapter 4: Licensing

Figure 4.1: Microsoft licensing components

Figure 4.2: Terminal Servers periodically verify that they can contact license servers

Figure 4.3: Microsoft license server discovery process

Figure 4.4: The Terminal Server 2003 Device-Based TS CAL Licensing Process

Chapter 5: Application Strategies and Server Sizing

Figure 5.1: Applications installed on various silos

Figure 5.2: A few gigantic servers

Figure 5.3: Many smaller servers

Figure 5.4: Popular Windows application usage scripting tools

Chapter 6: Customizing the User Environment

Figure 6.1: Elements of a user profile.

Figure 6.2: The user logon process with local profiles

Figure 6.3: The user logon process with roaming profiles

Figure 6.4: The user logoff process with roaming profiles

Figure 6.5: The user logoff process with Hybrid profiles

Figure 6.6: The user logon process with Hybrid profiles

Figure 6.7: Users often connect to multiple Terminal Servers

Figure 6.8: A situation that might require multiple profiles for each user.

Figure 6.9: Differences between profiles and policies

Figure 6.10: Home folder Mapping Process

Figure 6.11: Some users need data in multiple locations

Figure 6.12: The various methods that can be used to launch scripts

Figure 6.13: Parker HealthNet's WAN Architecture

Figure 6.14: Typical Hospital with Terminal Server application access

Figure 6.15: Roaming profile and home folder Locations

Chapter 7: Designing High Availability Solutions

Figure 7.1: The Terminal Server components that must be functional

Figure 7.2: Redundant servers with data on a SAN

Figure 7.3: The elements of a Terminal Server cluster

Figure 7.4: The user connection process through a hardware load balancer

Figure 7.5: Load balancing in NAT environments

Chapter 8: Printing

Figure 8.1: The Windows printing process

Figure 8.2: The various types of Terminal Server printers

Figure 8.3: Server Printers in a Terminal Server environment

Figure 8.4: Server printers are not efficient when the Terminal Servers are remote

Figure 8.5: Printing to a client printer attached locally to a client device

Figure 8.6: Terminal Server printing to a client network printer

Figure 8.7: The Third-Party Universal Print Driver Process

Figure 8.8: The third-party EMF-based printing software process

Figure 8.9: Terminal Server in a WAN environment

Figure 8.10: Network printers at the Terminal Server location

Figure 8.11: Network printers at the regional offices

Figure 8.12: Network printers at remote office locations

Figure 8.13: Local printers attached to client devices

Chapter 10: Deploying and Configuring Remote Desktop Clients

Figure 10.1: RDP clients and the features they support.

Figure 10.2: An RDP file that launches Microsoft Word 2000 on tsserver01

Chapter 11: Accessing Terminal Servers via Web Portals

Figure 11.1: How the remote desktop web connection client works

Figure 11.2: The process of launching RDP applications from a web page

Figure 11.3: A quick application launching webpage made with FrontPage

Figure 11.4: A more sophisticated looking webpage based on the same basic code

Chapter 12: Security

Figure 12.1: Terminal Server layers

Figure 12.2: The drive mapping security parameter configured at multiple layers

Figure 12.3: Various configuration scope layers

Figure 12.4: Secedit configuration options

Figure 12.5: Advanced connection permission properties

Figure 12.6: Preconfigured connection permission levels

Figure 12.7: Terminal Server network segments

Figure 12.8: An RDP session encrypted via a VPN tunnel

Figure 12.9: Encrypting the RDP session

Figure 12.10: A Terminal Server outside the firewall

Figure 12.11: A Terminal Server behind the firewall

Figure 12.12: A Terminal Server in the DMZ

Figure 12.13: Firewall port usage

Figure 12.14: Network address translation at the firewall

Figure 12.15: The firewall translates the RDP client's request

Chapter 13: Performance Tuning and Optimization

Figure 13.1: Selected sample lines from a userenv.dll log

Figure 13.2: Components of the Windows memory usage analogy

Figure 13.3: Bandwidth shaping hardware

Chapter 15: Server Management and Maintenance

Figure 15.1: The change management lifecycle

Figure 15.2: Typical users and their permissions

Figure 15.3: The complete change control cycle

Figure 15.4: A sample change control log entries