The Definitive Guide to Windows Server 2003 Terminal Servicesby Greyson Mitchem
The Definitive Guide to Windows Server 2003 Terminal Services not only introduces you to Windows Server 2003 Terminal Services but also walks you through and touches upon installation and configuration issues, load balancing and session directories, administration of Terminal Services, and much more.
Chapter 1: Introduction to Windows Server 2003 Terminal Services
With the launch of Windows Server 2003 (WS2K3), Microsoft has continued to improve upon Terminal Services. At the launch event, Microsoft focused on the fact that this version of Windows is the most customer driven to date. Terminal Servicesâ€™ new features clearly demonstrate this focusâ€”there are certainly several enhancements that I have been hoping for.
n this book, I will introduce you to the new features and enhancements in WS2K3 Terminal Services. I will also discuss best practices for configuring and managing Terminal Services with an eye to the new techniques available to systems administrators in WS2K3. As weâ€™ll explore, with Remote Desktop Protocol (RDP) 5.2, Active Directory Service Interfaces (ADSI) access to Terminal Services attributes of user objects, new Group Policy Object (GPO) controls, and Session Directory, we now have the ability to use native Terminal Services as an enterprise-class solution for providing users with Terminal Servicesâ€“based desktops.
Chapter 2: Installing and Configuring the Terminal Server Role
This chapter will take you through the steps of adding the terminal server role to WS2K3. Iâ€™ll introduce you to the settings used to configure a terminal server via the administrative tools, Group Policy, and registry editor, and even give you a few system tweaks to help improve your serverâ€™s performance. Finally, I will give you an in-depth look at the Remote Desktop Connection client, and the new version of the Terminal Server Advanced Client (TSAC)â€”Remote Desktop Web Connection. Iâ€™ll begin by exploring the most common reasons for deploying Terminal Services.
Chapter 3: Load Balancing and Session Directory
If you have more users than a single terminal server can support or you need the ability to take a server offline for maintenance or application installations without impacting availability, load balancing will become an integral part of your Terminal Services architecture. In this chapter, I will introduce you to the native Microsoft Network Load Balancing (NLB) service. I will also cover a new feature of WS2K3â€”Session Directoryâ€”which enables Windows to track user sessions across multiple servers so that users can reconnect to the sessions when needed.
Iâ€™ll begin by introducing you to the basics of terminal server hardware configuration, then weâ€™ll explore terminal server sizing. This foundation of information will enable you to determine how many servers you need to support your usersâ€™ needs.
Chapter 4: Terminal Services Administration
As with any technology deployment, the process of installing and configuring your terminal server is only half the work. You must also plan for ongoing administration and maintenance and software life cycle management. In this chapter, weâ€™ll focus on Terminal Services administration, including user account configuration and management. In addition, weâ€™ll explore GPO-based configuration from an AD perspective. I will introduce you to loopback policy processing, the creation of custom administrative templates, and the domain policy processing order. I will also walk you through some common terminal server administrative tasks and introduce you to the toolsâ€”both GUI and command lineâ€”used to manage terminal servers and user sessions. Letâ€™s start by jumping into user account administration.
Chapter 5: Application Installation and Compatibility
Weâ€™ve explored how to enable the Terminal Services role, create and manage a Session Directory farm, and integrate terminal servers into your AD environment. All of these factors are vital to a successful Terminal Services infrastructure, but it is the user applications that can make or break your terminal server deployment.
As Terminal Services evolved, user applications have also evolved. Today, the majority of applications will install natively on Terminal Services and function in a multi-user environment without modification. However, there will always be a mission-critical program that is either legacy or from a vendor that does not follow the Microsoft Windows Logo specifications, so it is important to become familiar with the various features available in Windows Server 2003 to help address application compatibility.
This chapter will focus on installing, deploying, and managing applications in a Terminal Services environment. Youâ€™ll learn how to tune applications for simultaneous users, write an application compatibility script, and use Terminal Services registry flags to handle legacy applications. Iâ€™ll discuss the various administrative modes that youâ€™ll use and how to test an application for Terminal Services compatibility.
Chapter 6: Managing Security and Virus Protection
Blaster, Love Bug, Nimda, Melissaâ€”computer viruses and worms are a fact of life these days, so Windows infrastructure design must take them into account. Virus scanning software, firewalls, and patch management should be a part of even the smallest environments. If users will be accessing email or browsing the Internet from terminal servers, you will need to be vigilant in keeping your servers safe and virus free. Luckily, the restrictive permissions on a terminal server make it difficult for users to introduce viruses to the system; nonetheless, you should be prepared.
In this chapter, we will explore available options for keeping servers secure and up to date, including Microsoft Automatic Updates and Software Update Services, as well as best practices for implementing these options in your environment. In addition, I will highlight considerations for installing virus scanning software on terminal servers.