Planning an Implementation of

Citrix® MetaFrame™ XP on Dell™

PowerEdge™ ServersEnterprise Systems Group (ESG)

Dell White PaperBy Fred Gonce

July 2001

ContentsExecutive Summary.............................................................................4Introduction........................................................................................6

Server-based Windows Environments.......................................................6Engaging a Citrix Specialist......................................................................6Understanding the Deployment Environment...........................................7Selecting a Server.....................................................................................7Licensing Software....................................................................................7

Windows Terminal Services................................................................8Citrix MetaFrame XP.........................................................................10

Benefits of Adding MetaFrame to Windows Terminal Services..............11Client Features........................................................................................11Server Features.......................................................................................12MetaFrame XP Changes..........................................................................13Published applications on the user desktop............................................14

Planning an Implementation.............................................................16Selecting an Implementation Environment.............................................16Server Sizing Guidelines.........................................................................16Citrix MetaFrame Sizing.........................................................................16User’s Expectations.................................................................................16Understanding the Deployment Environment.........................................17General Sizing Guidelines.......................................................................17Defining User Types...........................................................................................17Types of Applications..............................................................................18Storage....................................................................................................19Network...................................................................................................20Other Considerations..............................................................................20Choosing the Correct Server for the Implementation.............................20Test Tools................................................................................................21

Conclusion.........................................................................................22Appendix A........................................................................................24

Multi-User Windows................................................................................24Citrix Products........................................................................................24Server Products.................................................................................................24Management Products.......................................................................................24Portal Products..................................................................................................24ICA Clients.........................................................................................................24

Appendix B........................................................................................25Planning considerations before deployment.....................................25

General....................................................................................................25Servers....................................................................................................25Applications.............................................................................................26Clients.....................................................................................................26Connectivity............................................................................................27

July 2001 Page 2 Dell Enterprise Systems Group

Other considerations...............................................................................27References...............................................................................................28

Appendix C........................................................................................29Feature Overview of RDP & ICA........................................................29Appendix D........................................................................................32Contact Information..........................................................................32

Dell Resources.........................................................................................32Appendix E.........................................................................................33Reference Material............................................................................33

Citrix MetaFrame....................................................................................33Microsoft Windows 2000 Terminal Services...........................................33

Figure 1: Delivering applications to the enterprise....................................................5Figure 2: Terminal Services Client Desktop................................................................9Figure 3: MetaFrame published applications............................................................15

Table 1: Users per CPU.............................................................................................19Table 2: Memory requirements.................................................................................19Table 3: Recommended Number of Users Per PowerEdge Server............................19

July 2001 Page 3 Dell Enterprise Systems Group

Section 1Executive Summary

This paper is the first in a series -- targeted at technical sales representatives, system consultants, and technical field support -- to assist in better understanding the process of deploying multi-user Microsoft® Windows® using Dell™ PowerEdge™ servers. Successfully deploying Terminal Services and MetaFrame™ to the enterprise usually requires multiple phases. First is the planning phase, which may require evaluation software to validate customers’ applications. Next is the pilot phase, used to customize and tune hardware and software in the customer’s environment. Finally, a phased rollout is used to tune and customize hardware and software on a workgroup or departmental basis to provide the best user experience for each workgroup. This paper covers the planning phase of an implementation, and compares the features and function of Windows 2000 Terminal Services and Citrix® MetaFrame XP™. This information is presented to assist the implementer in choosing the proper deployment environment for the customer’s solution.

Many customers today need to overcome the challenge of delivering applications to many different clients across the enterprise using a common technology that is scalable and manageable. A good solution minimizes the retraining of users and integrates easily into the existing environment while delivering the features and function required by users. Customers also require enterprise level deployment and management tools to assist with implementation and maintenance of the solution. See Figure 1 for an enterprise deployment of MetaFrame to better understand the complexity it supports.

July 2001 Page 4 Dell Enterprise Systems Group

Source: Citrix Systems Inc.

Figure 1: Delivering Applications to the Enterprise

Server-based computing using Microsoft Terminal Services and Citrix MetaFrameTM has become a popular way to make window applications available to the corporate enterprise. Dell recommends using a qualified Citrix Solution Network Member throughout the three phases to provide the best solution for the planned deployment.

The goal of this paper is to provide better understanding of the features and function of both Windows Terminal Services and Citrix MetaFrame to help clarify the benefits of choosing each solution.

July 2001 Page 5 Dell Enterprise Systems Group

Section 2Introduction

Server-based computing using a Windows operating system is a logical and efficient way of managing and extending Windows client applications and resources to the enterprise while simplifying application deployment and administration and potentially lowering the total cost of application ownership. Server-based computing using Windows allows clients (Win-32, Win-16, UNIX, MAC, and others) to access and execute Win-32 based applications on remote Windows Servers while the display is on the local client. Dell provides a variety of PowerEdge servers to meet the needs of customer deployment environments.

Server-based Windows Environments

A good understanding of the features and functions provided by Windows Terminal Services and Citrix MetaFrame XP will assist the implementer in planning the solution that will benefit the customer the most.

