Configuring Citrix MetaFrame for Windows 2000 Terminal Services
Helps administrators get up to speed on MetaFrame, including designing solutions, installing the software, and configuring remote client access.
TABLE OF CONTENTS Configuring Citrix MetaFrame for Windows 2000 Terminal Services
Chapter 4: Designing a Citrix MetaFrame Internetwork
Introduction
Citrix MetaFrame is not identical to Windows 2000 Terminal Services. It is a set of applications, utilities, and a proprietary Citrix thin-client protocol that is installed on top of Windows 2000 Server, which already has Terminal Services installed.
While the Citrix MetaFrame design has many of the same requirements that Windows 2000 Terminal Services design has, there are many differences, which dictate different design considerations. These differences are based on the protocols and client operating systems that are supported. Citrix MetaFrame also has the ability to provide load balancing of applications, which can impact the design and placement of the servers.
Designing and Placing MetaFrame Servers on the Network
Most technology projects follow the same process. First you have a business requirement that drives a vision. The vision then gives rise to the method with which the company seeks to satisfy the business requirement with a process and/or technology change. This leads to a design stage, followed by testing and development. Then there is a pilot, and finally a full-production deployment of the process and/or technology. At some point in the future, there may be another business requirement requiring this process to begin all over again, so it is somewhat cyclical in nature. This proc-ess is illustrated in Figure 4.1.
Figure 4.1: Project cycle.
When you begin designing your Citrix MetaFrame environment that is, the server and the network on which it will communicate you should already have one or more business requirements and a vision that the MetaFrame server...
Copyright Syngress Publishing, Inc. 2000 under license agreement with Books24x7
