It has been almost 10 years since I first set eyes on the installation of a Windows server–based computing operating system, and it has been true love (in the traditional geek-loves-technology kind of way) ever since. My introduction to Citrix WinFrame was very much a life-altering (or at least career-altering) experience, expanding my interests far beyond the simple life of application development to one of systems architecture and the design and implementation of server-based computing solutions. Even back then I saw the potential for the technology, not only in revolutionizing the way companies delivered applications to their employees but also in how IT staff supported that environment. Coming from the world of application development, I had a true appreciation of how difficult it was both to develop the applications for an organization and to roll those products out to the myriad of desktop hardware and software configurations that existed within every company, regardless of its size.
Troubleshooting why the application installed and ran fine on one machine but not on another even though they appeared to be identical was truly a lesson in frustration.
Needless to say I was excited and intrigued by the concept of server-based computing and the potential benefits to be had from providing the end user with a centrally managed, secure, and—best of all—stable environment within which to run their applications. Delivering a consistent computing environment to the user, regardless of their local desktop hardware and software configuration, was like stumbling upon an oasis in the middle of the desert. I saw salvation.
After our project team used WinFrame 1.6 to build a 60-server load-balanced environment, spread across two distinct geographical locations, to successfully deploy a full desktop solution to over 2,000 call center and order processing staff, I was truly a believer. The fact that this little-known product from a small company named Citrix Systems had delivered so thoroughly on such a bold promise was truly remarkable. Considering the number of times we said, “Wow, it actually works,” I’m sure people thought that was our team slogan.
Eight-plus years, three published books, and countless consulting hours later, I still am in love with this technology and continue to be impressed with the ways it can be used to deliver on the expectations of the companies that deploy the product and the end users who work within the environment. Certainly many things have changed since those early days—some good, some not so good—but one thing that remains the same is the truly impressed look on the faces of the IT staff when they see the technology work exactly the way it was promised. I’m pretty sure I had that same look back then, too.
Having said all that, I must also say that an undisputed truth about computers in general is that they do not deliver solutions all by themselves. I have yet to see a software package pop out of a box, jump into a server, and configure itself while the administrator sipped coffee and reviewed stock quotes. Until that day, the ultimate success of a project still is dictated by the people tasked with the job, not the software or hardware deployed.
Unfortunately, for every server-based computing project that succeeds, there is an equal number of projects that would be deemed far from successful. In most cases the list of problems are long and varied, but unfortunately—and whether justified or not—much of the blame falls on the administrators responsible for implementing the environment. Many administrators make the mistake of assuming that because they understand Windows and know how to administer a Windows environment, they’re adequately qualified to deploy Terminal Services. Truly, such thinking is a recipe for disaster almost every time.
It doesn’t have to be this way. With a bit of planning and a lot of patience, any Windows administrator can successfully implement a Windows server–based computing environment. My ultimate goal in producing this book is to provide the knowledge, insight, and guidance necessary to achieve delivering a robust, scalable, and stable server-based computing environment using Microsoft Windows Terminal Services (2000 or 2003) and Citrix MetaFrame Presentation Server 3.0.
This book best serves the Windows administrator who wants to analyze, plan, test, and implement a server-based computing solution running Windows Terminal Services with or without MetaFrame Presentation Server 3.0. It focuses on the entire project life cycle, from properly assessing the needs of an organization and planning all aspects of the deployment (not just how to build a Terminal Server) right through to the actual implementation and support. The book is full of implementation examples, from server security to group policy creation and from patch management to client deployment. While I try to encompass all major aspects of a Terminal Server implementation, there are some areas where I provide only tertiary coverage and/or assume that you’re already familiar with (or are readily able to learn) that area. These areas include the following:
A basic knowledge of Windows Server 2000 and/or Windows Server 2003
An understanding of Windows 2000/2003 Active Directory and how to use the provided tools, such as Active Directory Users and Computers
Installation and use of Windows Internet Information Services (IIS)
In writing this book, my goal was to create a reference useful to administrators at a variety of skill levels related to the Terminal Server and MetaFrame technologies. What if you’re completely new to the world of server-based computing? No problem. Working through this book from beginning to end will instill the knowledge necessary to successfully implement a Terminal Server/MetaFrame environment of any size. After reading this book, you will have the knowledge and understanding necessary to make smart choices about your new Terminal Server/MetaFrame implementation or about the changes necessary to better stabilize an existing environment that you’ve been tasked with managing and supporting.
What if you’re an old-school Terminal Server/MetaFrame administrator who wants to update his or her knowledge on the latest and greatest technology from Microsoft and Citrix? Don’t worry; I’ve got you covered as well. Key changes in the technology such as Microsoft’s new licensing requirements for Windows Server 2003 Terminal Services, the Session Directory technology, and client drive and printer mapping support are all covered. And for all you MetaFrame 1.8 administrators who’re finally looking to upgrade, configuring interoperability between MetaFrame 1.8 and MPS 3.0 is also discussed.
I know that the solutions discussed in this book work, because I’ve used them successfully, but I also know that not all environments are created equally, and creative solutions are the computer-world equivalent of duct tape. When discussing the various aspects of these technologies, I provide suggestions and recommendations on how these can be configured, but unless I explicitly say so, my suggestions should not be taken as the only solution that will work. I always encourage creativity (although it is best kept in the test environment and not in production), and playing around is still the best way to thoroughly understand the limitations of any computer system. One of the biggest differentiators between a good administrator and a great administrator is the ability to create, adapt, and develop solutions under a variety of conditions.
The book is divided into four parts. Part I provides an overview of both the Microsoft Terminal Services and Citrix MetaFrame Presentation Server technologies, describing the main features and functionalities of both. Many of the general questions about the similarities and differences between the two products are answered in this section, including details on exactly what the licensing requirements are, a topic commonly misinterpreted by many people.
Part II is a project manager’s dream come true. In this section I cover the planning considerations of a Terminal Server/MetaFrame implementation, including topics such as client hardware and software planning, server hardware planning, and service pack and hotfix distribution planning.
Part III provides a detailed look at how to actually implement and support Terminal Server/MetaFrame, building on the planning discussed in Part II of the book.
Part IV consists of the appendixes, summarizing information such as the command line tools available with both Terminal Server and MetaFrame and providing detailed introductory information on areas such as file server and registry security.
Chapter 1: “Microsoft Windows Terminal Services”
Looks at the functionality and features of Terminal Services, comparing both Windows 2000 Server and Windows Server 2003 Terminal Services. Differences in areas such as licensing are also reviewed.
Chapter 2: “Citrix MetaFrame Presentation Server”
Focuses on the MetaFrame extensions to Terminal Services and the functionality enhancements it provides. Changes in client licensing management in MPS 3.0 are also introduced.
Chapter 3: “Project Management Considerations”
Provides the project manager of a Terminal Services implementation with an introduction to many of the important tasks that need to be managed before and during the early stages of the project, including implementation requirements, business process management, and policies and procedures.
Chapter 4: “Network Planning”
Examines the importance of the network in your Terminal Services implementation. Printing considerations as well as dial-up and Internet access are also discussed.
Chapter 5: “Client Hardware and Software Planning”
Complete coverage of both the Microsoft RDP and Citrix ICA clients is provided in different deployment scenarios. I also look at the importance of proper client planning for a successful Terminal Services project.
Chapter 6: “Terminal Server Hardware Planning”
Discusses the two main considerations when planning the hardware requirements of a Terminal Server environment: the capacity-planning requirements and the appropriate hardware sizing to meet those requirements.
Chapter 7: “Server and Application Software Planning”
Examines the strategies for categorizing and planning the deployment of both the server and application software.
Chapter 8: “Server Installation and Management Planning”
Looks at planning the Terminal Server installation and the importance of developing a sound technical management plan in order to maximize scalability and stability of the Terminal Services environment. Common monitoring tools are discussed and a general guideline is provided, which can be used to benchmark different tools in order to find those providing the best fit for the implementation.
Chapter 9: “Service Pack and Hotfix Management”
Proper management of service pack and hotfix deployments are critical to ensuring a stable and secure environment. The final planning chapter looks at techniques for managing these requirements.
Chapter 10: “Installing Windows Terminal Services”
Details the steps involved in installation of Windows 2003/2000 Terminal Services. Features such as service pack integration with the base operating system installation and use of answer files are discussed.
Chapter 11: “Terminal Services Configuration and Tuning”
Provides a detailed walkthrough of configuring and tuning your Terminal Server for optimal operation. Performance and stability considerations are discussed.
Chapter 12: “License Server Installation and Configuration”
Terminal Services licensing is a critical component of any Terminal Server environment; its proper deployment is thoroughly covered in this chapter.
Chapter 13: “MetaFrame Presentation Server Installation”
Details the steps involved in installation of Citrix MetaFrame Presentation Server on a Windows 2003/2000 Terminal Server.
Chapter 14: “MetaFrame Presentation Server Configuration”
Configuration tasks specific to a MetaFrame server are discussed in this chapter. All configurable settings within the Management Console are reviewed here.
Chapter 15: “Group Policy Configuration”
Examines use of group policies in Windows Active Directory domain to establish a more controlled and consistent Terminal Services environment.
Chapter 16: “Terminal Server Security”
Focuses specifically on properly securing your Terminal Server implementation.
Chapter 17: “Terminal Server and MetaFrame Printer Management”
An important part of any implementation is the ability of the users to print. This chapter looks at configuration of the various printer features supported in Terminal Server and MetaFrame.
Chapter 18: “User Profile and Account Configuration”
Provides a detailed look at the role of the user profile in a Terminal Services environment and how to effectively manage these profiles. Leveraging centralization of Active Directory and DFS (distributed file system) are also discussed here.
Chapter 19: “RDP Client Installation and Configuration”
Looks at the steps for installation of the RDP client and provides more detailed examples of how you would configure the client based on the desired implementation scenario.
Chapter 20: “ICA Client Installation and Configuration”
Looks at the installation steps required for the Citrix ICA client. Configuration details on features such as the Program Neighborhood Agent and custom installations are also examined.
Chapter 21: “Application Integration”
Provides a detailed discussion of the special application support features available with Terminal Services, the tools and techniques that will assist you.
Chapter 22: “Server Operations and Support”
Looks at the shift in responsibility from implementation to operations and the tools that can be used to ensure availability of the production environment to the end user.
Appendix A: “Terminal Services Command Reference”
Contains a complete list and explanation of Terminal Services–specific commands. Examples and common usage situations are also provided.
Appendix B: “MetaFrame Presentation Server Command Reference”
Describes the command line tools provided with MetaFrame. Examples and common usage situations are also provided.
Appendix C: “Network Primer”
Provides a general overview of networking and the OSI model.
Appendix D: “Terminal Server Tuning and Configuration Checklist”
A brief checklist that summarizes the settings discussed in Chapter 11.
Appendix E: “File System and Registry Security Primer”
Looks at Windows NTFS and registry security.