Windows Terminal Services provides a good solution for a workgroup deployment of Windows clients. The section on Windows Terminal Services covers the features and functions provided by using only Terminal Services.

Citrix MetaFrame is added to the Windows Terminal Services environment to provide support for additional clients (Windows, UNIX, MAC, Java, Web, and others) enhanced features, as well as it provides more enterprise management tools for managing the deployment. The section on Citrix MetaFrame describes some of the features and benefits of adding MetaFrame to a Terminal Services solution.

Engaging a Citrix Specialist

Engaging a Citrix specialist early on in the planning process can be very beneficial and increases the probability of a successful pilot and deployment. Since there can be many variables (software, hardware, network topology, and users expectations) that determine the success of the project, it is important that the implementer engage someone who has the expertise to identify problems early on and offer alternative solutions that will help ensure the success of the project.

Understanding the Deployment Environment

July 2001 Page 6 Dell Enterprise Systems Group

A good understanding of the deployment environment is key to successfully implementing server-based Windows solutions. This includes a thorough knowledge of memory and CPU requirements of applications to be supported for the deployment, network topology -- including LAN, WAN, and wireless support -- and how users will be using the applications.

In order to provide the application availability and performance expected by users, it is important to understand the memory and CPU utilization required by client systems when they access server resources. This includes peak load times such as everyone logging on in the morning or after lunch, as well as end-of-cycle processing, when many users are trying to connect and use resources at the same time.

A list of questions is included in Appendix B that will assist the implementer in better understanding the customers environment.

Selecting a Server

To assist the implementer in selecting the proper hardware, the Planning an Implementation section provides some guidelines in order to assist with the selection of the proper PowerEdge Server. Since there are many considerations when selecting a server such as rack mount or tower server, this section only discusses two systems (a 2-way and a 4-way), and describes the type of deployment for which each is best suited. With the information contained in this section, the reader should be able to determine which Power Edge server is the best choice for a particular solution.

Licensing Software

Microsoft Terminal Services is bundled in the Windows Server OS. The licensing of the product comes through the client access licenses or CALs.

Citrix and Microsoft have different license models. The Citrix pricing model is based on active users (the maximum number of simultaneous users on a server at any given time). The Microsoft model for Win2000 Terminal Services is based on named users (all users accessing the server including those who are not logged on). Microsoft’s licensing costs increase relative to Citrix's as the proportion of total users to active users increases. See Appendix E for information on licensing Citrix’s software.

July 2001 Page 7 Dell Enterprise Systems Group

Section 3Windows Terminal Services

Terminal Services (TS) is integrated into Windows 2000 Server, Windows 2000 Advanced Server, and Windows 2000 Datacenter Server. It only requires the component to be installed during the server installation, or added through “Add/Remove Programs” after the installation of the server. Windows NT® Server 4.0, Terminal Service Edition (TSE) is separate from Window NT Server 4.0 and must be purchased separately. Windows 2000 Terminal Services (TS) uses several technologies that allow multiple clients to remotely execute applications on a Windows-based server while the display is on a remote Windows client device. When Terminal Services is mentioned in this paper, it is referring to Windows 2000 Terminal Services. The multi-user kernel and other technologies that are used for TS were originally developed for TSE, so some of the function discussed in this paper also applies to TSE.

By using TS, the administrator does not have to install Windows-based 32-bit applications on each client desktop computer. The applications can be installed on the server(s) and the clients can automatically have access to the software packages through Terminal Services Client software. This also assures that all clients are accessing the same version of software, since they access it from the same server. Using a Terminal Services client, users of older Windows PCs can access applications that cannot be installed on their current systems. Terminal Services Advanced Client is supported on Internet Explorer 4.0 and above, which allows clients with an IE 4.0 client to access TS.

Using this model can reduce the cost and challenges of updating clients’ systems, especially for remote users who may otherwise not have easy access to current versions of software. Through TS, Windows systems such as Windows for Workgroups 3.11 and Windows CE devices now have access to 32-bit Windows-based applications. In addition, the ‘Remote Control’ capabilities can simplify the support of client applications, by allowing the support staff to view and control a user’s session.

Windows Terminal Services can be configured in administrative mode for the Windows 2000 Server family. This allows two Terminal Service Client connections for system administrators to remotely access and administer servers.

Remote Desktop Protocol (RDP) is the protocol that allows a TS client to communicate with the TS server over the network. See Appendix C for a feature function comparison of RDP 4 and RDP 5.

July 2001 Page 8 Dell Enterprise Systems Group

Figure 2: Terminal Services Client DesktopSource: Microsoft Corporation

Figure 2 shows two desktops displayed when using TS client to connect to a TS server. When the client is started, it first prompts the user for a server to connect to, and then prompts the user for a user name and password. Using a Terminal Services client, the user connects to the TSE or TS and logs in using a user name and Password. When connected to the server, the user can remotely execute applications on the server with the display on the client within the TS client window.

The administrator customizes the users desktop on a per user, group, or global level to provide users with the applications they need.

