metaframe presentation server administrators guide

MetaFrame Presentation Server Administrators Guide

For other guides in this document set, go to the Document Center

Citrix MetaFrame Presentation Server 4.0 for Windows Citrix MetaFrame Access Suite

Copyright and Trademark Notice Information in this document is subject to change without notice. Companies, names, and data used in examples herein are fictitious unless otherwise noted. Other than printing one copy for personal use, no part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Citrix Systems, Inc. Copyright 2001-2005 Citrix Systems, Inc. All rights reserved. Citrix, ICA (Independent Computing Architecture), MetaFrame, MetaFrame XP, and Program Neighborhood are registered trademarks, and SpeedScreen is a trademark of Citrix Systems, Inc. in the United States and other countries. RSA Encryption 1996-1997 RSA Security Inc., All Rights Reserved. This product includes software developed by The Apache Software Foundation (http://www.apache.org/). Trademark Acknowledgements Adobe, Acrobat, and PostScript are trademarks or registered trademarks of Adobe Systems Incorporated in the U.S. and/or other countries. Apple, LaserWriter, Mac, Macintosh, Mac OS, and Power Mac are registered trademarks or trademarks of Apple Computer Inc. DB2, Tivoli, and NetView are registered trademarks, and PowerPC is a trademark of International Business Machines Corp. in the U.S. and other countries. HP OpenView is a trademark of the Hewlett-Packard Company. Java, Sun, and SunOS are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. Solaris is a registered trademark of Sun Microsystems, Inc. Sun Microsystems, Inc has not tested or approved this product. Portions of this software are based in part on the work of the Independent JPEG Group. Portions of this software contain imaging code owned and copyrighted by Pegasus Imaging Corporation, Tampa, FL. All rights reserved. Macromedia and Flash are trademarks or registered trademarks of Macromedia, Inc. in the United States and/or other countries. Microsoft, MS-DOS, Windows, Windows Media, Windows Server, Windows NT, Win32, Outlook, ActiveX, Active Directory, and DirectShow are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Netscape and Netscape Navigator are registered trademarks of Netscape Communications Corp. in the U.S. and other countries. Novell Directory Services, NDS, and NetWare are registered trademarks of Novell, Inc. in the United States and other countries. Novell Client is a trademark of Novell, Inc. RealOne is a trademark of RealNetworks, Inc. SpeechMike is a trademark of Koninklijke Philips Electronics N.V. Unicenter is a registered trademark of Computer Associates International, Inc. UNIX is a registered trademark of The Open Group. All other trademarks and registered trademarks are the property of their owners. Document Code: 2/21/05 (MM)

Go to Document Center

Contents 3

ContentsChapter 1 Chapter 2 Welcome Designing Server FarmsOverview of Server Farms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Independent Management Architecture (IMA) . . . . . . . . . . . . . . . . . . . . . . . . . 16 Independent Computing Architecture (ICA) . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Centralizing or Distributing Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Deciding How Many Farms to Deploy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Configuring Zones and Data Collectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Zone Data Collectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Server Farm Deployment Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Small Farm Central Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Large Farm Central Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Small Farm Distributed Sites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Small Farm Remote Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Large Farm Multiple Data Centers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Large Farm Regional Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Chapter 3

The Farm Data StoreViewing Data Store Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Choosing a Database for the Data Store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 System Sizing for the Data Store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Suggested Hardware Configurations for the Data Store . . . . . . . . . . . . . . . . . . 42 Connecting Directly or Indirectly to the Data Store . . . . . . . . . . . . . . . . . . . . . 44 Using a RAID Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Using Replicated Data Store Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Data Store Database Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Microsoft Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Microsoft SQL Server 2000 Desktop Engine (MSDE) . . . . . . . . . . . . . . . . . . . 50 Microsoft SQL Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 IBM DB2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Working with the Local Host Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

4



Chapter 4

Planning for DeploymentSystem Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 System Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 System Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Sizing Systems for MetaFrame Presentation Server . . . . . . . . . . . . . . . . . . . . . 72 Network Configuration and Account Authority Issues. . . . . . . . . . . . . . . . . . . . . . 75 General Configuration Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Recommendations for Active Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 User Access to Applications and Printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Active Directory Security Model and Restrictions . . . . . . . . . . . . . . . . . . . . . . 77 Supporting Novell Directory Service Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Setting up Support for NDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Configuring Printer Autocreation in NDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Changing Domain Trust Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Configuring MetaFrame Administrator Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . 86 Planning for Client and Server Communications . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Linking Clients and Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Configuring ICA Browsing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Communicating with the Citrix XML Service. . . . . . . . . . . . . . . . . . . . . . . . . . 93 Using DNS Address Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Configuring Network Firewalls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Server Farm Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Changing Server Drive Letters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Using Smart Cards with MetaFrame Presentation Server. . . . . . . . . . . . . . . . . . . 103 Software Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Configuring the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Configuring the Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Compatibility with MetaFrame Conferencing Manager . . . . . . . . . . . . . . . . . . . . 106

Chapter 5

Deploying MetaFrame Presentation ServerCreating a New Server Farm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Task Summary for Creating a New Server Farm. . . . . . . . . . . . . . . . . . . . . . . 108 Remapping Server Drive Letters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Creating the Farm Data Store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110


Contents 5

Migrating to MetaFrame Presentation Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Upgrading from Versions Prior to MetaFrame XP Feature Release 3 . . . . . . 112 Migrating from MetaFrame Versions 1.0 and 1.8 . . . . . . . . . . . . . . . . . . . . . . 113 Migrating from MetaFrame XP, Feature Release 3, and MetaFrame Presentation Server 3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Installing or Upgrading Individual Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Creating a Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Using Autorun. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Using the Windows Installer Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Choosing Options during Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Installing MetaFrame Presentation Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Installing the Access Suite Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Installing the Presentation Server Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Installing the Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Installing the Document Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Installing Client Software on the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Unattended Setup of MetaFrame Presentation Server. . . . . . . . . . . . . . . . . . . . . . 140 Applying Transforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Creating an Answer File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Performing an Unattended Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Cloning Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Uninstalling MetaFrame Presentation Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Chapter 6

Managing Servers and FarmsManagement Tools Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Choosing Which Console to Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

6



Management Console for the MetaFrame Access Suite . . . . . . . . . . . . . . . . . . . . 149 Users and Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 The Access Suite Console User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 Viewing Applications, Servers, and Zones in Multiple Farms . . . . . . . . . . . . 152 Customizing Your Displays Using My Views. . . . . . . . . . . . . . . . . . . . . . . . . 152 Managing Sessions across Multiple Farms . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Monitoring the Performance of Server Farms . . . . . . . . . . . . . . . . . . . . . . . . . 154 Troubleshooting Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Creating Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Configuring Application Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Viewing Citrix Hotfix Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Starting the Access Suite Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Finding Items in Your Deployment Using Discovery . . . . . . . . . . . . . . . . . . . 156 Management Console for MetaFrame Presentation Server. . . . . . . . . . . . . . . . . . 157

Chapter 7

Securing Your FarmsCreating MetaFrame Administrator Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Overview of Security Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Overview - Deploying SSL Relay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Overview - Deploying the Secure Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Overview - Deploying ICA Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Setting up Citrix SSL Relay. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Deploying SSL Relay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Configuring Kerberos Logon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Managing the Secure Ticket Authority (STA) . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Viewing Secure Ticket Authority Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Identifying Entries in the STA Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Chapter 8

Configuring ICA ConnectionsOverview of ICA Connections and Sessions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Setting Up ICA Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Using the Citrix Connection Configuration Utility . . . . . . . . . . . . . . . . . . . . . 188 Adding ICA Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Adding Asynchronous ICA Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Configuring Session Settings for Clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Precedence of Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192


Contents 7

Configuring ICA Connection Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 Configuring Modem Callback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 Configuring Direct Cable Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Configuring Advanced ICA Connection Options . . . . . . . . . . . . . . . . . . . . . . 199 Restricting Connections to Published Applications. . . . . . . . . . . . . . . . . . . . . 200 Configuring ICA Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Using Shadowing to Monitor ICA Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Enabling Shadowing on a Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Configuring ICA Connections for Shadowing. . . . . . . . . . . . . . . . . . . . . . . . . 202 Configuring Audio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 Step 1 - Configuring Audio for Published Applications . . . . . . . . . . . . . . . . . 204 Step 2 - Configuring Audio Related Policy Rules . . . . . . . . . . . . . . . . . . . . . . 204 Optimizing Session Responsiveness for Users . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Optimizing Keyboard and Mouse Click Responsiveness . . . . . . . . . . . . . . . . 208 Optimizing Web Pages and Email . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 Optimizing Audio and Video Playback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 Optimizing Macromedia Flash Animations . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 Optimizing Throughput of Image Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Configuring Client Device Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 Options for Client Device Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 Client Drive Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 Client Printer Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 Client Serial Port Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 Client Audio Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 Granting Users Execute Permission on Mapped Client Drives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

Chapter 9

Deploying Client Software to UsersChoosing a Client Deployment Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 Delivering Applications to Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Determining the Scope of Client Deployment . . . . . . . . . . . . . . . . . . . . . . . . . 222 Using the MetaFrame Presentation Server Components CD . . . . . . . . . . . . . . . . 223 Installing a Pass-Through Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Using Remote Desktop Web Connection Software. . . . . . . . . . . . . . . . . . . . . 223 ICA Client Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

8



Deploying Client Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 Using the Components CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 Using the Client Packager for Client Deployment. . . . . . . . . . . . . . . . . . . . . . 228 Deploying Client Software over the Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 Client Deployment Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 Manufacturing Enterprise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 Application Service Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 Insurance Company . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Chapter 10

Publishing Applications, Content, and DesktopsDeciding How Users Access Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 Managing User Access through Content Redirection . . . . . . . . . . . . . . . . . . . . . . 236 Publishing Applications and Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 User Access to Published Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 Administrative Control of Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 Using Published Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 Determining Whether to Provide Virtual IP Addresses or a Virtual Loopback Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 Determining to Isolate Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 Configuring User Access to Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 Procedures for Publishing Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 Associating Published Applications with File Types . . . . . . . . . . . . . . . . . . . 244 Passing Parameters to Published Applications. . . . . . . . . . . . . . . . . . . . . . . . . 247 Creating Files for Application Launching and Embedding . . . . . . . . . . . . . . . 248 Providing the Client IP Address to an Application . . . . . . . . . . . . . . . . . . . . . . . . 249 Providing Virtual IP Address Ranges to Sessions. . . . . . . . . . . . . . . . . . . . . . . . . 250 Providing Virtual Loopback Addresses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 Enabling Applications for Use with Virtual IP Addresses or Virtual Loopback Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 Controlling and Monitoring Virtual IP Addresses and Virtual Loopback on Individual Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 Isolating Published Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 Enabling and Disabling Isolation Environments . . . . . . . . . . . . . . . . . . . . . . . 254 Creating an Isolation Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 Configuring an Isolation Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 Using an Isolation Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 Deleting Isolation Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258 Uninstalling Applications Installed into an Isolation Environment. . . . . . . . . 259


Contents 9

Removing Published Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260 Configuring Content Redirection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260 Redirecting Content from Client to Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . 260 Redirecting Content from Server to Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . 261 Publishing Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263 Publishing Content to be Opened with Applications Published on Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263 Publishing Content to be Opened with Applications on Local Client Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 Publishing Content on Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265 Setting CPU Priority Levels for Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267 Assigning CPU Priority Levels to Applications . . . . . . . . . . . . . . . . . . . . . . . 268

Chapter 11

Managing Users and SessionsControlling User Logons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271 Controlling User Logon Look and Feel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272 Providing Users with Workspace Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273 Controlling User Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 Limiting Total Connections in a Server Farm . . . . . . . . . . . . . . . . . . . . . . . . . 276 Limiting Application Instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 Configuring Connection Control Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 Logging Connection Control Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 Monitoring and Managing Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 Viewing Information about Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 Using Session Management Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281 Managing Session Consistency and Reliability. . . . . . . . . . . . . . . . . . . . . . . . . . . 284 Leveraging Session Reliability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284 Leveraging Automatic Client Reconnection . . . . . . . . . . . . . . . . . . . . . . . . . . 285 Creating and Applying Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289 Creating Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290 Configuring Policy Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291 Migrating Policies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294 Overriding Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295 Creating Exceptions to Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295 Prioritizing Policies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295 Applying a Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 Searching for Policies and Viewing the Results of Multiple Policies . . . . . . . 298 Enabling PDA Synchronization Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299

10



Controlling Use of TWAIN Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300 Managing CPU Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300 About CPU Utilization Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300 Controlling CPU Utilization Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . 301 Managing Virtual Memory Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301 About Memory Utilization Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301 Controlling Memory Utilization Management. . . . . . . . . . . . . . . . . . . . . . . . . 302 Scheduling Virtual Memory Optimization. . . . . . . . . . . . . . . . . . . . . . . . . . . . 303 Excluding Applications from Memory Optimization . . . . . . . . . . . . . . . . . . . 304 Shadowing Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 Configuring User-to-User Shadowing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 Monitoring Performance of Sessions and Servers. . . . . . . . . . . . . . . . . . . . . . . . . 308

Chapter 12

Managing PrintersOverview of Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311 Printing in ICA Sessions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313 Printing Configuration Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313 Printer Management Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315 Using the Printer Management Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316 Using the Servers Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319 Setting Up Network Printers for Client Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321 Installing and Replicating Printer Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321 Setting Up Automatic Replication of Printer Drivers . . . . . . . . . . . . . . . . . . . 322 Assigning Network Printers to Users through Policies . . . . . . . . . . . . . . . . . . . . . 323 Mapping Printer Drivers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323 Managing Drivers for Autocreated Printers . . . . . . . . . . . . . . . . . . . . . . . . . . . 324 Configuring Autocreation of Client Printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325 Autocreation for DOS and Windows CE Clients. . . . . . . . . . . . . . . . . . . . . . . 325 Autocreation and Citrix Connection Configuration. . . . . . . . . . . . . . . . . . . . . 325 Overriding Default Settings for Client Printers . . . . . . . . . . . . . . . . . . . . . . . . 326 Using MetaFrame Presentation Server Universal Printing . . . . . . . . . . . . . . . . . . 328 Specifying Printer Drivers for Client Printing. . . . . . . . . . . . . . . . . . . . . . . . . . . . 329 Limiting Printing Bandwidth in Client Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . 330 Limiting Printing Bandwidth through Policies . . . . . . . . . . . . . . . . . . . . . . . . 330 Limiting Printing Bandwidth through Server Settings . . . . . . . . . . . . . . . . . . 331


Contents 11

Appendix A Appendix B

MetaFrame Presentation Server Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333 Customizing Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389 Creating Transforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390 Creating Administrative Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396 Setup Property Names and Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397

Appendix C

Performance Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413 IMA Networking Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413 MetaFrame Presentation Server Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414 ICA Session Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417 Secure Ticket Authority (STA) Performance Counters . . . . . . . . . . . . . . . . . . . . 420

Appendix D

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429


CHAPTER 1

Welcome

The MetaFrame Presentation Server suite of products provides integrated management capabilities for system administrators, along with ease of use and productivity enhancements for users who access applications using MetaFrame Presentation Server Clients. Important Before you install MetaFrame Presentation Server, read the Readme file, located in the Documentation directory of the product CD. For information about new and important features, see Getting Started with MetaFrame Presentation Server. Citrix provides a variety of information resources online, including a complete product documentation library, documentation updates, and technical articles on the Citrix Web site at http://www.citrix.com. This Administrators Guide is part of the MetaFrame Presentation Server documentation set. The documentation set includes online guides that correspond to different features of MetaFrame Presentation Server. Online documentation is provided as Adobe Portable Document Format (PDF) files. Use the Document Center to access the complete set of online guides. The Document Center provides a single point of access to the documentation that enables you to go straight to the section you need. The Document Center includes: A list of common tasks and a link to each item of documentation. A search function that covers all the PDF guides. This is useful when you need to consult a number of different guides. Cross-references among documents. You can move among documents as often as you need using the links to other guides and the links to the Document Center.

14



Important To view, search, and print the PDF documentation, you need Adobe Acrobat Reader 5.0.5 or later with Search. You can download Adobe Reader for free from the Adobe Systems Web site at http://www.adobe.com/. If you prefer to access the guides without using the Document Center, you can navigate to the component PDF files using Windows Explorer. If you prefer to use printed documentation, you can also print each guide from Adobe Reader. More information about Citrix documentation, and details about how to obtain further information and support, is included in Getting Started with MetaFrame Presentation Server.


CHAPTER 2

Designing Server Farms

Read this chapter to understand how server farms are structured and how you should design farms to provide users with easy access to applications and resources. This chapter discusses the following topics you should consider when designing a farm: Overview of server farms. Farms are the central unit through which to organize and manage MetaFrame Presentation Server. Centralizing or distributing servers. How you organize server location is largely driven by the location of your users, the location of users applications and data, and your network environment. There are advantages to either centralizing servers at one site or distributing them among multiple sites. Deciding how many farms to deploy. Although most deployments use a single farm, you can consider deploying separate farms for remote sites or environments with tight firewall security between sites. Planning zones in farms. You can use zones to group servers by subnet or location, control communication, enhance performance, or discourage bottlenecks between groups of servers within the farm. Servers in a zone can communicate directly with one another. Server farm deployment scenarios. You can review and draw from these six common farm configurations when designing your deployment. The scenarios range from a small single-zone farm centralized in one location to a large multizone farm with regional sites.

For information about configuring the most appropriate licensing deployment for your farm, see the MetaFrame Access Suite Licensing Guide.

16



Overview of Server FarmsUsers run their applications on servers that are grouped into server farms. Server farms are groups of servers running MetaFrame Presentation Server that you can manage as a unit, enabling you to configure features and settings for the entire farm rather than configuring each server individually. For example, when you publish the applications or resources you want to make available to users, you do so at the farm level, establishing configuration settings that pertain to all instances of the application running in the farm. Published applications are the applications that you make available to users to run on servers in the farm. Servers in a farm share a network connection and a single data store of the farms configuration information. Your farm design must include creating a data store and connecting each server in the farm to it. For more information about data stores, see The Farm Data Store on page 39. Two main architectural elements of MetaFrame Presentation Server enable you to establish the on-demand enterprise, where users access published resources easily and with any client device. Keep these elements, described in the following topics, in mind when designing farms.

Independent Management Architecture (IMA)Independent Management Architecture (IMA) provides the framework for server communications and is the management foundation for MetaFrame Presentation Server. IMA is a centralized management service comprised of a collection of core subsystems that define and control the execution of products in a server farm. IMA enables servers to be arbitrarily grouped into server farms that do not depend on the physical locations of the servers or whether the servers are on different network subnets. IMA runs on all servers in the farm. IMA subsystems communicate through messages passed by the IMA Service through default TCP ports 2512 and 2513. The IMA Service starts automatically when a server is started. The IMA Service can be manually started or stopped through the operating system Services utility.

Independent Computing Architecture (ICA)The Independent Computing Architecture (ICA) is the communication protocol by which servers and client devices exchange data in a server environment. ICA is optimized to enhance the delivery and performance of this exchange, even on lowbandwidth connections.


Chapter 2 Designing Server Farms

17

The ICA protocol transports an applications screens from the server it is running on to the users client device, and returns the users input to the application on the server. As an application runs on a server, MetaFrame Presentation Server intercepts the applications display data and uses the ICA protocol to send this data (on standard network protocols) to the client software running on the users client device. When the user types on the keyboard or moves and clicks the mouse, the client software sends this data to the application on the server. ICA requires minimal client workstation capabilities and includes error detection and recovery, encryption, and data compression. For more information about client software, see Deploying Client Software to Users on page 219. A server farm is a grouping of servers running MetaFrame Presentation Server that you can manage as a unit, similar in principle to a network domain. When designing server farms, keep in mind the goal of providing users with the fastest possible application access while achieving the degree of centralized administration and network security that you need.

Centralizing or Distributing ServersThe existing network layout and the location of administrators, users, applications, and data all influence how you organize servers. When users and data sources are separated by a high latency or Wide Area Network (WAN) connection, users typically experience better performance if the servers hosting the application are placed near the data source. For example, if users in London need an application that accesses a data source in Brussels, place the servers running the application in Brussels rather than near the users in London. Locating servers running MetaFrame Presentation Server close to data sources leverages the speed of the ICA protocol and enhances the user experience across high latency connections.

18



For enterprises with geographically dispersed sites, there are trade-offs to consider between centralizing servers or scattering them with the applications or data centers. The following table outlines some of these trade-offs.Servers centralized at one site Advantages: Centralized server administration and support. Centralized application management. Servers distributed across multiple sites Advantages: Enhanced business continuity and redundancy; if one site loses connection, it does not affect all application access. When data is maintained at different sites, placing servers at those sites provides users with local access to the data. Sites can own and control their own servers. Disadvantages: If users need access to multiple sites, you may need to coordinate and replicate domains, trusts, user profiles, and data. Sites may need added local administration and support. Server-to-server communication crosses the WAN.

Disadvantages: Single point of failure; if the site loses connection, users have no alternative access. Access to data might be slow if an application must traverse a WAN link to the data.

In MetaFrame Presentation Server you use farms and zones to organize the application environment and administer servers. The next two sections discuss planning for farms and zones.



19

Deciding How Many Farms to DeployBefore deploying MetaFrame Presentation Server you must decide whether to implement a single farm or multiple farms. This decision is influenced by your individual environment, including such factors as: Location and needs of the end users Geographical layout of the enterprise Capabilities of the farms data store database Network congestion Hardware capability Enterprise security policies concerning server communications

There is no exact formula that determines what number of farms is ideal, but there are some general guidelines that can help you make this decision. Deploying a Single Farm. In general, a single farm meets the needs of most deployments. For very large deployments with, for example, thousands of servers, breaking the environment into multiple farms can increase performance. A significant benefit to deploying a single farm is needing only one data store database. For more information about data stores, see Choosing a Database for the Data Store on page 40. Deploying Multiple Farms. You typically consider using multiple farms when you have geographically dispersed data centers that can support their own data store database or you do not want communication between servers within the farm to cross a firewall or WAN.

20



The following table compares how single and multiple farm deployments relate to a few of the important factors you must consider when planning the server environment:Farm Element Data Store Data Store Replication Load Balancing Firewall Traversal Single Farm The farm has one data store. Citrix recommends that you replicate the data store to remote sites when using one farm in a WAN environment. You can load balance an application across the farm. If the farm spans multiple sites, firewall ports must be open for server-to-server communication. Data store information is synchronized with member servers through notifications and queries. When a farm has multiple zones, data collectors are used to communicate dynamic information such as logons and application use across the farm Centralizing administration and support may be easier for a single farm. You can monitor and configure the farm from a single Management Console and need to log on to only one farm to do so. Multiple Farms Each farm must have a data store. If each remote site is a farm with its own data store, there is no need for data store replication. You cannot load balance an application across servers in different farms. Site-based farms eliminate the need to open firewall ports for server-to-server communication. Multiple farms may improve performance over a single farm when server-to-server traffic crosses a WAN link or when the farm is very large.

Server-to-server Communication

Administration and Support Management Consoles

You can decentralize administration and support if you want sites to have control and ownership. You can monitor and configure multiple farms from the Access Suite Console. Communicating with multiple farms from the console requires logging on to multiple servers.

You can use zones to organize servers within a farm. The next section provides information about setting up zones.



21

Configuring Zones and Data CollectorsYou can use zones to enhance a farm's performance and organization. A zone is a grouping of servers that share a common zone data collector. A zone data collector is a server that manages dynamic information about the servers in the zone. Each farm has at least one zone. By default, all servers in a farm that are on the same network subnet belong to the same zone. Use Zones in the left pane of a farms Properties page to view the servers that belong to each zone. To change the membership of a server from one zone to another, select the server from the list of servers in the zone and move it to another zone. Important If you change a servers zone membership (move the server to another zone), incorrect information can appear in the Presentation Server Console until the server sends updates to the zone data collector. To ensure data synchronization, restart a server after you move it to another zone. Zones are designed to enhance the performance of a farm by allowing geographically related servers to be grouped together, whether they are connected to the same network subnet or not. If all the servers in a farm are in one location, you can configure the farm with a single zone without causing slower performance or making the farm more difficult to manage. If you manage an enterprise farm with servers in different geographic regions, you can create zones based on the location of the servers. This can improve performance and allow you to more efficiently manage the farm.

Zone Data CollectorsZone data collectors are communication gateways between zones in farms that have more than one zone. Zone data collectors communicate information used by MetaFrame Presentation Server to list available applications for users and, when users open an application, to locate the most appropriate server on which to run the application. Each zone in a farm contains one server that is designated as the zone data collector. Zone data collectors store dynamic information about the servers, published applications, server load, and user sessions in their zone. The zone data collector tracks, for example, which applications are available and how many sessions are running on each server in the zone.

22



This diagram shows a server farm with two zones connected by a WAN link. Only the zone data collector in each zone communicates over the WAN link. Individual servers communicate over LANs primarily with their zone data collector.

When resolving a users application request to the least-loaded server in the farm, a zone data collector queries the other zone data collectors for the information it needs to identify the server with the lightest load. Only zone data collectors send messages between zones, reducing communication traffic in the farm because every server does not need to communicate with every other server. If you have a large or geographically diverse farm, you may be able to enhance performance by organizing servers into zones. Note Beginning with MetaFrame Presentation Server 3.0, zone data collectors no longer automatically send updates about server loads in their zone to other zone data collectors. This change in communication is designed to reduce network traffic between zones. Zone data collectors no longer maintain load information for all servers in the farm as they did in earlier releases. The zone data collector now maintains load information only for the servers in its own zone. This behavior is especially beneficial in large farms. To ensure users are efficiently routed to the least loaded server in the server farm, you can set farm properties to share load information across zones. Exchanging server load information should be limited to the following conditions: The bandwidth capacity between zones is not limited The Zone preference and failover policy rule is not a consideration



23

To configure the sharing of load information across zones 1. In the left pane of farm Properties, choose Zones. 2. In the right pane, select Share load information across zones. Selecting to share load information across zones can result in increased network traffic because every change in server load is communicated to all data collectors across all zones. Connection requests are routed to the least loaded server in the server farm, even a server located across a WAN, unless a preferred order is established using the Zone preference and failover policy rule. When you establish a preferred connection order, the zone data collectors query the preferred zones in the order you set. To keep data exchanges between zones to a minimum when zones are located across WANs, thus reducing network traffic: Do not enable sharing load information across zones Set up a preferred zone connection order using the Zone preference and failover policy rule Configure a Primary Group zone in this policy rule so that incoming connection requests from users in a particular geographic location are always routed first to the zone that includes that geographic location

Tip To reduce network traffic in large farms with multiple zones, Citrix recommends that you use the Zone Preference and Failover policy rule to direct users requests for applications to preferred zones within the farm. For more information about Zone Preference and Failover, see Directing User Connections to Preferred Zones on page 27. Citrix recommends that you maintain all servers in a farm at the most recent release level of MetaFrame Presentation Server. If you find that you need to run different release levels of MetaFrame Presentation Server in your server farm on a temporary basis, configure a server running the latest release as the zones data collector.

Sizing ZonesDesign zones to enhance farm performance when enumerating or opening applications for users. The number of servers you can place in one zone depends largely on the hardware of the zone data collector and the amount of farm activity. Factors that can influence zone size include: How many users connect to the farm How many users log on simultaneously

24



How long the average user stays logged on to a session (a single daily session or repeated short sessions) How many published applications are load-balanced among servers

Routinely monitor the CPU and memory usage on the zone data collector to ensure that it is not being overloaded with requests, especially after adding new applications or additional users to the farm. For most deployments, limit a zone to a group of servers that are located in a single data center and connected by low latency links. Tip Citrix recommends that you maintain as few zones as possible while still being able to complete application enumeration requests and resolutions in a timely manner. Creating too many zones can decrease performance in a farm, resulting in high network bandwidth consumption and decreased performance of the zone data collectors. Zones can typically support more than 500 servers. When sizing zones, start with 500 servers per zone and then monitor the IMA Work Item Queue Ready Count counter on the zone data collector to determine how much activity it can support. Tip To find out if a zone data collector is overloaded, you can monitor the server for the number of work items that are ready for execution. As a zone data collector becomes overloaded, work items on the server begin to pile up and stand in queue for execution. You can check the Work Item Queue Ready Count counter from the Citrix MetaFrame performance object in Windows Performance Monitor. If this counter rises above zero for a steady length of time, you should be concerned about the load on the data collector. For more information about monitoring performance, see Monitoring Performance of Sessions and Servers on page 308. If users experience delays when their available applications are being enumerated or when they open an application, or if reports are being generated slowly, the zone data collector may be overloaded. Consider taking the following actions to reduce the load on the zone data collector: Increase the CPU power of the zone data collector Dedicate the zone data collector to handling zone information and users requests for applications, but not running published applications As a last resort, divide the current zone into two zones



25

If you are installing MetaFrame Presentation Server on servers that reside on multiple subnets in the same zone, do not use the default zone name presented to you during MetaFrame Presentation Server Setup, because the default zone name is based on the subnet of the server joining the farm. If you do not change the zone name when you install MetaFrame, you can change it in the farms Properties dialog box using the Presentation Server Console.

Configuring Data Collectors for Large ZonesIf you are using large zones that have more than 512 servers, Citrix recommends the following: Dedicate a server to being the zone data collector Dedicate a server to being the backup for the zone data collector Both the zone data collector and its backup are the latest generation servers with at least two processors Add the registry key entry MaxHostAddressCacheEntries to both servers

To configure a zone for more than 512 servers CAUTION Using Registry Editor incorrectly can cause serious problems that can require you to reinstall the operating system. Citrix cannot guarantee that problems resulting from incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Make sure you back up the registry before making changes to it. 1. Add the following entry to the registry \\HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\IMA\ Runtime\MaxHostAddressCacheEntries (DWORD) 2. Set the value of MaxHostAddressCacheEntries to a number greater than the number of servers you are planning to put in the zone but no higher than necessary, because MetaFrame Presentation Server uses this number for memory management. Note Increasing the value of MaxHostAddressCacheEntries higher than necessary can negatively impact performance. Increasing this value does not improve data collector performance. 3. Restart the IMA Service on the server.

26



Configuring the Election of Zone Data CollectorsA zone elects, or selects, a zone data collector if a new server joins the zone or if the current data collector becomes unavailable. A zone data collector becomes unavailable if the server hosting it fails or is disconnected from the network, or if you move the server to another zone. Zones elect a new zone data collector using a preference ranking of the servers in the zone. You can set this preference ranking using Zones in the left pane of a farms Properties page. The preference levels, in order from highest to lowest preference, are: Most Preferred Preferred Default Preference Not Preferred When the zone elects a new data collector, it tries to select a server from the Most Preferred level. If no servers are available at this level, the zone selects a server from the Preferred level, and so on. The first server added to a zone is set to Most Preferred and becomes the zones initial data collector. All other servers are set to Default Preference. You can designate a specific server to become the zone data collector. For example, you may want to switch the zone data collector to a server you just added to the farm because the new server has more powerful CPU capabilities. To designate a specific server as the zone data collector, set the election preference for the server to Most Preferred and set all other servers in the zone at a lower election preference. Assign servers that you do not want to become the zone data collector to Not Preferred. If a zone spans multiple sites and the network link goes down between the sites, each site elects a zone data collector. The zone data collector does not need a connection to the farm data store to function. This allows user connections to continue to work during the interruption. When the network connection is restored, the zone returns to having one elected data collector. When a new zone data collector is elected, it gathers fresh data from the servers in the zone. Zone data collectors do not copy or back up data to or from other servers; they gather and provide only dynamic information about servers in the zone.



27

Dedicating a Server as Zone Data CollectorIn large farms and enterprise networks with high client traffic, you can reduce the possibility of data collector performance issues by using dedicated data collectors. You can do this by setting up data collectors on servers that run MetaFrame Presentation Server but do not host applications. When you publish applications, do not include the data collector among the servers to run the applications. In general, if users experience slow connection times due to high CPU utilization on the data collector, consider dedicating a server to act solely as the zone data collector.

Directing User Connections to Preferred ZonesIf your users connect through the Web Interface or the Program Neighborhood Agent, you can configure policies in MetaFrame Presentation Server to transparently direct users to launch applications in preferred zones. The Zone Preference and Failover policy rule enables you to set preferred zones and establish failover to other zones when the preferred servers are unavailable. Citrix recommends using this feature in farms with multiple zones dispersed geographically. Routing users to connect to servers in their own zone can reduce traffic across high latency connections. To use Zone Preference and Failover, apply it as a rule in a policy. For more information about configuring policies, see Creating and Applying Policies on page 289.

Setting Connection Order for ZonesMetaFrame Presentation Server directs user connections to zones according to the connection order assigned to each zone in the Zone Preference and Failover policy rule. The connection order levels, in order of preference, are: Primary Group. Use for zones to which you want connections directed first. Backup Group. Use for zones to which you want connections directed if the application is not available in zones assigned as the Primary Group. There are ten levels of backup groups, from 1 to 10. Backup Group 1 has highest preference among the backup groups. No Preference. Use for zones that users are directed to after Backup Group 10. Do Not Connect. Use for zones to which you do not want users to connect.

You can set connection order preferences only in the Zone Preference and Failover rule of a policy.

28



Configuring the Zone Preference and Failover RuleYou can configure zone preference and failover in a policys properties. To configure zone preference and failover in a policy 1. In the Presentation Server Console, select the Policies node. 2. On the Contents tab, select the policy for which you want to configure zone preference and failover. 3. From the Actions menu, choose Properties. 4. In the Properties dialog box, open User Workspace > Connections and select Zone Preference and Failover. 5. Enable Zone Preference and Failover and assign a connection order to each zone. When you enable zone preference and failover, it takes precedence when in conflict with session sharing. When a user launches an application, the zone data collector first queries the zones in the users Primary Group to locate the server in that group with the smallest load. If the application is not available in the Primary Group zones, the data collector queries the zones in Backup Group 1 and so on, following the connection order you set. For example, if you have users who open applications in a farm that spans zones in Vancouver, Seattle, and Hong Kong, you can create a policy for users at each site. Set the Zone Preference and Failover rule on each user groups policy to connect to their local zone and set one of the remote sites as Backup Group 1 and the other remote site as Backup Group 2. For the Vancouver user group, assign the Vancouver zone as the Primary Group, the Seattle zone as Backup Group 1, and the Hong Kong zone as Backup Group 2. This configuration ensures that users in Vancouver launch an application on a server in Vancouver. Only if the application is not available in Vancouver does the data collector query across the WAN to find the application in Seattle. Likewise, the data collector queries the Hong Kong zone only if the application is not available in both Vancouver and Seattle. Tip To ensure the most efficient use of network traffic between zone data collectors, do not place zones at the same connection order if they have a high latency link between them. The data collector queries all zones in the same connection order simultaneously. Assign a different connection order to zones at each remote site. If you do not enable Zone Preference and Failover, users are directed by default to the server in the farm with the lightest load, even if that server is in another zone across a WAN link.



29

To use Zone Preference and Failover in an environment with servers running earlier releases of MetaFrame Presentation Server: Make sure that the zone data collector is a server running MetaFrame Presentation Server 4.0 or later Run the Citrix XML Service on servers with MetaFrame Presentation Server 4.0 or later Make sure that the Web Interface is configured to communicate with the servers in the farm that are running MetaFrame Presentation Server 4.0 Use only the most recent version of the Presentation Server Console to create, rename, or remove zones

30



Server Farm Deployment ScenariosRead the following sections for information about common server farm infrastructures and recommendations from Citrix for each one. The findings presented for these scenarios are based on results from extensive testing in Citrix labs.

Small Farm Central LocationThis scenario describes a simple single farm environment where all servers reside in one location and are configured as follows:Servers Zone(s) Physical Sites Data Store Connectivity 1-100 1 1 Microsoft Access, MSDE, Microsoft SQL Server, IBM DB2, or Oracle 10 Mbps or higher (LAN)

This diagram shows a small farm in a central location. The farm contains a data store, a single zone, one data collector for the zone, and multiple farm member servers.



31

Citrix recommends the following for small farms in a central location: Dedicate a data collector for zones with more than 50 servers If using Access or MSDE for the farms data store, you can consider using the same server to act as the data collector and also host the data store

Large Farm Central LocationThis scenario describes a larger, but only slightly more complex, single farm environment where all servers reside in one location and are configured as follows:Servers Zone(s) Physical Sites Data Store Connectivity 100+ 1 zone per 300+ servers 1 Microsoft SQL Server, Oracle, or IBM DB2 10Mbps or higher (switched 100Mbps is recommended)

32



This diagram shows a large farm in a central location. The farm contains a data store and four zones. Each zone consists of a data collector and multiple farm member servers.

Citrix recommends the following for large farms in a central location: Dedicate a data collector for zones with more than 50 servers. With extremely large farms, using replicated Microsoft SQL Server databases, replicated Oracle databases, or Oracle RAC can improve performance and prevent a bottleneck at the data store. If replication is used with IBM DB2 databases, you must configure it for read-only and all changes must be made on the master database. Do not exceed 25 zones in a single farm. Scale zones to maximum capacity before introducing more zones.



33

Small Farm Distributed SitesThis scenario describes a small single farm environment where servers reside in a few locations as follows:Servers Zone(s) Physical Sites Data Store Connectivity 1-100 (evenly distributed at a few physical locations) 1-4 2-4 Microsoft Access, MSDE, Microsoft SQL Server, IBM DB2, or Oracle 512Kbps or higher to a central site or between all locations

This diagram shows a small farm with distributed server locations. The farm consists of a single zone distributed across four locations. Location 1 includes the data store, data collector, and multiple farm member servers. Each of the other locations contain farm member servers.

Citrix recommends the following for small farms in distributed sites:

34



Use a single zone if all distributed sites have a connection to a central site, the frequency of users connecting is limited, and the remote sites are in a single zone and each have fewer than twenty-five servers. If you are using multiple zones, provide all sites hosting a zone with a direct link to all other zone sites. Otherwise, all locations need connectivity to a central site where the zone data collector is located. Restart servers only when WAN links are at low utilization. If the majority of the servers in the farm reside at one location and the remote sites have very few servers, use a single zone.

Small Farm Remote SitesThis scenario describes a small single farm environment where small groups of 2-5 servers are distributed in multiple locations.Servers Zone(s) Physical Sites Data Store Connectivity 1-100 (2-5 at each site to support local use) 1 2+ Microsoft Access, MSDE, Microsoft SQL Server, IBM DB2, or Oracle 128Kbps or higher to a central site

This diagram shows a single zone with remote sites and a central office. The data store and data collector are located at the central office.



35

Citrix recommends the following in for small farms with remote sites: Provide a central site with a dedicated connection to each remote site Consider centralizing servers at one site and have users connect from clients at remote sites so that communication between servers does not cross a WAN link, allowing the ICA protocol to enhance performance for users across the WAN Consider using Virtual Private Network (VPN) technology for remote sites Restart servers only when WAN links are at low utilization

Large Farm Multiple Data CentersThis scenario describes a large single farm environment where all servers reside in large data centers as specified in the following configuration:Servers Zone(s) Physical Sites Data Store Connectivity 200+ 2-4 2 Microsoft SQL Server or Oracle (replicated to speed server start time and minimize WAN queries) High speed (T1 or higher)

This diagram shows a farm with two data centers, each with its own zone. Zone 1 contains the data store master, a data collector, and multiple farm member servers. Zone 2 contains a data store replica, a data collector, and multiple farm member servers.

Citrix recommends the following for large farms with multiple data centers: Tune database replication intervals to reduce WAN utilization. Be aware that changes made at the central site can take a few minutes to disseminate to replicas.

36



The IBM DB2 database does not support updateable replicas and should, therefore, not be used in this scenario.

Large Farm Regional SitesThis scenario describes a large single farm environment where servers reside both in regional sites and small remote sites.Servers Zone(s) Physical Sites Data Store Connectivity 200+ (smaller sites connect to closest regional site) 1 per regional site 2+ Microsoft SQL Server or Oracle (replicated to each regional site) High speed (T1 or higher) between all regional sites 128Kpbs or higher between regional and smaller sites

This diagram shows four regional sites with remote access. Each site is a zone and includes a data collector for the zone, multiple local farm member servers, and multiple remote farm member servers. The data store master is located in Zone 1 and a data store replica is located in each of the other zones.



37

Citrix recommends the following for large farms with regional sites: Consider using Virtual Private Network (VPN) technology for remote sites. Consider centralizing servers at one site and have users connect from clients at remote sites so that communication between servers does not cross a WAN link, allowing the ICA protocol to enhance performance for users across the WAN. Tune database replication intervals to reduce WAN utilization. Be aware that changes made at the central site can take a few minutes to disseminate to replicas. The IBM DB2 database does not support updateable replicas and should, therefore, not be used in replicated scenarios.

38




CHAPTER 3

The Farm Data Store

The data store provides a repository of persistent information about the farm that each server can reference, including the following: Farm configuration information Published application configurations Server configurations MetaFrame administrator accounts Printer configurations Trust relationships

CAUTION Ensure that the data store is properly backed up on a regular basis. If the data store database is lost, you must recreate the farm. You cannot recreate the data store from an existing farm. When servers in a farm come online, they query the data store for configuration information.

Viewing Data Store InformationYou can view and change data store information using only management tools for MetaFrame Presentation Server, such as the Presentation Server Console or the Access Suite Console. You can install these management tools from the MetaFrame Presentation Server CD.

40



CAUTION Do not directly edit any data in the data store database with utilities or tools provided by any product other than the MetaFrame Access Suite. For example, do not use IBM DB2, Microsoft SQL Server, or Oracle utilities to edit the data store. Doing so corrupts the data store database and destabilizes the farm.

Choosing a Database for the Data StoreBefore installing MetaFrame Presentation Server, you must decide which database to use for your farms data store. You can use the following database software for the farm data store: Microsoft Access. Access is a lightweight database that is included with Windows server operating systems. The Access database is created on the first server in a new farm. It is most appropriate for small to mid-sized farms. Microsoft SQL Server 2000 Desktop Engine (MSDE). MSDE is a database engine based on Microsoft SQL Server core technology. The MSDE database is created on the first server in a new farm. It is most appropriate for small to medium-sized farms and can be administered using standard Microsoft SQL Server tools. Microsoft SQL Server. SQL Server is a true client/server database that offers robust and scalable support for multiple-server data access. It is suited for use in farms of any size. Oracle. Oracle is a true client/server database that offers robust and scalable support for multiple-server data access. It is suited for use in farms of any size. IBM DB2. DB2 is a true client/server database that offers robust and scalable support for multiple-server data access. It is suited for use in farms of any size.

When using Microsoft Access, the data store database is created when you install MetaFrame Presentation Server. When using MSDE, you first install MSDE and then create an MSDE instance. Then you run MetaFrame Presentation Server Setup. The database is stored on the first server in the farm. When using Microsoft SQL Server, Oracle, or IBM DB2, the database is on a server dedicated to running the database product. This dedicated server must be set up prior to creating the farm because you need to configure an ODBC connection to it. Servers running MetaFrame Presentation Server must also have the appropriate database client software installed on them.


Chapter 3 The Farm Data Store

41

CAUTION Do not install MetaFrame Presentation Server on the Microsoft SQL, Oracle, or IBM DB2 database server. See your database products documentation for specific hardware requirements for the database server. You should consider many factors before deciding which database product to use for the data store, including but not limited to: The number of servers you currently plan to have in the farm and whether you plan to expand that number Whether or not you have a database administrator on staff with the expertise to configure and manage a data store running on SQL Server, Oracle, or DB2 Whether or not you foresee the enterprise expanding, therefore expanding the number and type of published applications Whether or not the database can sustain an increase in the number of users and connections Whether a server has the appropriate hardware configuration to also run an Access or MSDE database or whether you require that the database be located on a server that is not also running MetaFrame Presentation Server Any database maintenance requirements you may have, such as backup, redundancy, and replication

Important Microsoft SQL, Oracle, and IBM DB2 servers require significant expertise to install and maintain. If you do not have expertise with these products, attempting to use them in a production environment is not recommended. See the documentation included with your database product for important details such as performance tuning and database backup procedures. For information about supported database and ODBC driver versions, see Data Store Database Requirements on page 47.

42



System Sizing for the Data StoreThe choice of which database to use for the data store depends on your implementation and environment. Use the chart below as a guideline to determine which scenario most closely matches your environment. If your environment does not fit neatly into the categories listed, choose the category that has the most in common with your environment.Small Servers Named Users Applications 1-50 < 150 < 100 Medium 25-100 < 3000 < 100 Large 50-100 < 5000 < 500 Enterprise 100 or more > 3000 < 2000

The following are general recommendations for the farms data store database: Microsoft Access and MSDE are suitable for all small and many medium-sized environments that are located in one physical location. Microsoft SQL, Oracle, and IBM DB2 are suitable for any size environment and are especially recommended for all large and enterprise environments. When deploying large farms across a WAN, you can obtain considerable performance advantage by replicating the data store and distributing the load over multiple database servers. Microsoft SQL, Oracle, and IBM DB2 are suitable for large farms and support replication. For more information about replicating data stores, see Using Replicated Data Store Databases on page 46.

Suggested Hardware Configurations for the Data StoreThis section outlines suggested hardware configurations resulting from testing in Citrix labs. All tests used Microsoft SQL Server 2000 in the default configuration without replication for the farms data store. Increasing the CPU power and speed of the database server can improve the response time of queries made to the data store. Increase the processing power of the data store database server to achieve improved results in the following areas: Starting the Citrix IMA Service on multiple servers simultaneously Adding a server to the farm Removing a server from the farm



43

The response time of other events occurring in the farmsuch as starting the IMA Service on a single server, recreating the local host cache, or replicating printer drivers to all servers in the farmis affected more by the size of the farm than by the response time of the data store. Citrix testing shows that adding processors to the server hosting the data store can dramatically improve response time when multiple simultaneous queries are being executed. If the environment includes large numbers of servers coming online simultaneously and at frequent intervals, the additional processors can service requests faster. The actual performance of a farms data store can vary depending upon which database engine is used and the level of performance tuning that can be achieved. Depending on the characteristics of a server farm, the CPU speed and CPU quantity can vary widely. In the chart below, five sample farm configurations are displayed and referred to as scenarios A through E. Each scenario lists measurements of various metrics in the farm. The second chart shows, for each corresponding scenario, which hardware configurations are suggested for the server hosting the data store.Scenario Number of servers in farm Number of applications published to all servers Number of user policies Printers per server Printer drivers installed per server Network print servers with printers Number of Load Manager load evaluators Number of Resource Manager applications Number of Installation Manager groups Number of Installation Manager packages Number of application folders in Presentation Server Console Number of server folders in Presentation Server Console A 80 50 25 5 25 5 10 10 5 5 10 8 B 160 50 25 5 25 5 10 10 5 5 10 16 C 250 50 25 5 25 5 10 10 5 5 10 25 D 350 50 25 5 25 5 10 10 5 5 10 35 E 500 50 25 5 25 5 10 10 5 5 10 50

44



Scenario Number of Resource Manager metrics per server Number of MetaFrame administrators Size of data store database in megabytes Scenario Dual Pentium 3/700MHz with 1GB RAM Dual Pentium 4/1.6GHz with 4GB RAM Quad Pentium 4/1.6GHz with 4GB RAM 8-way Pentium 3/700MHz with 8GB RAM

A 25 10 32 A X X X X

B 25 10 51 B X X X X

C 25 10 76 C

D 25 10 101 D

E 25 10 125 E

X X X X X X X

Connecting Directly or Indirectly to the Data StoreAfter you decide which database to use for the data store, decide whether servers running MetaFrame Presentation Server will connect directly to it or indirectly through another server. Direct access. To make a direct connection to the data store, a server must have the appropriate ODBC drivers installed and configured properly. The server then connects directly to the server on which the database is running. Indirect access. For indirect access, a server connects to an intermediary server running MetaFrame Presentation Server that connects to the data store directly. Citrix does not recommend that you use indirect access for mission-critical farms because the intermediary server is a single point of failure. Note Although it is possible to configure multiple servers in the farm to connect directly to a single MSDE database, Citrix does not recommend this configuration because it is not supported by MSDE. MSDE allows only five connections per installed instance of MSDE. If more than five servers attempt to access the MSDE database at the same time, they cannot connect. Citrix recommends that you configure an MSDE database for indirect access. For more information, see Configuring Connections to the MSDE Database on page 52. By default, indirect access uses TCP port 2512 for communication between servers in the farm and the intermediary server that connects to the data store. If the servers are in different subnets divided by a firewall, be sure this port is open on the firewall.



45

Using a RAID EnvironmentThis section describes factors to consider if you are thinking about putting the farms data store in a Redundant Array of Independent Disks (RAID) environment. See the table below for information about cost, performance, and fault tolerance related to four different RAID configurations.RAID 0 RAID 0 has no redundancy. It is striped, which means that data is divided into blocks spanning multiple disks. RAID 0 has multiple actuators (read/write mechanisms) because of the multiple disk use. More actuators improve read and write performance. Citrix does not recommend the use of RAID 0 for critical data, such as a server farms data store. The savings realized from purchasing fewer disks does not typically make up for the costs resulting from downtime and support. RAID 1 uses fully redundant disk mirroring. With disk mirroring, a complete copy of one drive is maintained on another drive. RAID 1 provides high fault tolerance and can improve read performance. However, RAID 1 writes the data twice, which can degrade write performance in single disk/controller environments. In addition, this type of redundancy requires twice the disk space. Like RAID 0, RAID 5 is striped. However, because RAID 5 adds parity to the data striping, it includes fault tolerance. If one disk in a RAID 5 group fails, the logical disk continues to function. The parity information is used to recreate data on a replacement disk. The loss of two disks in a group at one time cannot be sustained. RAID 5 uses multiple disk actuators that provide improved read and write performance. RAID 10 combines RAID 1 and RAID 0. It is a striped and fully mirrored set of disks. It is the best configuration for both redundancy and performance. Because of this, it is the most expensive storage option.

RAID 1

RAID 5

RAID 10

46



Using Replicated Data Store DatabasesCitrix recommends using a single data store where appropriate but in some situations, a replicated data store can improve farm performance. This section covers the concerns and situations that arise from using replicated database technology.

High Latency WAN ConcernsCrossing high latency links without the use of replicated databases can create situations where the data store is locked for extended periods of time when performing farm maintenance from remote sites. This means that the Citrix IMA Service may start after extended periods of time and some normal operations may fail when performed from the remote site. Tip You might experience poor performance if you use a local Presentation Server Console to perform farm maintenance on a remote site that has high latency. Such a situation requires communication between the console and the data store to cross the high latency link. You can publish the Presentation Server Console as an application on a server at the remote site and use a MetaFrame Presentation Server Client to access the published console. The following issues can arise in a high-latency situation: Data store writes take longer to complete and can, for a period of time, block all additional writes from local or remote sites Data store reads do not generally adversely affect local connections but remote sites can experience slower performance

Enhancing Performance with Replicated DatabasesBecause servers in a farm perform many more reads from the data store than writes to the data store, you may want to use replicated databases to increase read performance. In a WAN environment you can place replicas of the data store at sites with a considerable number of servers. This practice minimizes reads across the WAN link. Database replication does consume bandwidth. Limit the use of replicated databases to situations where the remote site has enough servers to justify the cost of placing a replicated copy of the database at the site.



47

Data Store Database RequirementsYou can use the Microsoft Access or MSDE database engines or a Microsoft SQL Server, Oracle, or IBM DB2 database for the farms data store. The supported database versions and ODBC drivers are listed below. Microsoft Access Jet Engine 4.0, Service Pack 1 through Service Pack 8 Microsoft SQL Server Desktop Engine (MSDE) 8.00.760 for Windows 2000, Service Pack 3 or later Microsoft SQL Server 7.0 with Service Pack 2 Microsoft SQL Server 2000 Oracle Server 7 (7.3.4) for NT Oracle Server 8 (8.0.6) for NT Oracle Server 8i (8.1.5, 8.1.6, 8.1.7) for NT and UNIX Oracle Server 9i (9.0.1) for NT Oracle 9i R2 for NT and Solaris IBM DB2 Version 7.2 with FixPak 5-13 IBM DB2 Version 8.1 with FixPak 1-7a

Microsoft SQL Server, Oracle, and IBM DB2 databases require an ODBC database client driver installed on each server that connects directly to them. Servers that connect to the data store database indirectly (that is, through another server running MetaFrame Presentation Server) do not require an ODBC client driver.

48



The following table lists the drivers required for supported ODBC database clients:Database SQL 7.0 Enterprise for NT MDAC 2.5 SQL 7.0 Enterprise for NT MDAC 2.5 Service Pack 1 SQL 2000 Enterprise for NT MDAC 2.5 Service Pack 2 SQL 2000 Enterprise for NT MDAC 2.6 Service Pack 1 SQL 2000 Enterprise for NT MDAC 2.7 SQL 2000 Enterprise for NT MDAC 2.7 Service Pack 1 SQL 2000 Enterprise for NT MDAC 2.8 Oracle 7.3.4 for NT Oracle 8.1.5 for NT Oracle 8.1.6 for NT Oracle 8.1.6 for Solaris Oracle 8.1.7 for NT Oracle 9.0.1 for NT Oracle 9i R2 for Solaris Oracle 9i R2 for NT IBM DB2 FixPak 5 for NT IBM DB2 FixPak 7 for NT IBM DB2 Version 8.1 ODBC Client Driver Version 3.70.0820 3.70.0821 3.70.0961 2000.80.380.0 2000.81.7713.00 2000.81.9031.38 2000.85.1022.00 2.50.0301 8.01.55.00 8.1.6.00 8.1.6.00 8.1.7.00 9.00.11.00 9.2.0.1.0 9.2.0.1.0 7.01.00.55 7.01.00.65 8.01.04.341

CAUTION The Oracle Client Version 8.1.5 is not supported. If you are using this version, upgrade to 8.1.55.

Tip Before installing an update of Microsoft Data Access Components (MDAC), stop the Microsoft Terminal Services Licensing service. Restart the Terminal Services Licensing service before beginning MetaFrame Presentation Server Setup.



49

Microsoft AccessChoosing Use a local database on this server and selecting the Access Database entry from the list of possible databases during MetaFrame Presentation Server Setup creates a Microsoft Access database on the first server in the new farm. This database acts as the farms data store. The Microsoft Access database engine and ODBC drivers are default components of Windows servers. The ODBC connection to Access uses the Microsoft Jet Engine. To use the database engine, you do not have to install any drivers or perform any database configuration prior to installation of MetaFrame Presentation Server.

Minimum RequirementsThe server that hosts the Access database should meet the following minimum requirements: Approximately 50MB of disk space for every 100 servers. Increase disk space if there are a large number of published applications in the farm. 32MB of additional RAM if the server also hosts connections.

Authenticating to the Access DatabaseIf you decide to create a local Microsoft Access database for the data store,

metaframe presentation server administrators guide

Documents