HOW THIS BOOK IS ORGANIZED

This book provides the framework to design and implement a successful access infrastructure for an on-demand enterprise. Our focus is on using Windows Server 2003 Terminal Services and Citrix Access Suite 4 to accommodate hundreds or thousands of users running their desktop applications from one or more central data centers. We address the myriad technical, design, and implementation issues involved in constructing this environment, and assume readers already have a good working knowledge of networking and system administration for Windows Server 2003.

The book is divided into three parts . Part I provides an overview of the Citrix Access Platform. This section reviews Windows Server 2003 Terminal Services and Citrix Access Suite 4 and includes justifications for enterprise deployments. Part II covers the design of an on-demand computing solution and ranges from planning and internally selling the project to providing guidelines for data center and WAN architecture, file services, remote access, security, network management, and thin-client devices. Part III covers the deployment of an access platform and includes project management, installation, automation, server farms, profiles, policies and procedures, printing, and migration methodologies.

In Appendix A, we present internetworking basics for those who would like a quick brush-up on networking concepts. Appendix B provides a methodology for building a spreadsheet-based financial model to analyze the comparative benefits of on-demand versus client-side computing. Appendix C includes a suggestion for creating a utility-like billing model for charging users for application hosting.

We include Notes, Tips, and Cautions to supply additional detail to the text. A Note is meant to provide information when the general flow of the discussion is concentrating in a different area or is not as detailed as the Note itself. A Tip is a specific way to do or implement something being discussed. A Caution is meant to alert the reader to watch out for a potential problem.

Writing a book about such a rapidly evolving technology poses a challenge. By the time this book is published, additional tools and practices will be coming on the scene. Fortunately, the methodologies and approaches we describe should be relatively timeless, and should prove very useful as you begin your own enterprise access platform project.