July 2001 Page 9 Dell Enterprise Systems Group

Section 4Citrix® MetaFrame XP™

MetaFrame XP is the latest version of the MetaFrame™ software, and it supports Windows 2000 Server products with Terminal Services installed, and Windows NT Server 4.0 Terminal Server Edition. Previous versions of MetaFrame required different versions of Windows to be installed and configured before installing MetaFrame. The following is the software stack required for MetaFrame:

MetaFrame XP for Windows Windows 2000 Server, Advanced Server, and Datacenter

Server, w/ Terminal Services installed -or- Windows NT® 4.0, Terminal Server Edition

MetaFrame 1.8 for Windows 2000 Servers Windows 2000 Server, Advanced Server, and Datacenter

Server, w/ Terminal Services installed MetaFrame 1.8 for NT 4.0, Terminal Server Edition

Windows NT 4.0, Terminal Server Edition

Many of the features in Terminal Services appear to a subset of features offered by MetaFrame. Implementers may be able to successfully deploy the required applications using only Terminal Services, but they should also consider other factors like user experience, performance, management, and maintenance of the solution after deployment.

Implementers need a good understanding of the software provided by Citrix as well as the benefits of its features. This section of the paper compares the features in MetaFrame with similar features in Terminal Services. For deployments that involve more than a small workgroup, implementers should consider including MetaFrame during the pilot phase to fully understand the benefits of the features it provides to users and the management, and maintenance packages available to the administrator.

See Appendix A for a complete list of Citrix Products.See Citrix web site for a complete description of products and features.

July 2001 Page 10 Dell Enterprise Systems Group

Benefits of Adding MetaFrame to Windows Terminal Services

Citrix MetaFrame brings additional benefits to the server-based computing model by adding support for a heterogeneous computing environments, enterprise-scale management tools, and seamless desktop integration of client systems. MetaFrame extends the functionality of Microsoft® Windows NT® Server 4.0, Terminal Server Edition and Microsoft Windows 2000 Terminal Services in the following ways: Provides enterprise application management for increased

scalability Provides deployment and simplified application support Enables applications for the Web Allows universal application access to users in virtually any

location, on any device, over any network connection, including wireless, to Web

The following guidelines have been included to help implementers better understand the differences between Terminal Services, and MetaFrame, and explain how MetaFrame adds value over Terminal Service alone.

Client FeaturesNote: The information in this section and the Server Features section comes from RYNO Technology, written by Marc Mangus. For more information about RYNO, please consult its website at http://www.ryno.com/webcontent.nsf.

The following is a feature function comparison of MetaFrame and Terminal Services. See Appendix C for a detailed feature overview of ICA (MetaFrame’s client protocol) & RDP (Terminal Services’ client protocol).

Client Platform Supporto The Independent Computing Architecture (ICA) client

software from Citrix lets users connect to Citrix servers and access applications. ICA client software is available on many platforms including Windows, UNIX, Linux, MAC, Java, Web, and others. This allows an organization to keep existing infrastructures while deploying advanced 32-bit Windows-based applications across the enterprise.

o Terminal Services’ RDP supports 16 and 32-bit Windows clients

Multi-protocol supporto MetaFrame supports most LAN, WAN, Internet, and

Wireless connection types running TCP/IP, IPX/SPX, NetBEUI, and direct asynchronous protocols.

o RDP supports TCP/IP

July 2001 Page 11 Dell Enterprise Systems Group

Seamless Windowso With MetaFrame, a published application can appear as an

icon on a user's Windows desktop PC. The user clicks and runs the application just as if it were local.

o With RDP, the user must login to another desktop and switch between the local and remote (server) desktop sessions.

Color Depth / Latency Reduction o Version 6.0 of the ICA Client supports high color (16 bit)

and true color (24 bit) color depths for ICA sessions. It supports all currently available resolutions. (High color depth and resolution are critical elements in achieving user satisfaction in areas of image quality and for satisfactory video performance.)

o RDP provides a maximum depth of 256 colors.

Server Features

Load Balancingo ICA uses session count, processor utilization, memory

utilization, and several other factors to determine where to send a user session. If users sessions disconnect, they will be reconnected to their old session upon login. Due to application publishing support, different applications can be published from different servers. It doesn't matter to which server users connect.

o RDP on Windows 2000 relies on a feature called "Network Load Balancing Services" (NLBS). NLBS only uses network traffic to determine connection assignments to a given server; application performance is not taken into account. If a user session disconnects, there is no guarantee he/she will get the session back upon reconnecting. Also, since RDP does not support application publishing, all the servers must have the same applications configured the same way or a user may connect to a server that doesn't have his/her application. NLBS is only included with Windows 2000 Advanced Server and Windows 2000 Datacenter Server.

Application Publishingo MetaFrame has the ability to expose either an entire

Windows desktop or a single application to a user.o RDP only has the ability to make a Windows desktop

available to the user.

Web Application Accesso MetaFrame's portal technology, NFuse, provides a web-

based "front-end" to any published application or desktop. No changes to the application or special administration are required. NFuse also has several ways to personalize a web page by a user, group or other criteria, and mix content from both MetaFrame and non-MetaFrame sources. For

July 2001 Page 12 Dell Enterprise Systems Group

example, a user could have a web page with Microsoft Office application icons as well as company news from an Intranet site and stock quotes from an external source.

o RDP has the rudimentary capability to provide access through a browser via an ActiveX control.

Automatic Client Drive Mappingo MetaFrame allows the option to control client drive

mapping from the server or from the client. Typically, client drive mappings are controlled at the server and require no changes or interaction from the client. Drive mapping works on all supported client platforms (Mac, UNIX, etc.). ICA drive mapping relies on TCP, UDP, and IP protocols, and it functions well over the Internet.

o RDP requires a .DLL and a registry change on the client and a registry change on the server before any drive mapping is possible. RDP uses Netbios name resolution to map client drives, which means drive mapping will not work over the Internet and will not work reliably without a WINS service running on the LAN.

Auto-created Printerso MetaFrame supports printers that are connected directly to

a client or to the network. Printer mapping works on all supported client platforms (Mac, UNIX, etc.)

o RDP only supports printers connected to the local client.

Shadowingo An administrator logged into any server running

MetaFrame can attach to, watch, or control, any user session on any other server running MetaFrame. A single administrator session can shadow multiple user sessions. Multiple administrator sessions can shadow a single user session.

o RDP has a remote control feature that allows an administrator to watch or control a single user session on the same machine on which the administrator is logged on.

Citrix MetaFrame for UNIXo MetaFrame for UNIX provides the benefits of improved

performance over low-bandwidth connections and tighter security. Using the same Citrix client, users have access to Windows MetaFrame servers and UNIX MetaFrame servers.

o RDP does not provide connectivity to UNIX

MetaFrame XP Changes

With MetaFrame XP, Citrix has changed the packaging model for the new software, as described in the following:

July 2001 Page 13 Dell Enterprise Systems Group

MetaFrame XP supports Windows NT Terminal Server Edition, Windows 2000 Server, Windows 2000 Advanced Server, Windows 2000 Datacenter Server, and the upcoming “Whistler” technology.

Available in three tailored solution environments: MetaFrame XPs, XPa, XPe.

o XPs – includes Citrix Management Console, Centralized Printer Management, Centralized License Management, Active Directory Support, Advanced Shadowing, Client Time Zone Support, NFuseTM1.5

o XPa – adds Advanced Load Managemento XPe – adds Application Packaging & Delivery, Network

Management, System Monitoring & Analysis

The new licensing model provides single-point license installation and administration.

See Citrix MetaFrame XP Administrator’s Guide for more details.

Published Applications on the User Desktop

In addition to connecting users to the Windows Server desktop like Terminal Services, MetaFrame allows the administrator to publish applications to users and groups. By publishing applications, the users are able to add an icon to their desktop so they can access the application directly without signing onto the server and launching the application. This provides seamless integration of server applications on the users’ workspace. Users are now able to access applications as though they were installed locally on their systems. The ICA client can be configured to access the user’s local resource (CD ROM, local drive, floppy disk, etc.). This eliminates the problems that users may have when moving from local applications to server applications.

In Figure 3, a published application (Acrobat Reader) has been added to the user’s desktop so when it is opened the user is taken directly into the application. This simplifies user access to server-based applications.

The administrator can publish applications to users and groups, so that only required applications are accessed on the server system.

July 2001 Page 14 Dell Enterprise Systems Group

Figure 3: MetaFrame Published ApplicationsSource: Citrix Systems, Inc.

July 2001 Page 15 Dell Enterprise Systems Group

Section 5Planning an Implementation

With a good understanding of the customer’s deployment environment and future plans and requirements, the implementer is ready to size the servers that will be used for the pilot phase. During the pilot, the implementer will be able to make changes to the configuration, identify problems, find resolutions, and tune the solution before the final deployment.

Selecting an Implementation Environment

Unless the implementer and the customer have determined that Terminal Services fully meets the needs of the deployment, it is a good idea to include MetaFrame in the pilot to better understand the features and functions provided by both. Citrix provides evaluation versions of software that can be used during the piloting phase.

Server Sizing Guidelines

Selecting and sizing the server to use in the implementation is based as much on the deployment and applications as the number of users that will be supported. Therefore, knowing the number of users that need to be supported is only the first step in properly choosing and configuring the server that will be used for the deployment.

Citrix MetaFrame Sizing

Selecting and sizing a server for a Citrix MetaFrame deployment is dependent on many factors, and this document should only be used as a guideline to help with planning a pilot. After the pilot, the implementer will better understand the configuration that best meets the needs for the deployment.

User’s Expectations

The users of the system require a certain level of function and performance, and this will affect the final sizing of the deployment. This is one of the main reasons to do a pilot; it will give the implementer a better understanding of usage patterns and activities. By using monitoring tools over the duration of the pilot, the implementer will better be able to identify problems areas and to tune the configuration for the deployment environment.

July 2001 Page 16 Dell Enterprise Systems Group

Understanding the Deployment Environment

Many questions need to be answered in order to better understand the customer environment so that the proper hardware and software can be configured for the MetaFrame pilot. The questions in Appendix B, are designed to help the implementer to better understand the customer environment.

Most companies find that they have different kinds of users and it is necessary to group the users into different categories to better understand the resources needed for a planned deployment. So it is important to understand how many of each type of user will need to be supported.

General Sizing Guidelines

The sizing guidelines provided here are very general, and each deployment will vary. Careful planning needs to be done to better understand the actual implementation based on the supported environment.

Understanding users’ applications and the way they are used will help determine the type of user on which to base the server sizing.

Defining User TypesAn important part of using this guideline for sizing a MetaFrame server is categorizing the types of users that will be accessing the server and identifying the types of applications the users will be requiring. Citrix identifies two types of users: “Typical User” and “Power User.” Dell has provided two additional categories to emphasize the need to pilot applications to better understand resource utilization, and when it is difficult to group the users into one of the types provided by Citrix:

o The “light user” is one who only accesses an application infrequently, and the application uses less than 4 MB of memory. Depending on the applications and the way the user works, the number of users per CPU can be much higher than the “typical user.” The number of users per CPU is highly dependent on the application accessed.

o The “typical user” is one who uses one or two applications, and there is little data transferred between the client and server. The amount of memory required by all users’ applications is between 4 and 8 MB of memory. For example, a user who accesses a single instance of MS Word would fall into this category, as long as he/she does not use Object Linking and Embedding (OLE), or access other applications. See Tables 1, 2, and 3.

o The “power user” is one who typically has multiple applications active at one time, and more data is being moved between the client and server. The amount of memory required by all of the

July 2001 Page 17 Dell Enterprise Systems Group

users applications would be between 8 and 16 MB of memory. See Tables 1, 2, and 3.

o The “advanced power user” plus would be a user who accesses applications that require more than 32 MB of memory for all user applications. For this type of user, it may require a pilot in order to better understand resource utilization on the server.

Types of Applications

Type of applications used by light users:o Wordpado Character-based terminal emulator

Type of applications used by typical users:o Microsoft® Word1

o Microsoft® Excel1

o Microsoft® Outlook 2000o Microsoft® Internet Explorer (IE) 2

o Adobe® Acrobat® Reader3

Type of applications used by power users:o Microsoft® Officeo Microsoft Wordo Microsoft Excelo Microsoft® Outlook 2000o Microsoft Internet Explorero Adobe Acrobat Reader

Type of applications used by advanced power users:o SAPGUIo CAD/CAM

NOTE: 1 – No Object Linking and Embedding (OLE) is used, only simple documents. 2 – The types of web pages accessed and the features of IE used will determine user resource utilization. 3 – Large PDF files will consume more resources.

Tables 1-3 show processor, memory, and server capacities to be used as guidelines for planning the deployment, but the implementer should also allow for expandability of server resources depending on the final deployment.

CPU Typical Users Power UsersPIII 30 to 50 20 to 30PIII Xeon 30 to 501 20 to 301

Table 1: Users per CPU

Memory Typical Users Power UsersSystem 128 128

July 2001 Page 18 Dell Enterprise Systems Group

Users’ Applications 4 to 8 MB 8 to 32 MBTable 2: Memory Requirements

Dell Server Typical Users Power UsersPowerEdge 25x0 (2 CPUs)

70 to 100 30 to 50

PowerEdge 64x0(4 CPUs)

100 to 2001 50 to 1001

Table 3: Recommended Number of Users Per PowerEdge Server

Note1 – Dell recommends using the PE64x0 for solutions that are very CPU intensive, and/or for solutions that want to limit the number of servers.

Storage

Application storage and user storage vary depending on the deployment, type of applications, and user requirements. Some things to remember when planning storage requirements:o All partitions should be defined as NTFS to allow for security

configuration, better performance, and fault tolerance.o Since the server will probably be configured with large amounts of

memory, the page file will need sufficient space.o The registry will need additional space to accommodate user

profiles and application settings, about 40 MB for a single CPU and about 100 MB for a 4-way processor.

o The storage subsystem is an important factor in system throughput. SCSI drives and adapters have significantly better throughput than Integrated Device Electronics (IDE). For best performance, consider using a SCSI-based Redundant Array of Independent Disk (RAID) controller.

o Dell recommends putting users home directories on separate storage (like NAS or SAN), depending on the size of the deployment.

July 2001 Page 19 Dell Enterprise Systems Group

Network

Although the network is not typically a performance bottleneck, some consideration should be given to the type of adapter used and the network configuration on the server. Since the performance of the solution will be very dependent on the network, it is important that the proper tools are in place to monitor the network performance. o The protocol used to access Terminal Server and/or MetaFrame

server is highly compressed and causes negligent loading on a network, so a high performance network NIC with fail over capabilities is recommended to improve the reliability of the server.

o Installing only one protocol on the server will free up system resources and help reduce network traffic.

Other Considerations

The sizing numbers listed in Tables 1,2, and 3 are to be used only as guidelines.

It is important to plan a pilot very carefully utilizing tools such as Citrix Resource Management Services 1.0 (part of MetaFrame XPe, it sold as 1.0 along with MetaFrame 1.8) and Windows performance monitor to better understand the way your users access and use applications. The implementer is responsible for understanding high utilization times and deploying a solution that meets the needs of the users. The most important measurements for performance monitoring are as follows:o The percentage of total processor time o Memory pages per secondo Percentage of network utilizationo Hard disk I/O rates

Depending upon users’ expectations regarding response time, and the way they access and utilize applications, the number of users per CPU will vary per deployment.

Adding memory to a server that has high resource utilization may improve the performance more than upgrading the processor speed.

When using 16-bit applications the number of users per CPU may be reduced by 20 percent, and the RAM required per user may be increased by 25 percent.

Choosing the Correct Server for the Implementation

Dell recommends the following servers because they offer excellent redundancy and expandability. The PowerEdge 25x0 server is recommended for installations that

require the flexibility to grow into server farms, since they support memory to 4 GB.

July 2001 Page 20 Dell Enterprise Systems Group

The PowerEdge 64x0 server is recommended for installations that support more CPU intensive applications as well as installations that may want to limit the number of servers, they support up to 8 GB memory.

The following systems are good choices but they offer less expandability and redundancy. The PowerEdge 3x0 server is a good choice for small MetaFrame

installations where the installed user base is not expected to grow. The PowerEdge 1550 server would also be a good choice by

offering lower cost solution with less redundancy. The PowerEdge 1400 server would also be a good choice by

offering lower cost solution with less redundancy.

For customers who want extra computing power: The PowerEdge 8450 Server is a good solution for applications

that are very CPU intensive.

Test Tools

The performance monitor, available with Windows, provides a very useful tool for measuring resource utilization through the evaluation, pilot, and deployment phases. Citrix also offers tools that will help fine tune the deployment environment:

Citrix Server Test Kit is an automated tool that can be used by administrators of Citrix Servers to configure and run various user load configurations with selected applications.

Citrix Resource Management Services is an application and systems management tool specifically for the Citrix and multi-user Windows environments. This tool provides full feature management tools for analyzing and tuning multi-user Windows deployments, and is part of the MetaFrame XPe package.

July 2001 Page 21 Dell Enterprise Systems Group

Section 6Conclusion

Deploying Windows Terminal Services and Citrix MetaFrame offer many benefits to the customer, which vary depending on the deployment environment. To maximize the benefits for the customer, the implementer will need a thorough knowledge of the deployment environment and must plan the pilot and implementation in phases so that all variables are well understood and can be considered during the pilot and deployment phases. This can minimize unexpected results and allow for easier resolution of problems during the deployment phase.

Unless the implementer or customer has specific reasons for choosing Windows Terminal Services or Citrix MetaFrame, it is a good idea to include both during the pilot phase to better understand the benefits of each environment. By using both environments, the implementer and customer will have a better understanding how each works with their solution.

Using Microsoft Terminal Services is a good way to bring Windows applications to new and existing users in the enterprise. Terminal Services provides a good solution for implementation at the workgroup level, where Terminal Services provides the required level of function. Using Windows Network Load Balancing Services, available in Windows 2000 Advanced Server and Windows 2000 Data Center Server, Terminal Services can be scaled to a larger user base. With limited enterprise level management tools, a large Terminal Services deployment may be more difficult to manage without MetaFrame.

Adding Citrix MetaFrame to the Terminal Services deployment provides additional client functions and management functions to the deployment. A thorough knowledge of MetaFrame assists the implementer in identifying MetaFrame features and functions that might improve the planned deployment. It is also important for the implementer and customer to understand the management tools provided by MetaFrame to assist the administrator in deploying, monitoring, and managing users, systems, and applications after deployment.

Many variables influence the selection of a server to be used in this type of deployment. Dell recommends the PowerEdge 64x0 and 24x0 because they offer redundancy and expandability.

The 64x0 server is a good high-end system for solutions where the customer wants to minimize the number of servers, and for solutions that are CPU intensive. Unless the applications are very CPU intensive, selecting a server with greater than 4 processors does not

July 2001 Page 22 Dell Enterprise Systems Group

usually offer much benefit since most Terminal Service solutions are bound by other resource constraints such as memory verses processing power. The 25x0 server is a good solution for solutions for implementation that support mainly typical users with a few power users.

The next paper in this series will detail information on Piloting a Terminal Services and MetaFrame deployment.

Dell and PowerEdge are trademarks of Dell Computer Corporation. Microsoft, Windows, and Windows NT are registered trademarks of Microsoft Corporation. Citrix MetaFrame and MetaFrame XP are registered trademarks of Citrix Systems, Inc. Other trademarks and trade names may be used in this document to refer to either the entities claiming the marks and names or their products. Dell disclaims proprietary interest in the marks and names of others.

©Copyright 2001 Dell Computer Corporation. All rights reserved. Reproduction in any manner whatsoever without the express written permission of Dell Computer Corporation is strictly forbidden. For more information, please contact Dell. Dell cannot be responsible for errors in typography or photography.

Information in this document is subject to change without notice.

July 2001 Page 23 Dell Enterprise Systems Group

Appendix A

Multi-User Windows

o Microsoft Windows NT Server 4.0, Terminal Server Editiono Microsoft Windows 2000 Server (Terminal Services is an install option)o Microsoft Windows 2000 Advanced Server (Terminal Services is an install

option)o Microsoft Windows 2000 Data Center Server (Terminal Services is an

install option)o CALs for client access licenses

Citrix Products

Server Productso MetaFrame XPs for Windowso MetaFrame XPa for Windows1

o MetaFrame XPe for Windows1

o MetaFrame 1.8 for Windows 2000 Serverso MetaFrame 1.8 for NT 4.0, Terminal Server Editiono MetaFrame 1.1 for UNIX Operating Systemso WinFrame 1.8o VideoFrame 1.0

Management Products o Citrix Extranet 2.0o Citrix Installation Management Services 1.0o Citrix Load Balancing Services 1.0o Citrix Resource Management Services 1.0

Portal Productso NFuse TM1.5

ICA Clientso Windowso Windows CEo DOSo Macintosho Javao OS/2o UNIXo EPOC

NOTE: 1 MetaFrame XPa & XPe includes advanced management capabilities

Appendix B

July 2001 Page 24 Dell Enterprise Systems Group

Planning Considerations before DeploymentIt is important to have a good understanding of the deployment environment before starting the planning phase. Answering the question in bold should help with the planning phase.

GeneralAre you considering a thin client deployment using Terminal Services and/or MetaFrame?

What business problem are you trying to solve?

What is the time frame for initial pilot and full deployment?

Have the resources been allocated for this project?Budget approvedProject manager and internal resources assignedProfessional systems integrator/Citrix authorized reseller

engaged

How will the system be supported once it is in place?

Security issues like dial-back, firewalls, third-party security hardware, etc.

ServersDoes the customer have a mixed computing environment of server systems?

Does the customer want to reduce the number of systems or is price performance important?

What is the planned server deployment?Small Farm – Central:Large Farm – CentralSmall Farm – DistributedSmall Farm – RemoteLarge Farm – Multiple Data CentersLarge Farm – Regional Sites

July 2001 Page 25 Dell Enterprise Systems Group

ApplicationsWhat application will the implementation need to support?

MS Office?E-Mail client?Browser?Other?

What applications will be on the client?

What application will be on the server?

ClientsWhat is the total number of users for this pilot?

What is the total number of users for this deployment?

How many concurrent users? How long will a typical connection last?

Does the customer have a mixed client-computing environment that they want to maintain?

What applications will the users be running?

Does the user require access to several applications?

Will all applications be on a single server?

What types of clients need to be supported?

What is the total amount of memory that each user will require?

Does the client require more than 256 colors for client applications?

What are the functional requirements for a remote user? Print e-mail?Print large reports to client printer?File transfer between clients and servers?

What devices will be attached to the clients? Printers? Scanners? Other?

What are the performance requirements for the clients?Time to power up system?Time to open an application?

July 2001 Page 26 Dell Enterprise Systems Group

Connectivity

Since a Terminal Services and/or MetaFrame deployment is very dependent on the network infrastructure, it is important that network-monitoring tools are available to diagnose problems. What tools does the customer have to monitor systems and network performance?

Has analysis been done on the network to assure proper configuration for the planned deployment?

What software are they planning to use for connecting to server applications?

For a WAN environment what is the connectivity for Servers and Clients?

Will applications be accessed over a WAN? What speed?Async Dial-InRemote node (Microsoft RAS or third-party remote node

software)LANWAN (leased line, Frame Relay, ISDN, ATM)Internet

What is the LAN connectivity?How much data will be transferred between client and server? Do remote clients need to print large reports remotely?

Other Considerations

What computing platforms will be used?NetWareWindowsUnixOthers

Who are the decision makers?Director of MIS: budget approval, overall responsibilityVice President of Finance: signoff on success criteria and final

OKProject Manager: "owns" the project

How will users be supported and trained?

How will we support the system once it is in place?

Disaster and recovery plansMaintenance plansCapacity planning and evaluating future needs

July 2001 Page 27 Dell Enterprise Systems Group

ReferencesCitrix MetaFrame XP Advanced Concepts

July 2001 Page 28 Dell Enterprise Systems Group

Appendix C

Feature Overview of RDP & ICAMicrosoft RDP & Citrix ICA Feature Overview

Windows NT® Server 4.0, Terminal Server Edition, (Terminal Server) and Windows® 2000 Terminal Services support both the native Microsoft Remote Desktop Protocol (RDP) as well as the Citrix Independent Computing Architecture (ICA) protocol (via the Citrix MetaFrame add-on). The following table provides an overview of many of the features available with each of these protocols, as presented by Microsoft.Note: RDP 4.0 is native to Terminal Server, and RDP 5.0 is available in Windows 2000 Terminal Services.  The protocol is backwards compatible, so both RDP 4.0 and 5.0 clients are capable of connecting to either Terminal Server or Windows 2000 Terminal Services.

Feature Description RDP4 RDP5 ICA

Clients 32-bit client for Windows® based PCs (Windows 95, Windows 98, Windows NT Workstation/Server 3.51, Windows NT Workstation/Server 4.0, Windows 2000 Professional/Server)

X X x

16-bit client for Windows for Workgroups 3.11

x x x

16bit client for older versions of Windows and the MS-DOS® operating systems

x

Windows CE-based client (Windows-based Terminal Standard and H/PC Pro)

x x1 x

UNIX client, Macintosh client, Java client x

Browser client x7 x

Transport Protocols

TCP/IP x x x

SPX, IPX, NetBEUI and Direct Asynch x

Network connection

Connect client over local area network (LAN)

x x x

Connect client over wide area network (WAN)

x x x

July 2001 Page 29 Dell Enterprise Systems Group

Connect client over dial-up, ISDN, xDSL,VPN

x x x

Dial-up connection directly to the server without using a dial-up service such as RAS

x

Audio System beeps x x x

Support for stereo Windows Audio (system and user)

X2 x

Local Printing Printing to a local printer attached to a PC client

X6 x x

Printing to a local printer attached to a WBT.

x x

Local Drive Mapping

Local drives accessible from server-based applications

x6 x3|6 x

Local Port Redirection

Redirection of server ports (LPT/COM) to local client ports

x2 x2 x

Cut and Paste Cut and paste of text/graphics between client and server

x x

Cut and paste of files/directories between client and server

x3

User-centric session access

Client remembers previous user’s logon name for each connection

x x

Connect to an active or disconnected session using a different screen resolution than the original session

x x

Connect directly to an application rather than an entire desktop

x x x

Server-based applications resize and minimize on a Windows PC similar to local applications

x

Application Publishing

Advertise server-based applications directly to client desktops

x

Load Balancing Pooling of servers behind a single server address and for increased availability

x4 x5

Remote Control Viewing of and interaction with other client sessions (“shadowing”)

X8 x x

Bitmap Caching Optionally cache display bitmaps in memory for improved performance

x x x

July 2001 Page 30 Dell Enterprise Systems Group

Optionally cache display bitmaps to disk for improved performance

x x

Encryption Multiple-level encryption for security of client communications

x x x5

Multiple-level encryption on all Windows CE-based Terminals

x x

Automatic Client Update

Administrative means for updating client connection software from the server

x9 x9 x

Pre-configured Client

Predefined client with published applications, IP addresses, server names and connections options

x x

Source: Microsoft:http://www.microsoft.com/windows2000/server/evaluation/features/rdp.asp

1 Windows CE RDP 5.0 client is available with WBT Standard 1.5. Consult your WBT manufacturer for availability. H/PC Pro RDP 5.0 client is not currently available.2 Available with third-party add-on from NCD .3 Using Windows 2000 Server Resource Kit utilities.4 Requires Windows 2000 Advanced or Datacenter Server, or 3rd party add-on from NCD or Clusterisis

.5 Requires optional Load Balancing Services or SecureICA Services in addition to Citrix MetaFrame.6 Uses Windows native networking.7 Using the Terminal Services Advanced Client Web package.8 The RDP 4.0 client can be used for remote control, but only Windows 2000 Terminal Services supports this functionality.9 Using Microsoft Systems Management Server, IntelliMirror® management technologies or 3rd party utilities in conjunction with the Terminal Services Advanced Client MSI package.

July 2001 Page 31 Dell Enterprise Systems Group

Appendix D

Contact InformationDell Resources

Dell Technical Consulting (DTC)

Dell Technology Solution Center - W. Kenneth Mason

DellWare- Brian Clifton

Third party thin client devices

Global Alliance Manager - Shirley Donahue

Server Product Manager - Peter Marrs

Technical Marketing - Fred Gonce

July 2001 Page 32 Dell Enterprise Systems Group

Appendix E

Reference MaterialCitrix MetaFrame

The best place to start is Citrix’s web site and search and read material that pertains to the planned solution. http://www.citrix.com

o Citrix MetaFrame XP Application Server for Windows: Administrator’s Guide

o Advanced Concepts for MetaFrame XP: Application Server for Windows, V.1.0

o Citrix MetaFrame for Windows Servers-Installation and Tuning Tips

o Configuration Guidelines for a Citrix Server Farmo Planning Your MetaFrame XP Deployment

Tools to help in size server for applications:o Citrix Server Test Kit: User’s Guide

Microsoft Windows 2000 Terminal Services

For additional information on Windows 2000 Terminal Services, including service architecture, client licensing, remote administration and optimization go to the following web site:http://www.microsoft.com/windows2000/technologies/terminal/default.asp

Types of Information:o Introductory Overviews o Featureso Online Demoso Downloadso Case Studieso Technical Informationo General Technical

Documentso Planning & Deployment

Guides

July 2001 Page 33 Dell Enterprise Systems Group