Administrator’s Guide · deploying, and maintaining Citrix ICA Clients for UNIX (also called the...

Administrator’s Guide

Citrix ICA UNIX ClientsVersion 6.30 Version 6.20 Version 6.0Linux Sun Solaris (SPARC) IBM AIX

HP-UX

Version 3.0SGI IRIXCompaq Tru-64Sun OSSun Solaris (x86)SCO

Citrix Systems, Inc.

Information in this document is subject to change without notice. Companies, names, and data used inexamples herein are fictitious unless otherwise noted. No part of this document may be reproduced ortransmitted in any form or by any means, electronic or mechanical, for any purpose, without the expresswritten permission of Citrix Systems, Inc.

© 1994-2002 Citrix Systems, Inc. All rights reserved.

RSA Encryption © 1996-1997 RSA Security Inc., All Rights Reserved.

Version 6.30 includes software developed by David Corcoran ([email protected]) http://linuxnet.com (MUSCLE).

Winscard.h/pcsc lite for smartcard reader communications Copyright (c) 2000 David Corcoran([email protected]). All rights reserved. Redistribution and use in source and binary forms, with orwithout modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and thefollowing disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and thefollowing disclaimer in the documentation and/or other materials provided with the distribution.

3. All advertising materials mentioning features or use of this software must display the followingacknowledgement:

This product includes software developed by: David Corcoran ([email protected])<http://www.linuxnet.com> (MUSCLE)

4. The name of the author may not be used to endorse or promote products derived from this softwarewithout specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR

IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES

OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.

IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,

INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT

NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,

DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY

THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT

(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF

THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Citrix, Independent Computing Architecture (ICA), MultiWin, SecureICA, Program Neighborhood, andMetaFrame are registered trademarks or trademarks of Citrix Systems, Inc. in the U.S.A. and othercountries.

Microsoft, MS, MS-DOS, Windows, Windows NT, and BackOffice are either registered trademarks ortrademarks of Microsoft Corporation in the United States and/or other countries.

UNIX is a registered trademark of The Open Group in the U.S.A. and other countries.

Solaris is a trademark or registered trademark of Sun Microsystems, Inc. in the United States and othercountries.

All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARCInternational, Inc. in the United States and other countries. Products bearing SPARC trademarks are basedupon an architecture developed by Sun Microsystems, Inc.

HP-UX is a registered trademark of Hewlett-Packard Company.

AIX and RS/6000 are registered trademarks of International Business Machines Corporation.

SGI is a registered trademark of Silicon Graphics, Inc.

SCO is a registered trademark of The Santa Cruz Operation, Inc.

Tru64 is a registered trademark of Compaq Computer Corporation.

Linux® is a registered trademark of Linus Torvalds.

All other Trade Names referred to are the Servicemark, Trademark, or Registered Trademark of therespective manufacturers.

Last Updated: April 5, 2002 (JF)

Contents 5

Contents

Before you Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Who Should Use this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

How to Use this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Finding More Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Citrix on the World Wide Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Providing Feedback About this Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Chapter 1 Introduction to the Citrix ICA UNIX Clients. . . . . . . . . . . . . . . . . . . . . . . . . 13Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Features Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Client Device Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Client Drive Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Client Printer Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15COM Port Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Client Audio Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Disk Caching, Data Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Low Bandwidth Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Client Auto Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Color Approximation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16ICA Client Hotkeys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Transparent Clipboard Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Application Publishing Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Business Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

New Features Introduced in Version 6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17ICA Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17SpeedScreen Latency Reduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Increased Color Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Seamless Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

New Features Introduced in Version 6.20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Enhanced Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

SSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Extended Parameter Passing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Time Zone Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

New Features Introduced in Version 6.30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Smart Card Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Auto Client Reconnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

6 Citrix ICA UNIX Client Administrator’s Guide

Server-Client Content Redirection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Roaming User Reconnect. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20TLS Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Citrix Secure Gateway Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Enhanced Proxy Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21User-to-User Shadowing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Improved in this Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Chapter 2 Deploying the Citrix ICA UNIX Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

About Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Installing the ICA Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Starting the ICA UNIX Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Preparing for Client Auto Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Using the Client Update Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26The ICA Client Update Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Configuring the Client Update Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Creating a New Client Update Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Setting a Default Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Configuring the Properties of the Client Update Database . . . . . . . . . . . . . . . . 30Adding and Removing Clients From the Database . . . . . . . . . . . . . . . . . . . . . . 31Changing the Properties of an ICA Client in the Database. . . . . . . . . . . . . . . . 33

Uninstalling the ICA Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Using the UNIX ICA Client as an “ICA to X Proxy”(“Server Side ICA”) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Supported Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Starting the ICA Client with “Server Side ICA” . . . . . . . . . . . . . . . . . . . 37

Chapter 3 Configuring the Citrix ICA UNIX Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Creating a Connection Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Enabling Smart Card Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Opening a Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Mapping Client Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Mapping COM Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Mapping Client Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Mapping Client Printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Mapping Client Printers on MetaFrame for Windows . . . . . . . . . . . . . . . . . . . 49Mapping Client Printers on MetaFrame for UNIX . . . . . . . . . . . . . . . . . . . . . . 50

Setting up Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Using Printing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Contents 7

To print from applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Mapping Client Audio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Changing a Connection Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Configuring Network Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Improving Performance over a Low-Bandwidth Connection. . . . . . . . . . . . . . 55

Changing your ICA Client Configuration . . . . . . . . . . . . . . . . . . . . . . . . 56Changing the Way You Use the Client . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Specifying an Application to Run at Connection . . . . . . . . . . . . . . . . . . . . . . . 58Changing the Window Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Configuring Login Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Changing Default Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Changing Settings for the Disk Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Configuring Default Window Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Configuring Auto Client Reconnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Configuring Network Protocol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Configuring Server Location and Business Recovery. . . . . . . . . . . . . . . . . . . . 66Configuring Hotkeys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Configuring Preferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Using xcapture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Integrating the ICA UNIX Client with Security Solutions . . . . . . . . . . . . . . . . . . . 72Connecting Through a Proxy Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Using Auto-Client Proxy Detection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Connecting Through a SOCKS Proxy Server . . . . . . . . . . . . . . . . . . . . . . . . . . 72Connecting Through a Secure Proxy Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Connecting Across a Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Using ICA Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Integrating the ICA UNIX Client with Citrix Secure Gateway or SSL Relay . 75

Using Applications Published on a MetaFrame for UNIX Server . . . . . . . . . . . . . 79Using the Window Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

About Seamless Windows on MetaFrame for UNIX. . . . . . . . . . . . . . . . 79Minimizing, Resizing, Positioning, and Closing Windows . . . . . . . . . . . 79Using the Citrix Window Manager Menus . . . . . . . . . . . . . . . . . . . . . . . 80

Copying and Pasting Graphics Using ctxgrab and ctxcapture . . . . . . . . . . . . . 81Using ctxgrab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Using ctxcapture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Setting up Extended Parameter Passing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Setting up Server-Client Content Redirection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Common Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Command-line Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

9

Before you Begin

Who Should Use this ManualThis manual is for system administrators responsible for installing, configuring,deploying, and maintaining Citrix ICA Clients for UNIX (also called the CitrixICA UNIX Clients). This manual assumes knowledge of:

! Citrix MetaFrame

! The operating system on the client computer (UNIX or Linux)

! Installation, operation, and maintenance of network and asynchronouscommunication hardware, including serial ports, modems, and deviceadapters.

How to Use this GuideTo get the most out of the Citrix ICA UNIX Clients Administrator’s Guide, reviewthe table of contents to familiarize yourself with the topics discussed.

This guide contains the following sections:

Chapter Contents

Chapter 1, “Introduction tothe Citrix ICA UNIX Clients”

Gives a detailed list of features.

Chapter 2, “Deploying theCitrix ICA UNIX Client”

Describes how to install and deploy the Citrix ICAUNIX Client.

Chapter 3, “Configuring theCitrix ICA UNIX Client”

Describes how to configure connection properties anddevice mappings for the Citrix ICA UNIX Client.


ConventionsThe following conventional terms, text formats, and symbols are used throughoutthe printed documentation:

The front cover of this Guide shows you the various Citrix ICA UNIX Clientsand their current release version.

Instructions or features specific to Citrix ICA Clients for UNIXVersion 6.0 and later.

Instructions or features specific to Citrix ICA Clients for UNIXVersion 6.20 and later.

Instructions or features specific to Citrix ICA Clients for UNIXVersion 6.30.

Note Example screens shown throughout this document are for illustrative pur-poses only and may not match the same screen displays on your system.

Convention Meaning

Bold Indicates boxes and buttons, column headings, command-linecommands and options, icons, dialog titles, lists, menu names,tabs, and menu commands.

Italic Indicates a placeholder for information or parameters that youmust provide. For example, if the procedure asks you to typefilename, you must type the actual name of a file. Italic alsoindicates new terms and the titles of other manuals.

ALL UPPERCASE Represents keyboard keys (for example, CTRL, ENTER, F2).

[brackets] Encloses optional items in syntax statements. For example,[password] indicates that you can choose to type a passwordwith the command. Type only the information within thebrackets, not the brackets themselves.

...(ellipsis) Indicates a command element can be repeated.

Monospace Represents examples of screen text or entries that you can typeat the command line or initialization files.

! Indicates a procedure with sequential steps.

! Indicates a list of related information, not procedural steps.

Before you Begin 11

Finding More InformationThis manual contains information about the Citrix ICA UNIX Clients, togetherwith instructions for installing and configuring these clients. For additionalinformation, refer to:

! The Citrix ICA Client Administrator’s Guides for the other ICA Clients.

! For instructions on installing, configuring, and maintaining your MetaFrameservers, see the documentation included in your MetaFrame package.

This manual and other Citrix documentation are available in Adobe PDF formatin the following locations:

! The documentation directory of your Components CD-ROM

! The documentation directory of your MetaFrame server CD-ROM

! On the Citrix Web site at http://www.citrix.com/support/. Click ProductDocumentation and choose ICA Client.

Using Adobe Acrobat Reader, you can view and search the documentationelectronically or print it for easy reference. To download Adobe Acrobat Readerfor free, go to Adobe’s Web site at http://www.adobe.com.

Important Always consult the Readme files for MetaFrame and the Citrix ICAClients for any last-minute updates, installation instructions, and corrections tothe documentation.

Citrix on the World Wide WebThe Citrix Web site, at http://www.citrix.com/, offers a variety of information andservices for Citrix customers and users. From the Citrix home page, you canaccess Citrix online Technical Support Services and other information designedto assist MetaFrame administrators, including the following:

! Downloadable Citrix ICA Clients at http://www.citrix.com/download/

! Citrix Product Documentation Library, containing the latest documentation forall Citrix products (at http://www.citrix.com/support/ select ProductDocumentation). You can download updated editions of the documentationthat ships with Citrix products and supplemental documentation that may onlybe available from the Citrix Web site.

! Program information about Citrix Preferred Support Services options

! An FTP server containing the latest service packs, hotfixes, utilities, andproduct literature for download

! An online Solution Knowledge Base containing an extensive collection ofapplication notes, technical articles, troubleshooting tips, and white papers

! Interactive online Solution Forums for discussion of technical issues withother users

! Frequently Asked Questions pages with answers to common technical andtroubleshooting questions

! Information about programs and courseware for Citrix training andcertifications

! Contact information for Citrix headquarters, including worldwide, European,Asia Pacific, and Japan headquarters

! The Citrix Developer Network (CDN) at http://www.citrix.com/cdn/ Thisopen enrollment membership program provides access to developer tool kits,technical information, and test programs, for software and hardware vendors,system integrators, ICA licensees, and corporate IT developers whoincorporate MetaFrame server-based computing solutions into their products.

Providing Feedback About this GuideWe strive to provide accurate, clear, complete, and usable documentation forCitrix products. If you have any comments, corrections, or suggestions forimproving our documentation, we want to hear from you. You can send email tothe documentation authors at [email protected]. Please include the productname and version number, and the title of the document in your message.

C H A P T E R 1

Introduction to the Citrix ICA UNIXClients

OverviewICA Clients are the client-side software components of the MetaFrame ApplicationServer product family. Combining the ease of use you expect with the securityfeatures you require, ICA Clients offer point-and-click, secure access toapplications, content, and entire desktops published on MetaFrame servers.

The ICA UNIX Clients have the following features:

• Client Device Mapping

• Client Drive Mapping

• Client Printer Mapping

• COM Port Mapping

• Client Audio Mapping

• Disk Caching and Data Compression

• Low Bandwidth Requirements

• Client Auto Update

• Color Approximation

• ICA Client Hotkeys

• Transparent Clipboard Access

• Application Publishing Support

• Business Recovery

• Encryption

• SpeedScreen Latency Reduction


• Increased Color Support

• Seamless Windows Support

• SSL Support

• Extended Parameter Passing

• Time Zone Support

• Smart Card Support

• Auto Client Reconnect

• Server-Client Content Redirection

• Roaming User Reconnect

• TLS Encryption

• Citrix Secure Gateway Support

• Enhanced Proxy Support

• User-to-User Shadowing

Some client features are available only when connecting to MetaFrame forWindows NT and MetaFrame for Windows 2000 servers.

Features OverviewThe following sections provide a brief introduction to major features of the CitrixICA UNIX Clients.

Client Device MappingClient device mapping allows a remote application running on the MetaFrameserver to access printers and disk drives attached to the local client computer.

Note Client device mapping, except printers, is not supported when connecting toCitrix MetaFrame for UNIX Operating Systems Versions 1.0 and 1.1. Client printermapping and, with hotfix 2, client drive mapping are supported when connecting toVersion 1.1, Feature Release 1.

Chapter 1 Introduction to the Citrix ICA UNIX Clients 15

Client Drive MappingClient drive mapping makes any directory mounted on your UNIX-based computer,including CD-ROMs, available to you during ICA sessions on MetaFrame servers.When a MetaFrame server is configured to allow client drive mapping, you canaccess your locally stored files, work with them during your ICA sessions, and thensave them either on a mounted directory or on a drive on the MetaFrame server.

Client Printer MappingClient printer mapping lets users access printers attached to their computers duringICA sessions. ICA Client users can print to any spooled printer available from theUNIX workstation.

COM Port MappingClient COM port mapping allows devices attached to the client computer’s COMports to be used from ICA sessions on a MetaFrame server. This allows localdevices like modems, serial printers, and bar-code scanners to be used byapplications running on the MetaFrame server.

In the Citrix ICA UNIX Clients Version 3.0, COM port mapping was introduced forthe Linux client only. Version 6.0 and later of the Clients now have this feature formore operating systems — Linux, Solaris SPARC, HP-UX, and AIX.

Client Audio Mapping

Client audio mapping allows your client computer to play sounds generated byapplications running on the MetaFrame server.

ICA Client audio support includes configurable sound quality levels that allow youto customize sound quality based upon the amount of bandwidth available.

Disk Caching, Data CompressionThese features can increase performance over low-speed asynchronous and WANconnections. Disk caching stores commonly used portions of your screen (such asicons and bitmaps) locally, increasing performance by avoiding retransmission oflocally cached data. Data compression reduces the amount of data sent over thecommunications link to the client.

Low Bandwidth RequirementsThe Citrix ICA protocol typically uses 20K of bandwidth for each session.


Client Auto UpdateThe Client Auto Update feature allows administrators to update ICA Clientinstallations from a central location instead of having to manually install new clientversions on each client computer. New versions of ICA Clients are stored in acentral Client Update Database on a MetaFrame for Windows server. The latestversions of the ICA Client software are downloaded to ICA Client devices whenusers connect to a MetaFrame server.

Color ApproximationBecause of differences in the palettes used by the ICA Client (and the applications itdisplays) and native UNIX desktops, an annoying flashing can occur whenswitching context on a pseudo-color display. The ICA Client’s color approximationscheme eliminates this flashing by using colors from the local desktop palette todisplay the ICA Windows sessions.

ICA Client HotkeysThe ICA Client provides hotkeys that can be used to control various functions whilein an ICA session. ICA Client hotkeys let you define alternative key combinationsfor the hotkeys ALT+F1 to ALT+F12, ALT+TAB, ALT+SHIFT+TAB, and ToggleSpeedscreen, because these are reserved for use by X Window managers.

Transparent Clipboard AccessYou can use the client workstation’s clipboard to cut and paste text and graphicsbetween applications running locally on the client computer and applicationsrunning remotely in an ICA session.

Access to the local clipboard requires no special configuration or procedures.Usingthe familiar cut, copy, and paste commands, you can transfer text and graphics backand forth between local and remote applications.

To help the exchange of graphical data between the MetaFrame server clipboardand non-ICCCM-compliant X Windows applications on the X desktop, you can usethe xcapture program. See “Using xcapture” on page 70 for more details. Note thatnot all server platforms support all media types on the clipboard.

Application Publishing SupportYou can create a remote application entry that contains all of the informationnecessary to launch a user session or a published application.


Business RecoveryThe ICA Client supports multiple server sites (such as primary and backup), withdifferent addresses for the same published application name.

This feature provides consistent connections to published applications in the eventof primary server disruption.

New Features Introduced in Version 6.0The following sections provide a brief introduction to new features introduced inCitrix ICA UNIX Client Version 6.0. These features are also available in all laterversions.

ICA EncryptionThe ICA Client supports encryption using Citrix ICA Encryption Services. ICAEncryption (SecureICA) is a server extension that adds advanced RSA RC5encryption to the MetaFrame server and clients. See the ICA Encryption Servicesdocumentation for more information.

Note To use advanced encryption, you must install ICA Encryption on yourMetaFrame server. ICA Encryption is included by default in MetaFrame XP,Feature Release 1 and later versions. ICA Encryption is not available forMetaFrame for UNIX operating system servers.

SpeedScreen Latency ReductionSpeedScreen Latency Reduction is a combination of technologies implemented toenhance user experience over high latency connections by providing instantfeedback to the user in response to typed data or mouse clicks.

SpeedScreen Latency Reduction includes Local Text Echo, which accelerates thedisplay of input text by using a default font that is updated when the actual fontdetails are received from the server, effectively shielding the user fromexperiencing latency on the network; and Mouse Click Feedback, which providesvisual feedback of a mouse click by immediately changing the mouse pointer intoan hourglass indicator.

Note SpeedScreen Latency Reduction is not available when connecting to CitrixMetaFrame for UNIX 1.0 and 1.1 servers.


Increased Color SupportYou can configure the Citrix ICA UNIX Clients for true color (24-bit) support.Version 6.0 and later of the ICA Clients supports high color (32 thousand colors)and true color (24-bit) ICA connections. Support for 16 and 256 colors is includedin earlier versions.

Seamless WindowsThe ICA Client supports the seamless integration of local and remote applicationson the local desktop. By selecting the Seamless Windows option when configuringa connection to a MetaFrame server, a user does not need to access an entire remotedesktop to run remote applications. With a single session, a user can gain access tomultiple applications and switch between local and remote applications.

Note Because the UNIX Client supports seamless windows natively, it is notnecessary to use "pass-through" mode. Pass-through mode is intended to facilitateseamless windows for ICA Clients that do not support seamless windows natively,and should only be used from a fixed-size window session on the client device.Please note that "seamless within seamless" (that is, seamless windows via pass-through mode) is not a supported configuration for the UNIX Client.

New Features Introduced in Version 6.20The following sections give you an introduction to new features introduced inCitrix ICA UNIX Clients Version 6.20. These features are also available in all laterversions.

Enhanced EncryptionVersions 6.20 and later have enhanced encryption handling capabilities.

SSLThe ICA Client supports Secure Sockets Layer (SSL) encryption. SSL-levelencryption provides server authentication, data stream encryption, and messageintegrity checks. SSL+HTTPS (secure HTTP) browsing is also supported.

Note TLS Encryption is supported in Version 6.30 Clients.


Extended Parameter PassingWith extended parameter passing, you can integrate MetaFrame publishedapplications into desktop UNIX environments by associating a file type on a clientdevice with an application published on a MetaFrame XP server. When a useropens a locally saved file, the file is opened in the application associated with it.

Time Zone SupportThis MetaFrame XP feature allows the user, when logging on to a MetaFrameserver in a different time zone, to have the ICA session reflect the time zone of theclient device.

For example, a user in London, which is in the Greenwich Mean Time zone, logs into a MetaFrame server in New York City, which is in the Eastern time zone, andlaunches Microsoft Outlook as a published application. Microsoft Outlook stampsemails sent during the ICA session with the user’s GMT time zone information.

New Features Introduced in Version 6.30The following sections provide an introduction to new features introduced in CitrixICA UNIX Clients Version 6.30.

Smart Card SupportThe ICA UNIX Clients offer support for a number of smart card readers. If smartcard support is enabled on both the server and client sides, you can use smart cardsfor the following purposes:

Smart card login authentication. Use smart cards to authenticate users toMetaFrame XP servers.

Smart card application support. Allow smart card-aware published applicationsto access local smart card readers.

Smart card data is security-sensitive, and should be transmitted over a secureauthenticated channel such as Secure Sockets Layer (SSL). Smart card devices andpublished applications must comply with the PC/SC industry standard.


Auto Client ReconnectICA sessions can be dropped because of unreliable networks, highly variablenetwork latency, or range limitations of wireless devices.

The Auto Client Reconnect feature is triggered when the ICA Client detects adisconnected session. When this feature is enabled on a MetaFrame XP server,users do not have to reconnect manually or reenter login credentials to continueworking. Automatic reconnection does not occur if users exit applications withoutlogging off.

Server-Client Content RedirectionServer-client content redirection allows you to specify that URLs in a publishedapplication are opened using a local application. For example, double-clicking alink to a Web page while using Microsoft Outlook in an ICA session opens therequired file using the browser on the client device. Server-client contentredirection allows administrators to allocate MetaFrame resources more efficiently,thereby providing users with better performance.

Roaming User ReconnectRoaming User Reconnect adds roaming capabilities to ICA sessions. Previously,ICA sessions were identified by the name of the client device from which they wereinitiated, and they were limited to that device. Feature Release 2 of MetaFrame XPidentifies sessions by user name. As a result, users can resume their ICA sessionsfrom any ICA-enabled device. This allows users to start a session on one device andresume work on another. Note that Roaming User Reconnect is only effective whenconnecting to load balanced published applications.

Roaming User Reconnect does not require client configuration.

Note Roaming User Reconnect is not supported for connections that use smartcard authentication.

TLS EncryptionThe ICA Client now supports TLS 1.0, the successor to SSL 3.0, for environmentsthat demand it. TLS (Transport Layer Security) is the standardized form of SSL(Secure Sockets Layer). Both are cryptographic security protocols designed toensure the integrity and privacy of data transfers across public networks. SSL andTLS are functionally equivalent. Certain organizations have a security policy thatrequires TLS rather than SSL.


Citrix Secure Gateway SupportThe ICA UNIX Clients provide full support for Citrix Secure Gateway Version 1.1.Citrix Secure Gateway acts as a secure Internet gateway between SSL/TLS-enabledICA Clients and MetaFrame XP servers. The Internet portion of ICA trafficbetween client devices and the Citrix Secure Gateway server is SSL/TLS-encrypted. SSL/TLS is the Internet standard 128-bit encryption technology used forclient-server authentication, and to ensure the integrity and privacy of data transfersacross public networks.

Enhanced Proxy SupportAs an alternative to SOCKS proxy, the ICA UNIX Clients also support Secureproxy (also known as Security proxy, HTTPS proxy, and SSL-tunnelling). Proxyauthentication is also supported. When used with Citrix Secure Gateway,applications can be delivered securely to anywhere in the world, via the Internet.

The ICA UNIX Clients can auto-detect proxy server settings from the Web browserand use these for making ICA connections.

User-to-User ShadowingShadowing is the process of monitoring a user’s session remotely and, optionally,participating in the session using your own keyboard and mouse. Previouslyreserved for MetaFrame administrators, this feature no longer requiresadministrative rights. You can now make shadowing available to users, addingpowerful collaborative capabilities to a variety of applications, including:

• Help desks, where trained personnel troubleshoot applications

• Training organizations, where students observe instructors, and instructorsmonitor student performance

• Presentation sessions, where multiple remote users attend a presentation hostedby a single user

Shadowing does not require client configuration. This feature is governed by users’policies set on the MetaFrame XP server. For information about enabling andconfiguring this feature, see the MetaFrame XP Administrator’s Guide.


Improved in this ReleaseVersion 6.30 of the ICA Linux Clients provides performance enhancements in thefollowing areas:

• Increased ICA performance

• Improved performance when using SSL

• Enhanced security at log in

• Enhanced printer support and management

C H A P T E R 2

Deploying the Citrix ICA UNIXClients

OverviewThis chapter describes how to install, deploy, and remove the Citrix ICA UNIXClient. Topics covered in this chapter include:

• System requirements

• Installing the ICA Client

• Starting the ICA Client

• Preparing for Client Auto Update

• Using the Client Update Database

• Removing the ICA Client

• Using the ICA Client as an “ICA to X proxy” (“Server Side ICA”).

About InstallationThere are two ways to install the ICA Client:

• If you are installing the client on machines that don’t already have an ICAClient installed on them, you must install the client manually. See “Installing theICA Client” on page 24 for details.

• If you already have a previous version of the ICA Client, you can update itautomatically to this version by adding this client to the Client Update Database.See “Using the Client Update Database” on page 26 for details.

If you are using Citrix NFuse Classic in conjunction with Citrix MetaFrame, see theNFuse Classic 1.7 Administrator’s Guide for information about deploying the ICAClients with NFuse Classic.


System RequirementsThe ICA Client supports the following systems and versions. Symbols are used toidentify instructions or features specific to Version 6.0 and later versions; Version6.20 and later versions; or Version 6.30 only of the Citrix ICA Clients for UNIX.See “Conventions” on page 10 for details.

Systems running the ICA Client require the following:

• 4MB of free disk space for the installed client and up to 12MB if you expand theinstallation package on the disk

• 16 color video display or higher

• TCP/IP networking.

Installing the ICA ClientBefore installing the ICA Client, ensure that you have at least 12MB of free diskspace available. Depending on your UNIX platform, you can check the availabledisk space with one of the following commands:df -k <Enter>df <Enter>bdf <Enter>

UNIX System Version

Compaq Tru64 UNIX 3.2 or above

HP-UX 10.20 or above

IBM AIX 4.3.1 or above

Linux Red Hat 5.2 or above, Caldera 2.2 or above, SuSE 6.0 or above, andSlackware 4.0 or above***

SCO UNIXWare 7, UNIXWare 2.1*, OpenServer 5*

SGI IRIX 6.3 or above

Sun Solaris 1.0** (SunOS 4.1.4),2.5.1 (SunOS 5.5.1), andIntel Platform Edition 2.6 (SunOS 5.6) or above

** The SCO client requires the Binary Compatibility Module to run under UNIXWare 2.1 andOpenServer 5.** Requires OpenWindows patch 100444-76.tar.Z, available from SunSolve Online.*** Requires LibC6

Chapter 2 Deploying the Citrix ICA UNIX Clients 25

" To install the Citrix ICA UNIX Client

1. Log on as root at the client workstation.

2. Open a command window.

3. If you are installing the ICA Client from a CD-ROM, insert the CD-ROM in thedrive. Mount the CD-ROM using the appropriate instructions for yourworkstation. Change to the ICAinst/IcaUNIX directory (ICAclient/IcaUNIX forVersion 3.0 installations) on the mounted CD-ROM.

— or —

If you are installing the ICA Client from a tar file, uncompress the tar file andextract the contents into a temporary directory.

4. Run the setup program by typing ./setupwfc and press ENTER.

— or —

If file names on the CD-ROM are displayed in uppercase and are followed byother characters (such as ;1), use the command ./SETUPWFC* and pressENTER.

A menu of options appears.

5. To install the ICA Client, type 1 and press ENTER.

The installation procedure prompts:Please enter the directory in which Citrix ICA Client is to beinstalled [default /usr/lib/ICAClient] or type “quit” to abandon theinstallation:

6. To install in the default location, press ENTER.

The installation procedure allows you to confirm that you want to proceed.

7. To proceed, type y and press ENTER. To cancel the installation, type n andpress ENTER.

The installation procedure displays the Client Software License Agreement andthen prompts for confirmation to proceed.

8. To proceed, type y and press ENTER. To cancel the installation, type n andpress ENTER. If you have Netscape Navigator installed you will prompted tochoose installation of the plug in. If you require the plug in, press y.

9. When the installation is complete, the main installation menu is displayed again.To exit from the setup program, type 3 and press ENTER.


Starting the ICA UNIX Client" To start the UNIX client

At the UNIX prompt, type /usr/lib/ICAClient/wfcmgr and press ENTER(where /usr/lib/ICAClient is the directory in which you installed the ICAClient).

Note If the ICA Client has not been installed in the default installation directory,ensure that the environment variable $ICAROOT is set to point to the actualinstallation directory.

Preparing for Client Auto UpdateICA Client software can be set up so that you can automatically update it from aMetaFrame for Windows server when a newer version is available. This means thatyou can “push” a new version of the client software from the Client UpdateDatabase to the workstation instead of installing the client manually at eachworkstation. You must be logged on as root to deploy the ICA Client.

" To enable the ICA UNIX Client software for automatic update

1. Log on as root.

2. In the ICA Client main window, click Options and then click Settings.

3. In the Settings dialog box, select Preferences from the pull-down menu.

4. Select Allow Automatic Client Updates to allow the client to be automaticallyupdated with a newer version from the MetaFrame server.

Using the Client Update DatabaseClient Auto Update allows future versions of the same platform ICA Client to beautomatically downloaded when a user connects to a MetaFrame for Windowsserver. The new versions of the ICA Clients are downloaded from the Client UpdateDatabase.

ICA Client Auto Update:

• Automatically detects older client files

• Provides full administrative control of client update options for each client

• Updates clients from a single database on a network share point

• Safely restores older client versions when needed


Note Auto Update only functions if the UNIX user has logged on as the root useron the client or has switched to superuser. If the user is not root or superuser, theserver returns an error when trying to perform the client update.

The ICA Client Update ProcessEach ICA Client has a product number, model number, and version number. TheICA Client product and model numbers uniquely identify the ICA Client.

The version number is the release number of the ICA Client.

The process of updating ICA Clients with new versions uses the standard ICAprotocol:

• When the user logs in, the MetaFrame for Windows server queries the ICAClient. If the server detects that the ICA Client is up to date, it continues thelogin transparently.

Product/Model number Platform

1/1 ICA Client for DOS

E/1 ICA 32-bit Client for DOS

1/2 ICA Client for Win16

1/3 ICA Client for Win32

81/1 ICA Client for Compaq Tru64

81/2 ICA Client for HP-UX

81/3 ICA Client for SunOS

81/4 ICA Client for Solaris (SPARC)

81/5 ICA Client for SGI

81/6 ICA Client for RS6000

81/7 ICA Client for Linux (Intel)

81/8 ICA Client for SCO

81/9 ICA Client for Solaris (Intel)

81/A ICA Client for Linux (ARM)

81/B ICA Client for NetBSD

81/C ICA Client for SCO CMW

82/1 ICA Client for Macintosh


• If an update is needed, by default the MetaFrame for Windows server informsthe user and asks to perform the update. You can also specify that the updateoccurs without informing the user or without allowing the user to cancel theupdate.

• By default, the user can choose to wait for the client files to finish downloadingor to download the files in the background and continue working. Usersconnecting to the MetaFrame for Windows server with a modem get betterperformance waiting for the client update to complete. You can also force theclient update to complete before allowing the user to continue.

• During the client update, new ICA Client files are copied to the ICA Clientdevice. The administrator can force the user to disconnect and complete theupdate before continuing the session. The user must log in to the server again tocontinue working.

• After disconnecting from the server, the ICA Client completes the update. Allclient programs must be closed before the ICA Client can be updated.

• If the user does not close all client programs before clicking OK, a messageappears informing the user of the open program. When all programs are closed,the ICA Client can complete the update.

• In case of a problem, the existing ICA Client files are saved in a hiddendirectory called .bk in /usr/lib/ICAClient.

Note The various Auto Update configuration options are only functional for usersconnected to the server without administrator permissions. If the user connects asadministrator, they will see only the Ask User dialog box and can therefore cancelthe update if desired. For more information, see Citrix Knowledge Base articleCTX955387.

Configuring the Client Update DatabaseDuring MetaFrame for Windows setup, a Client Update Database is created thatcontains current Citrix ICA Clients. By default, the Update Database is configuredto update older client versions.

You can configure either a Client Update Database on each MetaFrame forWindows server in a server farm, or a single Client Update Database on a centralnetwork share. With a single database, you can configure updates once for allservers.

Use the ICA Client Update Configuration utility to:

• Create a new Client Update Database

• Set a default Client Update Database


• Configure database properties

• Add ICA Clients to the Update Database

• Remove ICA Clients from the Update Database

• Configure client update options

" To start the ICA Client Update Configuration utility

1. From a MetaFrame for Windows server: Click the Start button, point toPrograms, and then point to MetaFrame Tools (Citrix folder for MetaFrameXP). Click ICA Client Update Configuration.

2. The ICA Client Update Configuration window appears.

The location of the current Client Update Database is shown in the status bar.This is the database the server uses to update ICA Clients. The main windowshows the ICA Clients currently configured in the database.

Creating a New Client Update DatabaseThe default location of the Client Update Database is %SystemRoot%\Ica\Clientdb. A new database can be created on the local server hard drive or on ashared network drive. Multiple servers can be configured to use one shared ClientUpdate Database.

" To create a new Client Update Database

1. From the Database menu, click New. The Path for the New Client UpdateDatabase dialog box appears.

2. Enter a path for the new Client Update Database and click OK.

A new Client Update Database is created in the specified folder and the newdatabase is opened.

Setting a Default DatabaseAn existing Client Update Database can be used by multiple MetaFrame forWindows servers. If the Client Update Database is on a shared network drive, usethe ICA Client Update Configuration utility to configure all MetaFrame servers touse the shared database.

" To specify a new default database for one or more MetaFrame servers

1. From the Database menu, click Open. The Open Existing Database dialogbox appears.

2. Specify the path to the database that will be used as the default.


3. Click OK.

4. From the Database menu, click Set Default. The Set Default Database dialogbox appears.

5. Select the Set as Default Database on Local Machine check box to make thecurrently opened database the default database.

Tip You can also set other MetaFrame servers to use the currently opendatabase as the default database. Double-click on a domain name to view theservers in that domain. Click on a server to set its default database to thecurrently open database. You can select multiple servers by holding down theCTRL key.

6. Click OK.

Configuring the Properties of the Client Update DatabaseUse the Database Properties dialog box to configure the current Client UpdateDatabase.

" To configure the properties of the Client Update Database

On the Database menu, click Properties. The Database Properties dialog boxappears.

Clear the Enabled check box to disable this Client Update Database. ICA Clientsare not updated if the database is not enabled.

The Default update properties for clients options specify the default behavior forICA Clients added to the Update Database. If you change the properties of anindividual client in the database, those properties will override the defaultproperties.

• In Client Download Mode, click Ask user to give the user the option to acceptor postpone the client update. To notify the user of the client updaterequirement, click Notify user. Note that even if you select Notify user, userswho are logged on as administrators are still able to cancel the update.

To update the user’s ICA Client without notifying the user, click Transparent.Note that even if you select Transparent, users who are logged on asadministrators are still prompted to accept or postpone the client update.

• In Version Checking, click Update older client versions only to update onlyclient versions that are older than the new client. Click Update any clientversion to update all client versions to this version of the client. Use this optionto force an older client to replace a newer client.


• In Update Mode, select the Force Disconnection check box to require users todisconnect and complete the update. By default, users can choose whether todisconnect and complete the client update after the new client files aredownloaded.

• To force users to wait for all client files to download before continuing, clear theAllow background download check box. By default, users can choose whetherto download new client files in the background and continue working.

• To write an event in the event log when a ICA Client is updated, select the LogDownloaded Clients check box.

• By default, errors that occur during a client update are written to the event log.Clear the Log Errors During Download check box to turn off error logging.

• Specify the maximum number of simultaneous updates per MetaFrame server.When the specified number of client updates are occurring, new clientconnections are not updated. When the number of client updates drops belowthe specified maximum, new client connections are updated.

Adding and Removing Clients From the DatabaseUse the ICA Client Update Configuration utility to add ICA Clients to, and removethem from the database.

" To add a new ICA Client to the Client Update Database

1. From the Client menu, click New. The Description dialog box appears.

In Client Installation File, enter the path to the client installation file or clickBrowse.

The client installation file, Update.ini, is located in the root of the updatepackages.

2. After you specify the client installation file, the Client Name, Product, Model,Version, and icon of the selected client appear.

You can also modify the Comment used for this client. After making anychanges, click Next to continue. The Update Options dialog box appears.

3. The Update Options dialog box controls how the client update occurs. Theseoptions for each client override the settings specified for the database as a wholein the Database Properties dialog box.


• In Client Download Mode, click Ask user to give the user the option toaccept or postpone the client update. To notify the user of the client updaterequirement, click Notify user. Note that even if you select Notify user,users who are logged on as administrators are still allowed to cancel theupdate.

To update the user’s ICA Client without notifying the user, clickTransparent. Note that even if you select Transparent, users who arelogged on as administrators are still prompted to accept or postpone theclient update.

• In Version Checking, click Update older client versions only to updateonly client versions that are older than the new client. To update all clientversions to this version of the client, click Update any client version. Usethis option to force an older client to replace a newer client.

• By default, users can choose to disconnect and complete the client updateafter the new client files are downloaded. To require users to disconnect tocomplete the update, select the Force Disconnection check box.

• By default, users can choose to download new client files in the backgroundand continue working. To force users to wait for all client files to downloadbefore continuing, clear the Allow Background Download check box.

• You can optionally enter a message in Display this message on the userterminal. The user can view this message at the start of the client update byclicking More Info in the dialog box that appears.

Click Next to continue.

4. The Event Logging dialog box appears.

Auto Client Update uses the Windows event log to report status messages andupdate errors.

• Select the Log Downloaded Clients check box to write an event in theevent log when an ICA Client is updated.

• By default, errors that occur during a client update are written to the eventlog. Clear the Log Errors During Download check box to turn off errorlogging.

Click Next to continue.

5. The Enable Client dialog box appears.

The Client Update Database can contain multiple clients with the same product,model, and version information. However, only one client of each product,model, and version can be enabled. The enabled client is the one used for theauto client update.

Select the Enable check box to update ICA Clients to this client. All otherclients of the same product, model, and version are disabled.


6. Click Finish to copy the ICA Client installation files into the Client UpdateDatabase.

" To remove an ICA Client from the database

1. In Client Update Configuration, click on the ICA Client to remove.

2. From the Client menu, click Delete. A dialog box displays the selected clientinformation and asks for confirmation.

3. Click OK to remove the client. The ICA Client is now removed from thedatabase.

Changing the Properties of an ICA Client in the DatabaseUse the Properties dialog box to maintain the configuration of an ICA Client in theClient Update Database. The Properties dialog box contains four tabs: theDescription tab, the Update Options tab, the Event Log tab, and the Client Filestab.

" To modify the properties of an ICA Client in the database

1. In ICA Client Update Configuration, click on the ICA Client to modify.

2. From the Client menu, click Properties. The Properties dialog box appears.

• The Description tab displays information about the selected client. TheProduct, Model, Version, and Client Name are display-only fields.

Type a new description of the client in Comment.Select the Enabled check box to update ICA Clients to this client. All otherclients of the same product, model, and version are disabled.

The Client Update Database can contain multiple clients with the sameproduct, model, and version information. However, only one client of eachproduct, model, and version can be enabled. The enabled client is the oneused for the auto client update.


• The Update Options tab configures how the client is updated.

In Client Download Mode, click Ask user to give the user the option toaccept or postpone the client update. Click Notify user to notify the user ofthe client update requirement. Note that even if you select Notify user, userswho are logged on as administrators will be able to cancel the update.

Click Transparent to update the user’s ICA Client without notifying theuser. Note that even if you select Transparent, users who are logged on asadministrators are still prompted to accept or postpone the client update.

In Version Checking, click Update older client versions only to updateclient versions that are older than the new client. Click Update any clientversion with this client to update all client versions to this version of theclient. Use this option to force an older client to replace a newer client.

By default, users can choose whether to disconnect and complete the clientupdate after the new client files are downloaded. Select the ForceDisconnection check box to require users to disconnect and complete theupdate.

By default, users can choose whether to download new client files in thebackground and continue working. Clear the Allow BackgroundDownload check box to force users to wait for all client files to downloadbefore continuing.

You can optionally enter a message in Display this message on the userterminal. The user can view this message at the start of the client update byclicking More Info in the dialog box that appears.

• The Event Logging tab configures the events to log for the client update.

Auto Client Update uses the Windows NT event log to report statusmessages and update errors.

Select the Log Downloaded Clients check box to write an event in theevent log when an ICA Client is updated.

By default, errors that occur during a client update are written to the eventlog. Clear the Log Errors During Download check box to turn off errorlogging.

• The Client Files tab displays the individual files for the ICA Client.

The Client Update Database stores the File Name, Group, Flags, FileSize, andFile CRC for each file of a Citrix ICA Client.


Uninstalling the ICA Client

" To uninstall the ICA UNIX Client

1. Log on as root.

2. Run the setup program by typing /usr/lib/ICAClient/setupwfc and pressENTER.

— or —

If you installed the ICA Client to a different location, enter that path and pressENTER.

3. Type 2 and press ENTER to remove the ICA Client.

Using the UNIX ICA Client as an “ICA to X Proxy”(“Server Side ICA”)

You can use a workstation running the ICA Client as a server and redirect the outputto another X11-capable device. You may want to do this to deliver MicrosoftWindows applications to X terminals or to UNIX workstations for which an ICAClient is not available. Note that ICA Client software is available for many Xterminals and this is the preferred solution in these cases.

Note The ICA Client for Sun Solaris (SPARC) will run on Sun Ray devices.

When you run the ICA Client, you can think of the client as an ICA-to-X11converter that directs the X11 output to your local UNIX desktop. However, youcan redirect the output to another X11 display. This means that you can run multiplecopies of the ICA Client simultaneously on one workstation, with each sending itsoutput to a different device.


To set up this type of system, you need a UNIX server to act as the ICA-to-X11proxy.

• If you have X terminals already, you can run the ICA Client on the UNIX serverthat usually supplies the X applications to the X terminals.

• If you want to deploy UNIX workstations for which an ICA Client is notavailable, you will need an extra UNIX server to act the proxy. This can be a PCrunning Linux.

Server Sizing

If you want to use a PC running Linux to act as the proxy, you can use the followingexample as a guide when choosing a computer:

• Pentium 166 MMX (no L2 cache), 64MB RAM, Red Hat 6.1, SuSE 6.4,Slackware 7.0, Debian 2.2, and Caldera 2.4 (Higher versions should work.Other Linux distributions may also work.)

• Linux ICA Client Version 6.30

• Sessions directed to an IBM Netstation 100 running as an X terminal.

In tests, each ICA session used approximately 2.5MB of RAM on the Linux proxydevice. With six sessions, the running CPU load was 20-25% with each connectionrunning an “average user load” stress test. This indicates that a Pentium II 400 with128MB RAM could be expected to comfortably support 40 X11 sessions.


Supported FeaturesApplications are supplied to the final device using X11, using the capabilities of theICA protocol. By default, you can only use drive mapping to access the drives onthe proxy. This is not a problem if you are using X terminals (which usually do nothave local drives). If you are delivering applications to other UNIX workstations,you can either:

• NFS mount the local UNIX workstation on the workstation acting as the proxy,then point a client drive map at the NFS mount point on the proxy.

• Use an NFS-to-SMB proxy such as SAMBA, or an NFS client on theMetaFrame server such as Interdrive NFS.

• Some features will not be passed to the final device:

• Audio will not be delivered to the X11 device, even if the server acting as aproxy supports audio.

• Client printers are not passed through to the X11 device. You will need tomount the UNIX printer on the MetaFrame server manually using LPDprinting, or use a network printer.

Starting the ICA Client with “Server Side ICA”

" To start the ICA Client session from an X terminal or a UNIX workstation

1. Telnet to the device acting as the proxy.

2. In a shell on the local device, set the DISPLAY environment variable to thelocal device. For example, in a C shell, type:setenv DISPLAY <local:0>

3. At a command prompt on the local device, type:xhost <proxy server name>

4. If the ICA Client has not been installed in the default installation directory,ensure that the environment variable $ICAROOT is set to point to the actualinstallation directory.

5. Locate the directory where the ICA Client is installed. At the command prompt,type:wfcmgr &

Note If you get font errors on the local X display when you start the ICA Client,start the font server on the proxy server — on Linux just type xfs &; on Solaris typexfs –port fs.

C H A P T E R 3

Configuring the Citrix ICA UNIXClients

OverviewThis chapter describes how to configure the Citrix ICA UNIX Client. Topics in thischapter include:

• Creating a connection entry

• Mapping client devices

• Changing a connection entry

• Changing the default settings

• Using xcapture

• Improving security

Creating a Connection EntryYou can create two types of connections to MetaFrame servers: ICA connectionsand published applications.

• An ICA connection lets a user access the desktop of a MetaFrame server. Theuser can run any applications available on the desktop, in any order.

• A published application is a predefined application and its associatedenvironment. Published applications can also be run in seamless mode, wherethe applications appear to the client as if they are running locally, eachapplication running in its own resizable window.


" To create a connection entry

1. Start the ICA Client. From the Entry menu, click New, or click the New icon onthe toolbar. The Properties dialog box appears with the Network pagedisplayed.

Note You can copy an existing entry by highlighting the required entry and thenchoosing Copy from the Entry menu. You can then edit the copied entry asrequired. This is useful if many of the configuration details are the same for bothentries

2. Click Server or Published Application.

3. For a server connection, type the name or IP address of the MetaFrame server orselect the name from the pop-up menu to the right of the Server field.

— or —

For a published application, type the name of the published application or selectthe name from the pop-up menu to the right of the Server field.

Chapter 3 Configuring the Citrix ICA UNIX Clients 41

4. If you have typed the name of the MetaFrame server or published application, inthe Description field, type a unique description for the entry. The description isused to identify the connection in the Citrix ICA Client window.

If you have selected a server or published application from the pop-up menu, adefault description is automatically added.

5. Click OK to save the entry or Cancel to exit the Properties dialog box withoutsaving the entry.

Note To save your changes but retain the current page, click Apply.

When you have created a connection entry with the appropriate network connectionproperties set up, the description appears in the main ICA Client window.

Note This is the simplest way to create a connection entry. When you follow thesesteps, you set the essential items you need to connect to the MetaFrame server fromthe workstation. You can change some of the other properties for a connection; forexample, the window size or color settings. See “Changing the Window Properties”on page 59.

Enabling Smart Card SupportThe ICA UNIX Client offers support for a number of smart card readers. If smartcard support is enabled on both the server and client, you can use smart cards for thefollowing purposes:

Smart card login authentication. Use smart cards to authenticate users toMetaFrame XP servers.

Smart card application support. Allow smart card-aware published applicationsto access local smart card devices.

For more information on configuring smart card support on your servers, see theMetaFrame Administrator’s Guide.

Smart card support has the following prerequisites:

• Your smart card readers and published applications must be PC/SC industrystandard compliant

• You must install the appropriate driver for your smart card reader

• You must install the PC/SC Lite package (including the Resource Managerdaemon and shared library), available for download from www.linuxnet.com


Note Smart card data is security-sensitive, and should be transmitted over a secureauthenticated channel such as SSL/TLS.

" To configure smart card support

1. In the ICA Client main window, either click New from the Entry menu toconfigure a new connection or select the existing connection entry you want toconfigure.

2. From the Entry menu, click Properties. From the drop-down list, click Loginto display the Login page.

3. Click the Allow Smart Card Logon button.

4. Click OK.

Note Auto client reconnect works in the same way regardless of whether a userhas logged on conventionally or with a smart card. Users who log in to aMetaFrame session using a smart card will be automatically reconnected shouldtheir session fail and will not have to reenter their PIN number, provided that theirsmart card remains in the smart card reader. However, Roaming User Reconnect isnot supported for connections that use smart card authentication.

Opening a ConnectionYou can connect to a MetaFrame server session from the main ICA Client window,directly from the UNIX prompt, or from a Web browser to a MetaFrame server viathe Internet.

" To open a connection from the main ICA Client window

• Double-click the name of the Connection Entry that you want to open in theCitrix ICA Client window. Alternatively, select the name of the connectionentry and click Connect from the Entry menu or click the Connect icon.

" To open a connection from the command line

• Type the following command at the UNIX prompt:/usr/lib/ICAClient/wfica -desc “description”

where description is the full text from the Description field of the connectionentry. If the description contains spaces, these will need to be quoted in thestandard manner for UNIX.


Note If you cannot connect to a MetaFrame server you may need to change theserver location or SOCKS proxy details. See “Configuring Server Location andBusiness Recovery” on page 66 and “Connecting Through a Proxy Server” onpage 72 for details.

" To open a connection using a Web browser

If you are using Netscape Navigator, Web browser configuration to enable CitrixICA session connection is normally carried out automatically during installation.

If you need to set up mailcap and MIME files for Netscape Navigator manually,use the following file modifications so that .ica files start up the ICA Clientexecutable, wfica. (To use other browsers, you will need to modify the .mailcapand MIME files accordingly.)

The .mailcap file modification is:

• In $HOME, create or modify the .mailcap file and add the line:

• For Version 3.0 Citrix ICA for UNIX Clients:

application/x-ica; wfica %s

• For Version 6.0 and later Citrix ICA for UNIX Clients:application/x-ica; /usr/lib/ICAClient/wfica -file %s; x-mozilla-flags=plugin:Citrix ICA

The application wfica must be in the path. The %s indicates that the fullfilename of the .ica file is passed to the application. The additional text in theVersion 6.0 mailcap file is to make use of the Netscape Citrix Client plug-in.

For Version 3.0 Citrix ICA for UNIX Clients only, the mime file modification is:

• In $HOME, create or modify the .mime.types file and add the line:application/x-ica ica

The x- in front of the format ica indicates that ica is an unofficial MIME typenot supported by the Internet Assigned Numbers Authority (IANA).

Mapping Client DevicesThe Citrix ICA UNIX Clients support client device mapping for connections toMetaFrame for Windows servers. Client device mapping allows a remoteapplication running on the MetaFrame server to access printers and disk drivesattached to the local client computer. The applications and system resources appearto the user at the client workstation as if they are running locally. Ensure that clientdevice mapping is supported on your MetaFrame server before using these features.


Note Client device mapping, except printers, is not supported when connecting toCitrix MetaFrame for UNIX Operating Systems 1.0 and 1.1. Client printer mappingand, with hotfix 2, client drive mapping are supported when connecting to Version1.1, Feature Release 1.

This section includes more information about:

• Mapping COM ports

• Mapping client drives

• Mapping client printers

• Mapping client audio.

Mapping COM PortsYou can perform bi-directional mapping of serial devices on the client machine (forexample, /dev/ttyS0 on Linux) to MetaFrame server COM ports. This allows a userat the client workstation to use local devices like modems, serial printers, and bar-code scanners seamlessly from the applications running on the MetaFrame server.

" To configure COM port mapping

1. In the Citrix ICA Client window, click the Option menu and then clickSettings.

2. In the Settings dialog box, select COM Ports from the pull-down menu.

3. Click Add to map a COM port.

Mapping Client DrivesClient drive mapping makes any directory mounted on the ICA Client workstation,including CD-ROMs, available to the user during ICA sessions on MetaFrameservers. When a MetaFrame server is configured to allow client drive mapping,users can access their locally stored files, work with them during their ICA sessions,and then save them again either on a local drive or on a drive on the MetaFrameserver.

You can control drive mapping at the MetaFrame server, in the Client Settingsdialog box in Citrix Connection Configuration. Use the Connection settings tospecify the devices to automatically map at login. You can also use the ClientMapping Overrides to allow a user to control the device mapping from the clientworkstation during ICA Client sessions, in the Drive Mapping dialog box. Use thisdialog box to specify which folders and drives to map at login. This applies for allconnection sessions.


" To specify the drives and directories to automatically map during login

1. In the Citrix ICA Client window, click Option and then click Settings. In theSettings dialog box, select Drive Mapping from the pull-down menu:

For each MetaFrame server drive letter, the Drive Mapping list shows the diskor pathname of the UNIX directory mapped to the drive. In the Enable/Read/Write columns, icons display whether each mapped drive is enabled for use andwhat type of access the user will have to the drive.

2. Click the check box in the Enable column next to an available drive letter andthen click in the field for the drive.

3. Click Modify. A standard UNIX file selection dialog box appears. Select theUNIX directory you want to map and click OK. Alternatively, you can simplytype the directory path into the field next to the required drive letter.

4. The mapped directory appears in the Drive Mapping list. If the drive letter youselected is not available on the MetaFrame server, the specified directory ismapped to another free drive letter at login.


5. Specify the access for the drive by clicking the corresponding read/write icons.You can use:

6. Make sure Enable Drive Mapping is selected. Click OK. Log off any ICAconnections already established and reconnect. The same drive mapping andaccess settings will apply to all connection entries.

" To view mapped client drives when connected to a MetaFrame for Windowsserver

1. From within the ICA Client session, double-click My Computer on the remotedesktop. The My Computer screen appears:

When connected to published applications, users can access local drives in the sameway they would when running applications locally.

" To manually map a client drive on a MetaFrame server

Mapped drives that do not appear after login can be manually mapped fromwithin an ICA session. Use the following procedure to manually map a clientdrive.

1. In the Citrix ICA Client window, double-click on a connection entry and log into the MetaFrame server.

Icon Meaning

Read access

Prompt for read access on first access per session

No read access

Write access

Prompt for write access on first access per session

No write access


2. On a MetaFrame for Windows server, start Windows Explorer. From the Toolsmenu, click Map Network Drive. The Map Network Drive dialog boxappears.

3. In the Drive field, select a server drive letter. This drive letter will represent themapped client drive.

4. From the Shared Directories list, double-click Client Network, Client, andthen select the appropriate icon for your UNIX directory from the list ofavailable client drives.

5. If you want to have this drive available to you each time you log in to thisserver, check Reconnect at Logon. Click OK.

" To configure drive mapping for floppy disks

You can map floppy drives on servers for access within an ICA session. Use thefollowing procedures to manually map floppy drives.

SGI IRIX: DOS formatted floppies mounted automatically by mediad can beaccessed in the same way as any other drive. Files can only be accessed through the8.3 filename convention.

Sun Solaris: On Solaris 2.5.1 or later, DOS formatted floppies mounted on yourUNIX workstation can be accessed, either automatically using vold, or by using thevolcheck utility. For details on vold and volcheck, and whether your version ofSolaris supports them, see your workstation documentation.

On SunOS 4.1.4 two scripts are provided so DOS formatted floppies mounted onyour UNIX workstation can be accessed. The scripts are located in the clientinstallation directory and are called:

• mntfloppy - used to mount floppy disks

• umntfloppy - used to unmount floppy disks

The scripts are owned by root, but can be run by any user. They use a floppy diskdevice name of /dev/fd0 and mount the floppy disk to /pcfs. To change thesesettings, log in as root and edit the script file.

Long filenames are not supported, so save files using the 8.3 filenamingconvention.

IBM AIX: DOS formatted floppies mounted on your UNIX workstation can beaccessed using dosread, doswrite, dosdir, dosformat and dosdel utilities. Fordetails, see your workstation documentation.

HP-UX: DOS formatted floppies mounted on your UNIX workstation can beaccessed using doscp, dosls, dosdf, dosmkdir, dosrm, doschmod, dos2ux andux2dos utilities. For details, see your workstation documentation.


SCO UnixWare or OpenServer: DOS formatted floppies mounted on your UNIXworkstation can be accessed using the following command:mount -f dosfs /dev/fd0 /floppy

Then select the /floppy directory in the Drive Mapping dialog box.

Linux: DOS formatted floppies mounted on your UNIX workstation can beaccessed using the following command:mount -t vfat /dev/fd0 /mnt/floppy

Then select the /mnt/floppy directory in the Drive Mapping dialog box.

Mapping Client PrintersClient printer mapping lets users access spooled printers available to theworkstation from within ICA sessions. When a MetaFrame server is configured toallow client printer mapping, applications running remotely on the MetaFrameserver can print to a spooled printer.

You can set a default printer to be available automatically when an ICA session isstarted, and which is removed upon session termination. This is known as an auto-created printer. Published applications often rely on auto-created printers to provideaccess to a printer as print management utilities may not be available from theapplication itself.

Note Auto-created printers are not used on MetaFrame for UNIX, however, theclient’s default printer is.

This section describes how to limit the number of printers available to clients. Thisis useful where there are many printers available and avoids delays when listingavailable printers. It also describes how to set a default auto-created printer. Theprinter used by the system is the default (auto-created) sought in the configurationfile. If none is set, the UNIX environment variables are searched for defaultprinters, otherwise, the default for the client machine print setup is used. Thesystem default printer can be overridden by the LPDEST or PRINTERenvironment variable in HP-UX, Solaris and AIX, and the PRINTER environmentvariable on Linux.

" To limit mapped client printers

A limited list of printers configured on the client and mapped for use from an ICAsession.

1. Open the configuration file, wfclient.ini, in the:

• $HOME/.ICAClient directory to apply the auto-created printer for a singleuser.

— or —


• $ICAROOT/Config directory to apply the auto-created printer to all clients— all clients being those to first use the wfcmgr program after the change.

2. In the [WFClient] section of the file type:ClientPrinterList=PrinterName1:PrinterName2:PrinterName3

Where PrinterName1, PrinterName2 etc. is the name for the chosen printer.Separate printer name entries by a colon (:).

3. Save and close the file.

" To set a default auto-created printer

The printer configured on the client for auto-creation. (Auto Created Clientprinter) is displayed after the printer that is the default.

1. Open the configuration file, wfclient.ini, in the:

• $HOME/.ICAClient directory to apply the auto-created printer for a singleuser

— or —

• $ICAROOT/Config directory to apply the auto-created printer to all clients— all clients being those to first use the wfcmgr program after the change.

2. In the [WFClient] section of the file type:DefaultPrinter=PrinterName

DefaultPrinterDriver=PrinterDriverName

Where PrinterName is a name for the chosen printer and PrinterDriverName isthe name of the Microsoft Windows driver for the printer.


Note An auto-created printer configuration can be stored on the client machine byrenaming it in the print management utility.

Mapping Client Printers on MetaFrame for WindowsThis section describes how to map client printers in the Windows environment.

" To map a local printer on a MetaFrame for Windows server

1. From the UNIX workstation, start an ICA connection and log in to theMetaFrame server.

2. Click Start on the taskbar, point to Settings, then click Printers.


3. In the Printers window, you will see an icon for a network printer with a namesimilar to workstation#printer, where workstation is the UNIX workstationname and printer is the UNIX name for the printer.

4. If no client printer is available, double-click Add Printer. The Add PrinterWizard appears.

5. Use the Wizard to add a network printer from the Client Network, Clientdomain with a name similar to workstation#printer.

See your Windows operating system documentation for more information onadding printers.

Mapping Client Printers on MetaFrame for UNIXBefore users can print to a client printer from MetaFrame for UNIX, printing mustbe enabled by the administrator. This section describes how to enable printing onthe server. It describes how users can list available client printers and print filesfrom the command line or from applications.

In a UNIX environment, the application performs the print rendering. The printerdriver is specified inside the application or, in the case of a desktop utility, raw textis generated.

Note For further information about printing on MetaFrame for UNIX OperatingSystems, see the MetaFrame Administrator’s Guide and the manual pages.

Setting up Printing

" To check if client printing is currently enabled or disabled

1. Log on to the MetaFrame server as a MetaFrame server administrator.

2. At the command prompt, type:ctxcfg -p list

" To enable or disable client printing

1. Log on to the MetaFrame server as a MetaFrame server administrator.

2. At the command prompt:

To Use the command

Enable client printing ctxcfg -p enable

Disable client printing ctxcfg -p disable


" To display mapped client printers

1. At the command prompt, type:ctxprinters

A list of printers configured on the client and mapped for use from the ICA sessionis displayed, (default) is displayed after the printer that is the default. The followinginformation is shown for each printer:

• Printer name or printer port (for example, lpt1). This can be used in thectxlpr -P command to specify a printer other than the default.

• Printer driver name. This is for information only.

• Printer connection description. This is for information only.

Using Printing

" To print a file from an ICA Client session

1. At the command prompt, type ctxprinters.

2. From the results of ctxprinters, identify the printer or printer port that you wantto use. To print to a printer other than the default, note the printer name—theprinter name is the first item in the ctxprinters listing.

3. At the command prompt:

To Use the command

Print the file named filename to the default printer. ctxlpr filename

Print a series of files to the default printer. Each file is treatedas a separate print job.

ctxlpr filename filename

Print a file to a printer (or printer port) other than the default.This is the printer name or printer port shown in the first columnof the output from ctxprinters.

ctxlpr -P [Printername |Printerport] filename

Print a file in the background. ctxlpr -b filename

Print a file only if the printer is not in use. Use this option to stopan application waiting while other printer jobs are handled. Ifthe printer is in use, an error message is displayed.

ctxlpr -n filename


To print from applicationsThe exact configuration of how to set up printing from applications depends on thebehavior and user interface of the UNIX application.

If the user interface for an application allows you to specify the actual printercommand to use when printing, you can configure client printing by replacing thelpr or lp command with the ctxlpr command.

When a user connects to the server and prints from the application in a session, theserver redirects the output to the mapped client printer.

Often, in this type of application, you can also specify the command line modifierson a different line. You can use the same switches for ctxlpr as when printing fromthe command line. For example, use -P with a printer name (or printer port) to printto a printer other than the default; use -b for background printing, and so on.

Tip If the user interface of an application does not allow you to specify the actualprinter command to use when printing, determine if the application (or windowmanager) uses a configuration file where you can replace the lpr commandfunctionality with ctxlpr.

Mapping Client AudioClient audio mapping enables applications running on the MetaFrame server to playsounds through a sound device installed on the client computer.

An administrator can set the audio quality or enable/disable client audio mappingon the MetaFrame server. A user can set the audio quality or enable/disable clientaudio mapping for an entry from the client workstation. If the client and serveraudio quality settings are different, the lower of the two qualities is used.

Client Audio Quality options are:

• High. This setting is recommended only for connections where bandwidth isplentiful and sound quality is important. This setting allows clients to play asound file at its native data rate. Sounds at the highest quality level require about1.3Mbps of bandwidth to play clearly. Transmitting this amount of data canresult in increased CPU utilization and network congestion.

• Medium. This setting is recommended for most LAN-based connections. Thissetting causes any sounds sent to the client to be compressed to a maximum of64Kbps. This compression results in a moderate decrease in the quality of thesound played on the client computer. The host CPU utilization will decreasecompared with the uncompressed version due to the reduction in the amount ofdata being sent across the wire.


• Low. This setting is recommended for low-bandwidth connections, includingmost modem connections. This setting causes any sounds sent to the client to becompressed to a maximum of 16Kbps. This compression results in a significantdecrease in the quality of the sound. The CPU requirements and benefits of thissetting are similar to those of the Medium setting; however, the lower data rateallows reasonable performance for a low-bandwidth connection.

" To enable or disable ICA Client audio on a MetaFrame for Windows server

1. Click ICA Settings in Terminal Server Connection Configuration.

2. Select an option from the Client Audio Quality drop-down list.

" To configure audio mapping for a connection entry

1. In the ICA Client main window, select the name of the connection you want.

2. Click Properties from the Entry menu, or click the Properties button. TheProperties dialog box shows the current properties of the selected connection.

3. In the Properties dialog box, select Connection from the pull-down menu.

4. Select Enable Sound to enable sound support. Select High, Medium, or Lowquality depending on the available bandwidth.

Note Client audio mapping is not supported by Version 3.0 of the ICA Client forSGI IRIX, Compaq Tru-64, Sun OS, Sun Solaris (x86), and SCO.

Changing a Connection EntryThis section describes how to change properties for an existing connection entry.

" To change the properties for a connection entry

1. From the Citrix ICA Client window, select the connection entry that you want tochange.

2. From the Entry menu, click Properties. The Properties dialog box has pagescorresponding to the properties you can control, including:

• The Network page, where you can change the settings required to establisha connection with the MetaFrame server. See “Configuring NetworkProperties” on page 54.

• The Connection page, where you can control the connection between theMetaFrame server and client workstation; for example, to improveperformance by reducing bandwidth. See “Improving Performance over aLow-Bandwidth Connection” on page 55.


• The Firewall page, where you can specify proxy server settings. See“Connecting Through a Proxy Server” on page 72.

• The Application page, where you can specify an application to run whenyou connect the MetaFrame server. See “Specifying an Application to Runat Connection” on page 58.

• The Window page, where you can specify the window size and number ofcolors used for the ICA session. See “Changing the Window Properties” onpage 59.

• The Login page, where you can specify your login details so that you do nothave to type them each time you connect to a MetaFrame server. See“Configuring Login Properties” on page 61.

• The Auto-reconnect page, where you specify settings for auto clientreconnection. See “Configuring Auto Client Reconnect” on page 64

Configuring Network PropertiesUse the Network page in the Properties dialog box to specify a connection with aMetaFrame server and the network protocol to use.

" To change the network properties for a connection entry

1. From the main ICA Client window, select the connection entry that you want tochange.

2. From the Entry menu, click Properties.

3. From the Properties dialog box, select Network from the drop-down list todisplay the Network page:

4. Adjust the properties as required:

• Enter a description of the connection in the Description field.

• Click Server to configure a connection to a MetaFrame server. ClickPublished Application to configure a connection to a publishedapplication. You can specify a server either by its name or its IP address.Click the … button (“browse”) to get a list of Servers or PublishedApplications.

• Click Network Protocol to change the protocol used when locating the ICAmaster browser. If a firewall restricts UDP messages, selectTCP/IP+HTTP from the list. In Version 6.20 and later of the ICA UNIXClient, TCP/IP+HTTP is the default setting. For more information onnetwork protocols, see “Configuring Network Protocol” on page 66


Improving Performance over a Low-BandwidthConnectionIf you are using ICA over a low-bandwidth connection, such as a modem or cellulartelephone, there are a number of changes that you can make to your clientconfiguration and the way you use the client to improve performance.

• Change your ICA Client configuration — Changing your clientconfiguration, as described below, can reduce the bandwidth that ICA requiresand improve performance

• Change the way you use the client — Changing the way you use the client canalso reduce the bandwidth required for a high-performance connection

• Use the latest MetaFrame server and ICA Clients — Citrix is continuallyenhancing and improving ICA performance with each release, and manyperformance features require the latest client and server software in order tofunction


Changing your ICA Client ConfigurationOn devices with limited processing power, or where limited bandwidth is available,there is a trade-off between performance and functionality. The ICA Client providesboth user and administrator with the ability to choose an acceptable mixture of richfunctionality and interactive performance. Making one or more of these changescan reduce the bandwidth that your connection requires and improve performance.

Enable the Bitmap Cache

Bitmap caching stores commonly-used bitmaps (images) locally on your client sothat they do not have to be transferred over the ICA connection every time they areneeded.

" To enable bitmap caching

1. From the ICA Client window, select the connection entry that you want tochange.

2. From the Properties page, select Connection from the drop-down list todisplay the Connection page.

3. Select Use Disk Cache for Bitmaps. Click OK.

Note You can enable or disable bitmaps for each connection entry so that you cancontrol the connection to each MetaFrame server. Note that only one physical cacheis used for all connection sessions that are enabled. See “Changing Settings for theDisk Cache” on page 62.

Data Compression

Data compression reduces the amount of data transferred across the ICA session.This requires additional processor resources to compress and decompress the data,but it can increase performance over bandwidth-limited connections.

" To enable data compression



3. Select Use Data Compression to reduce the amount of data transferred acrossthe ICA session.


SpeedScreen Latency Reduction

SpeedScreen Latency Reduction improves performance over high latencyconnections by providing instant feedback to the user in response to typed data ormouse clicks.

Note SpeedScreen Latency Reduction will work only when it is available on theMetaFrame server you are connecting to and has been enabled. See yourMetaFrame server documentation for more details.

" To change SpeedScreen settings



3. In the SpeedScreen section there are two list boxes, Local Text Echo andMouse Click Feedback. Local Text Echo accelerates display of the input text,effectively shielding you from experiencing latency on the network. MouseClick Feedback provides visual feedback of a mouse click, in that the mousepointer is immediately changed to an hourglass indicator. Select a mode fromthe drop-down list:

• For slower connections (for example if you are connecting over a WAN or adial-in connection), set mode to On to decrease the delay between user inputand screen display.

• For faster connections (for example, if you are connecting over a LAN), setmode to Off.

• If you are not certain of the connection speed, set the mode to Auto to turnSpeedScreen on or off depending on the latency of the connection. You canoverride Auto mode using the Toggle SpeedScreen hotkey.

Note Local text echo does not support input using IME.

Reduce the Window Size

Change the window size to the minimum you can comfortably use. See“Configuring Default Window Settings” on page 64 for more information.

Reduce the Number of Colors

Reduce the number of colors to 256. See “Configuring Default Window Settings”on page 64 for more information.


Reduce Sound Quality

If you are using sound, reduce the sound quality to the minimum setting or disableclient audio mapping. See “Mapping Client Audio” on page 52 for moreinformation.

Changing the Way You Use the ClientICA technology is highly optimized and typically does not have high CPU andbandwidth requirements. However, if you are using a very low-bandwidthconnection, you should consider the following to preserve performance:

• Avoid accessing large files using client drive mapping. When you access alarge file with client drive mapping, the file is transferred over the ICAconnection. On slow connections, this may take a long time.

• Avoid printing large documents on local client printers. When you print adocument on a local client printer, the print file is transferred over the ICAconnection. On slow connections, this may take a long time.

• Avoid playing multimedia content. Playing multimedia content uses a lot ofbandwidth and can cause reduced performance.

Specifying an Application to Run at ConnectionUse the Application page in the Properties dialog box to specify an application torun when you connect using the connection entry. If you specify an application, youdo not see the MetaFrame server desktop when you connect and the connection isclosed when you quit the application.

" To specify an application to run at connection


2. From the Properties page, select Application from the drop-down list todisplay the Application page:


• In the Application field, you can specify the pathname of an application tobe run after connecting to a MetaFrame server.

• In the Working Directory field, you can specify the pathname of adirectory to be used with the application.

Note If the entry you are configuring is a connection to a published application,the Application dialog box will not be available.

Changing the Window PropertiesUse the Window page to change the window size and number of colors used for aparticular connection.

" To configure the window properties

1. Select the connection entry you want to change.


2. From the Properties page, select Window from the drop-down list to displaythe Window page.

• Window Size allows you to select from Fixed Size, Percentage of ScreenSize, or Full Screen. Selecting Fixed Size or Percentage and type the size(in pixels) or percentage in the Window Size boxes. If you are connecting toa published application you can also select Seamless. Seamless integrateslocal and remote windows on the desktop.

Note Because the UNIX Client supports seamless windows natively, it is notnecessary to use "pass-through" mode. Pass-through mode is intended tofacilitate seamless windows for ICA Clients that do not support seamlesswindows natively, and should only be used from a fixed-size window session onthe client device. Please note that "seamless within seamless" (that is, seamlesswindows via pass-through mode) is not a supported configuration for the UNIXClient.


• Window Colors allows you to set the number of window colors to 16, 256,32 Thousand, or 16 Million. Your display must be capable of displaying theresolution and color depth you select. You can only specify a color depthgreater than 256 colors on Version 6.0 and later clients.

• 256 Color Mapping allows you to set up 256 color sessions to useapproximate or exact colors. Use Shared - Approximate Colors toeliminate color flashing when switching context. Note that if otherapplications have allocated all 256 colors, the client will use a privatecolormap.

• In each case, select Use Default to use the default window size or windowcolors setting. For more information about setting defaults, see “ConfiguringDefault Window Settings” on page 64.

Configuring Login PropertiesThe Login page allows you to enter login details of your ICA connection so thatyou do not need to type them in each time you connect.

" To configure login properties

1. From the Citrix ICA Client window, select the connection entry that you want tochange.

2. From the Properties page, select Login from the drop-down list to display theLogin page.

3. Type your Username, Domain (optional), and Password for the connection. Toenable smart card login, select Allow Smart Card Logon. For moreinformation on using smart cards with the ICA Client, see “Enabling SmartCard Support” on page 41.

Changing Default SettingsThis section describes how to change settings that apply for all connection entrieson the workstation.

It also describes how to change the default settings that are used when you create anew connection entry. You may want to do this if you prefer to use a particularsetting; for example, a window size that is different from the suggested setting.

" To change the default settings

1. Display the Citrix ICA Client window.

2. From the Option menu, click Settings. The Settings dialog box has pagescorresponding to the properties you can control, including:


• The Server Location page, where you can specify the server address for theMetaFrame server that will report the master browser. See “ConfiguringServer Location and Business Recovery” on page 66.

• The Hotkeys page, where you can define alternative key combinations forsystem hotkeys. See “Configuring Hotkeys” on page 68.

• The Window page, where you can specify the settings to use for all newconnection entries. See “Configuring Default Window Settings” on page 64.

• The Disk Cache page, where you can define settings for the disk cache. See“Changing Settings for the Disk Cache” on page 62.

• The Drive Mappings page, where you can set up drive mappings.See“Mapping Client Devices” on page 43.

• The COM Ports page, where you can configure COM port mapping. See“Mapping COM Ports” on page 44.

• The Preferences page, where you can control other settings that apply to allconnection entries. See “Configuring Preferences” on page 69.

• The Firewall settings page, where you can configure firewalls and aSOCKS proxy. See “Integrating the ICA UNIX Client with SecuritySolutions” on page 72.

• The Auto Reconnect page, where you specify settings for auto clientreconnection. See “Configuring Auto Client Reconnect” on page 64

Changing Settings for the Disk CacheUse the Disk Cache page in the Settings dialog box to control the location, size,and contents of the disk cache.

Note The disk cache is used only if it is enabled for a particular connection. See“Improving Performance over a Low-Bandwidth Connection” on page 55 fordetails.

" To adjust the settings for the disk cache

1. From the Option menu, click Settings.

2. From the Settings dialog box, select Disk Cache from the drop-down list. Thisdisplays the Disk Cache page:


• To set the maximum size of the cache, adjust the Amount of disk space touse slider to show a percentage of the disk, or type in the maximum size youwant to allow.

• To change the location of the cache, set the Disk Cache Directory asappropriate by clicking the Change button and browsing to your desiredlocation. If you change the location of a cache on a workstation, make surethat you clear the old cache first.

• To set the minimum size of bitmaps to cache, adjust the The minimum sizebitmap that will be cached is slider. The size setting is displayed next tothe slider.

• To clear the cache, click the Clear Cache Now button. Citrix does notrecommend that you clear the cache if any ICA connections are open.Before clearing the cache, verify that all ICA connections are closed.

Note An administrator can view information about the bitmap cache settings foran ICA connection using the Cache tab in Citrix Server Administration. See yourserver documentation for more details.


Configuring Default Window SettingsUse the Window page in the Settings dialog box to set up the default windowsettings for all new connection entries.

These settings are used as the default for all new connections. If you want to changethe window settings for a specific connection, see “Changing the WindowProperties” on page 59.

" To configure the default window settings

1. Select Window from the drop-down list on the Settings dialog box to displaythe Window page.

2. Adjust the settings as required, for example:

• Window Size allows you to select from Fixed Size, Percentage of ScreenSize, or Full Screen.

• Window Colors allows you to set the number of window colors to 16, 256,32 Thousand, or 16 Million. Before selecting a new color mode, ensurethat it is supported on your machine. You can only specify a color depthgreater than 256 colors on Version 6.0 and later clients.

• 256 Color Mapping allows you to set up 256 color sessions to useapproximate or exact colors. Use Shared - Approximate Colors to eliminatecolor flashing when switching context. Note that if other applications haveallocated all 256 colors, the client will use a private colormap.

Configuring Auto Client ReconnectICA sessions can be dropped because of unreliable networks, highly variablenetwork latency, or range limitations of wireless devices.

The Auto Client Reconnect feature is triggered when the ICA Client detects adisconnected session. When this feature is enabled on a MetaFrame XP server,users do not have to reconnect manually or reenter login credentials to continueworking. Automatic reconnection does not occur if users exit applications withoutlogging off.

When a reconnection sequence begins, the user is informed that the client willreconnect after a set interval. Reconnection requires no action by users, althoughthey can choose to cancel the process or reconnect immediately. Because sessiondrops may be caused by network instability, users should wait a few momentsbefore reconnecting to give the network time to recover from the problem thatcaused the disconnection.


Auto client reconnect incorporates a re-authentication mechanism based onencrypted user credentials. When a user initially logs in to a server to use anapplication, MetaFrame XP encrypts and stores the user credentials in memory, andsends the encryption key to the ICA Client. For reconnection, the client submits thekey to the server. The server decrypts the credentials and submits them to Windowslogin for authentication.

Auto client reconnect is enabled on the ICA Linux Client by default. When the ICAClient detects that its connection to the server is unexpectedly broken, it waits 30seconds before beginning the reconnection sequence. By default, the ICA Clientattempts to reconnect three times and then, if unsuccessful, it stops.

There is no configuration required on the client machine to use these defaultsettings.

" To change the auto client reconnection default settings

1. Click the Option menu and choose Settings.

2. From the drop-down list, click Auto Reconnect.

3. Select Enable Auto Reconnect and enter values for Maximum Retries andSeconds Delay Before Retrying Reconnect.

4. Click OK.

" To change the auto client reconnection settings for a connection entry

1. From the main ICA Client window, select the connection entry that you want tochange.


3. From the drop-down list, click Auto Reconnect.

4. Select Enable Auto Reconnect and, if required, enter values for MaximumRetries and Seconds Delay Before Retrying Reconnect.

5. Click OK.

Note Auto client reconnect works in the same way regardless of whether a userhas logged on conventionally or with a smart card. Users who log in to aMetaFrame session using a smart card will be automatically reconnected shouldtheir session fail and will not have to reenter their PIN number, provided that theirsmart card remains in the smart card reader.


Configuring Network ProtocolThe network protocol setting allows you to control the way the ICA client searchesfor MetaFrame servers and how it communicates with them.

" To configure a default network protocol

1. In the main ICA Client window, select Settings from the Option menu.

2. From the drop-down list, select Server Location.

3. Click the Network Protocol drop-down list to display a list of availableprotocols.

4. Select your required network protocol and click OK.

The default protocol for Versions 6.20 or later of the ICA Clients for UNIX isTCP/IP+HTTP. For earlier versions, the default protocol is TCP/IP.

Configuring Server Location and Business RecoveryServer location (also called server browsing) provides a method for a user at anetwork-connected Citrix ICA Client to view a list of all MetaFrame servers on thenetwork that have ICA connections configured for that network protocol, or a list ofall published applications. You can specify a separate server location for eachnetwork protocol.

The way in which server location works depends on which network protocol hasbeen configured:

TCP/IP+HTTP and SSL/TLS+HTTPS — The default server address isica.domainname, where domainname is a TCP/IP domain name.The ICA Clientuses the HTTP or HTTPS protocol respectively to contact the MetaFrame servers.TCP/IP+HTTP is supported in Version 6.0 or later of the ICA Clients for UNIX;SSL/TL+HTTPS is supported in Version 6.30.

TCP/IP — The default setting for server location is auto-locate. The ICA Clientattempts to contact all of the servers on the subnet by broadcasting on the UDPprotocol. Alternatively, you can set specific addresses for MetaFrame servers.

Business recovery provides consistent connections to published applications in theevent of a master ICA browser server disruption. You can define up to three groupsof MetaFrame servers to which you want to connect: a primary and two backups.Each group can contain from one to five servers. When you specify a server groupfor your client, the client attempts to contact all the servers within that group andthe first server to respond passes its master browser address to the client.

Server Location can be configured globally.


" To configure server location and business recovery

1. From the Settings page, select Server Location from the drop-down list todisplay the Server Location page:

2. Select the required network protocol from the drop-down list.

3. Click Add to display the Add Server Location Address dialog box.

4. Enter the name or IP address of a MetaFrame server.

Note For the TCP/IP+HTTP and SSL/TLS+HTTPS protocols, if you do notenter an IP address, you must have a MetaFrame server on your networkmapped to the default name of ica.domainname, where domainname is a TCP/IP domain name. TCP/IP+HTTP and SSL/TLS+HTTPS server location do notsupport the (Auto-Locate) function.

5. To define other server groups, select the required group from the Server Groupand repeat steps 3 and 4.

6. Click OK.


Configuring HotkeysHotkeys are used to control the behavior of the client and as substitutes for thestandard Windows hotkeys for a published application. For example, if you wantedto close the current window on a Windows PC, you would press ALT+F4. This keycombination closes the session in X Windows. Hotkey functionality allows you tomap common key combinations like ALT+F4 to a key combination such asALT+CTRL+F4 that will be ignored by your local operating system. When youpress this new combination, the ICA UNIX Client will send ALT+F4 to theMetaFrame server, closing the current window.

" To display the hotkey settings

From the Settings page, select Hotkeys from the drop-down list:

On the Hotkeys pages, you can define alternative key combinations for the hotkeys<Alt> <F1> to <Alt> <F12>, ALT+TAB, ALT+SHIFT+TAB, and ToggleSpeedscreen, -which are reserved for use by X Windows.


By default, these key combinations are generated by <Alt> <Ctrl> <F1> to <Alt><Ctrl> <F12>, but you can change the definitions by selecting alternative keys fromthe pop-up menus.

Any <Alt> key combinations not used by your X Window manager can be used asnormal within the ICA session.

Note If you want to use the PC key combination <Ctrl> <Alt> <Delete> duringthe connection session, use the key combination <Ctrl> <Alt> <Enter> or <Ctrl><Alt> <Return>.

Configuring Preferences" To configure the preference settings

1. Select Preferences from the drop-down list in the Settings dialog box todisplay the Preferences page:


2. Adjust the settings as required, for example:

• In the Keyboard Layout field, click the … button (“browse”) to select yourinput locale from the list. Input locale is the language you want to type in.

• In the Keyboard Type (Client) field, click the … button (“browse”) toselect your correct workstation keyboard type from the list.

• In the Keyboard Type (Server) field, click the … button (“browse”) toselect the specific physical keyboard type you are using from the list. If youare using a Japanese keyboard, select it. For all others, use the default(standard 105 key keyboard).

• Select Enable Windows Alert Sounds if you want Windows alert soundsto be played using the UNIX workstation sound system.

• Select Allow Automatic Client Updates to allow the client software at thisworkstation to be automatically updated when a newer version is available.See “Preparing for Client Auto Update” on page 26 for details.

Using xcaptureThe Citrix ICA UNIX Client includes a helper application, xcapture, that can assistthe exchange of graphical data between the MetaFrame server clipboard andnon-ICCCM-compliant X Windows applications on the X desktop. You can usexcapture to:

• Grab dialog boxes or screen areas and copy them between the UNIX desktop(including non-ICCCM-compliant applications) and an application running inan ICA Client window.

• Copy graphics between the ICA Client and X graphics manipulation utilitiesxmag or xv.

" To start xcapture

At the UNIX prompt, type /usr/lib/ICAClient/util/xcapture and press ENTER(where /usr/lib/ICAClient is the directory in which you installed the ICA UNIXClient).

" To copy from the UNIX desktop

1. From the xcapture dialog box, click From screen. The cursor changes to acrosshair.

2. To:

• Select a window: move the cursor over the window you want to copy andclick the middle mouse button.


• Select a region: hold down the left mouse button and drag the cursor toselect the area you want to copy.

• Cancel the selection: click the right mouse button. While dragging, you cancancel the selection by clicking the right button before releasing the firstbutton.

3. From the xcapture dialog box, click To ICA. The xcapture button changescolor to show that it is processing the information.

4. When the transfer is complete, use the appropriate paste command in theapplication in the ICA Client window.

" To copy from xv to an application in the ICA Client window

1. From xv, copy the information.

2. From the xcapture dialog box, click From XV and then click To ICA. Thexcapture button changes color to show that it is processing the information.

3. When the transfer is complete, use the appropriate command in the applicationin the ICA Client window to paste the information.

" To copy from an application in the ICA Client window to xv

1. From the application in the ICA Client window, copy the information.

2. From the xcapture dialog box, click From ICA and then click To XV. Thexcapture button changes color to show that it is processing the information.

3. When the transfer is complete, you can use the paste command in xv.

" To copy between xmag and an application in the ICA Client window

1. Copy the information in xmag or the ICA Client application.

2. From the xcapture dialog box, click From ICA and then click To ICA. Thexcapture button changes color to show that it is processing the information.

3. When the transfer is complete, use the appropriate paste command in thedestination application.

Note While both xmag and xv can also do screen grabs, they do not cope wellwith mixed-visual or mixed-colormap regions. xmag does not grab the colormap atthe same time as the pixels.


Integrating the ICA UNIX Client with Security SolutionsYou can integrate the ICA UNIX Client with a range of security technologies,including proxy servers, firewalls, and SSL/TLS based systems. This sectiondescribes:

• Making a connection through a SOCKS proxy server or Secure proxy server(also known as Security proxy server, HTTPS proxy server, or SSL tunnelingproxy server).

• Integrating the client with Citrix Secure Gateway or SSL Relay solutions withSecure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols.

• Connecting to a server across a firewall using alternate addressing.

• Using ICA encryption to help protect data on local networks.

Connecting Through a Proxy ServerProxy servers are used to limit access into and out of your network, and to handleconnections between ICA Clients and the MetaFrame servers. The ICA UNIXClient supports the SOCKS protocol and, from Version 6.30, the Secure proxyprotocol.

Note To ensure a secure connection, enable TLS/SSL.

Using Auto-Client Proxy DetectionIf you are deploying the ICA UNIX Client in an organization with many proxyservers, consider using auto-client proxy detection. Auto-client proxy detectioncommunicates with the local Web browser to try to discover the details of the proxyserver. It is also useful if you cannot determine which proxy server will be usedwhen you configure the client.

Auto client proxy detection can be used only with Netscape for UNIX 4.0 or later,and only if Netscape has been statically configured. Auto client proxy detection isnot supported if Netscape has been configured to use PAC (Proxy AutoConfiguration) files.

Connecting Through a SOCKS Proxy Server" To detect automatically the proxy server settings used by the Web browser

(auto-client proxy detection)

Auto-client proxy detection can be used only for Version 6.30 of the UNIX Client.



2. From the drop-down list, click Firewall.

3. From the Firewall dialog box, click Use Netscape settings

4. Click OK.

Note Auto client proxy detection can be used only with Netscape for UNIX 4.0 orlater, and only if Netscape has been statically configured. Auto client proxydetection is not supported if Netscape has been configured to use PAC (Proxy AutoConfiguration) files.

" To specify a SOCKS proxy for an ICA connection manually

1. Select the name of the connection you want in the ICA Client window. From theEntry menu, click Properties.

2. From the drop-down list, choose Firewall to display the Firewall page.

3. Select the SOCKS check box and type the address or IP number in the ProxyAddress field and the port number in the Port field for the SOCKS proxyserver.

4. Click OK.

" To specify a default SOCKS proxy manually



3. Select the SOCKS check box. Type the proxy address or IP number in theProxy Address field and the port number in the Port field for the SOCKSproxy.

4. Click OK.

Connecting Through a Secure Proxy Server" To detect automatically the proxy server settings used by the Web browser

(auto-client proxy detection)

Auto-client proxy detection can be used only for Version 6.30 of the UNIX Client.


2. From the drop-down list, click Firewall.

3. From the Firewall dialog box, click Use Netscape settings

4. Click OK.


Note Auto client proxy detection can be used only with Netscape for UNIX 4.0 orlater, and only if Netscape has been statically configured. Auto client proxydetection is not supported if Netscape has been configured to use PAC (Proxy AutoConfiguration) files.

" To specify a Secure proxy server for an ICA connection manually

1. Select the name of the connection you want in the ICA Client window. From theEntry menu, click Properties.


3. Select the Secure (HTTPS) check box and type the address or IP number in theProxy Address field and the port number in the Port field for the SOCKSproxy server.

4. Click OK.

" To specify a default Secure proxy server manually

1. Choose Settings from the Option menu.


3. Select the Secure (HTTPS) check box. Type the proxy address or IP number inthe Proxy Address field and the port number in the Port field for the SOCKSproxy.

4. Click OK.

Connecting Across a FirewallNetwork firewalls can allow or block packets based on the destination address andport. If you are using ICA through a network firewall, use the information providedin this section to configure the firewall settings. You can configure the ICA Clientto connect to a MetaFrame server through a firewall.

" To connect across a firewall

1. Click the Option menu and choose Settings.

2. From the drop-down list, choose Firewall.

3. Click Use alternate address for firewall connection.

4. Add the external Internet address of a MetaFrame server that is on the subnet towhich you want to connect to the Address List in the Server Location page.See “Configuring Server Location and Business Recovery” on page 66.


Using ICA Encryption

Note ICA Encryption cannot be used with Netscape Navigator 4.x or earlierbecause the key generation in Netscape Navigator is insufficiently random for asecure connection.

Encryption increases the security of your ICA connection. By default, basicencryption is enabled on all connections. The MetaFrame server must beconfigured to allow the selected encryption level or greater. To enable encryptionlevels higher than Basic, the MetaFrame server must support ICA encryption. Thissupport is included with ICA Encryption Services and MetaFrame XP FeatureRelease 1 or later.

Note Selecting ICA Encryption disables automatic login to the MetaFrame server.

" To change the encryption settings

1. Select the name of the connection you want in the Citrix ICA Client window.Click the Properties button.

2. Choose Connection from the Properties dialog box to display the Connectionpage.

3. Choose an encryption level from the Encryption Level popup menu.

4. Click OK.

Note The MetaFrame server can be configured to allow only connections fromICA Clients that support basic or advanced encryption.

Integrating the ICA UNIX Client with Citrix SecureGateway or SSL Relay

Note The SSL and TLS protocols cannot be used with Netscape Navigator 4.x orearlier because the key generation in Netscape Navigator is not sufficiently randomfor a secure connection.

You can integrate the ICA UNIX Client with:

• SSL Relay (Client Versions 6.20 and later)

• Citrix Secure Gateway (Client Versions 6.20 and later)


Client Versions 6.20 and later support the SSL protocol and Client Version 6.30 alsosupports the TLS protocol.

• SSL provides strong encryption to increase the privacy of your ICA connectionsand certificate-based server authentication to ensure that the server you areconnecting to is genuine.

• TLS (Transport Layer Security) is the latest, standardized version of the SSLprotocol. The Internet Engineering Taskforce (IETF) renamed it TLS when theytook over responsibility for the development of SSL as an open standard. TLSsecures data communications by providing server authentication, encryption ofthe data stream, and message integrity checks. Because there are only minortechnical differences between SSL Version 3.0 and TLS Version 1.0, thecertificates you use for SSL in your MetaFrame installation will also work withTLS. Some organizations, including US government organizations, require theuse of TLS to secure data communications. These organizations may alsorequire the use of validated cryptography, such as FIPS 140. FIPS (FederalInformation Processing Standard) is a standard for cryptography.

" To specify a Citrix Secure Gateway server that has been configured to run inRelay mode

To use an ICA file to connect to the Secure Gateway relay server, modify the .icafile as follows:

1. Open the .ica file.

2. In the [Application] section of the file, create or modify the following entries:SSLProxyHost=csgwy.company.com:443

SSLEnable=On

where Application Name is the section containing published applicationsettings; and the value of SSLProxyHost is the Secure Gateway relay server youwant to connect to.


For more information on Citrix Secure Gateway, see the Citrix Secure GatewayAdministrator’s Guide.

Configuring and Enabling the Client for SSL and TLS

SSL and TLS are configured in the same way and use the same certificates. WhenSSL and TLS are enabled, each time you initiate a connection the client tries to useTLS first, then tries SSL. If it cannot connect with SSL, the connection fails and anerror message appears.


To use SSL or TLS, you need a root certificate on the client machine that can verifythe signature of the Certificate Authority on the server certificate. Support for thecertificates listed below is built in to Citrix SSL and TLS-enabled ICA Clients:

You are not required to obtain and install root certificates on the client machine touse the certificates from these Certificate Authorities. However, if you choose touse a different Certificate Authority, you must obtain and install a root certificatefrom the Certificate Authority on each client machine.

Important Certificate key lengths of greater than 2048 bits are not supported onthe ICA UNIX Clients. Ensure that the bit lengths of Certificate Authority root andintermediate certificates, and of your server certificates, are supported by the clientor connection may fail.

" To configure ICA UNIX Clients to use SSL on a single connection

1. In the main ICA Client window, select the connection entry you want to set.


3. From the drop-down list, choose Network. In the Network Protocol panel,click the Network Protocol drop-down list to display a list of availableprotocols. If the list appears greyed out, click Use Default to stop using thedefault protocol, then click the Network Protocol drop-down list.

4. Select SSL/TLS +HTTPS from the Network Protocol list.

5. Either select the server location Use Default button or enter the machine to usefor server browsing.

6. Click OK.

Certificate Issuing Authority

Class4PCA_G2_v2.crt VeriSign Trust Network

Class3PCA_G2_v2.crt VeriSign Trust Network

BTCTRoot.crt Baltimore Cyber Trust Root

GTECTGlobalRoot.crt GTE Cyber Trust Global Root

GTECTRoot.crt GTE Cyber Trust Root

Pcs3ss_v4.crt Class 3 Public Primary Certification Authority

SecureServer.crt Secure Server Certification Authority


" To configure ICA UNIX Clients to use SSL as the default protocol


2. From the drop-down list, choose Server Location.



You can specify this protocol for all connections or for individual server groups/servers using the Server Group drop-down list and Address List.

5. Click OK.

Note If you attempt to make a non-SSL connection to a SSL server you will not beconnected and a connection failed message will be displayed.

" To configure ICA UNIX Clients to use TLS on a single connection

1. In the main ICA Client window, select the connection entry you want to set.


3. From the drop-down list, choose Network. In the Network Protocol panel,click the Network Protocol drop-down list to display a list of availableprotocols. If the list appears greyed out, click Use Default to stop using thedefault protocol, then click the Network Protocol drop-down list.


5. Either select the server location Use Default button or enter the machine to usefor server browsing.

6. Click OK.

" To configure ICA UNIX Clients to use TLS as the default protocol


2. From the drop-down list, choose Server Location.



You can specify this protocol for all connections or for individual server groups/servers using the Server Group drop-down list and Address List.

5. Click OK.


" To force TLS connections

To force clients to connect only with TLS, you must specify TLS on your CitrixSecure Gateway server or SSL Relay service. See the Citrix Secure GatewayAdministrator’s Guide or SSL Relay service documentation for more information.

Using Applications Published on a MetaFrame for UNIX ServerFor connections to applications published on a MetaFrame for UNIX server, twoadditional utilities provide functionality for configuring session display andcopying/pasting objects between the ICA session and the client device. This sectiondescribes how to access and use these tools through the Citrix window manager.

Using the Window ManagerIf you are connecting to an application published on a MetaFrame for UNIX server,use the Citrix window manager (ctxwm) to minimize, resize, position and closewindows, and access seamless full screen mode. This section describes how to usethe window manager.

About Seamless Windows on MetaFrame for UNIXSeamless windows are ICA Client session windows containing publishedapplications that are configured to run in seamless mode. In seamless mode,applications running on the MetaFrame server appear to the client as if they arerunning locally, and each application appears in its own resizable window.

Minimizing, Resizing, Positioning, and Closing WindowsWhen you connect to a published application on a MetaFrame for UNIX server,buttons to minimize, resize, position, and close windows are provided by the Citrixwindow manager.

" To minimize, resize, position, and close windows

Use the left mouse button, to click on the following buttons:

To Click Note

Minimize publishedapplication windowson your desktop.

Seamless windows are minimized as buttons onthe desktop’s taskbar. Non-seamless andseamless “full screen” windows are minimized asicons on the desktop.


Using the Citrix Window Manager MenusIn remote desktop and seamless “full screen” windows, you can use the ctxwmmenu system to log off, disconnect, and exit from published applications andconnection sessions.

" To access the ctxwm menu system

1. On a blank area of the remote desktop window, click and hold down the leftmouse button. The ctxwm menu is displayed.

2. Drag the mouse pointer over Shutdown to display the shutdown options.

" To choose an option from the Citrix window manager menu

Drag the pointer over the required option to highlight it. Release the mouse buttonto select the option.

Open a minimizedwindow

(Taskbar orIcon)

Click its button on the taskbar, or its icon on thedesktop.

Adjust the size ofpublished applicationwindows.

Click and hold down the mouse button, then movethe pointer to the edge of the window and drag it inthe direction you wish to scale it. The windowdimensions are displayed in the top left handcorner. Release the mouse button to apply theresizing.To resize the window proportionately, move themouse pointer to a corner of the window and dragit.

Re-position publishedapplication windows

(Title-bar)

Click and hold down the mouse button, drag thewindow to the required position on the desktopand release the mouse button.

Close and exit apublished application

When you close the last application in a session,after 20 seconds the session disconnectsautomatically.

To Choose

Terminate the connection and allrunning applications

Logoff


Note Your MetaFrame server may be configured to terminate any applicationsthat are running if a session is disconnected.

Copying and Pasting Graphics Using ctxgrab andctxcaptureIf you are connected to an application published on a MetaFrame for UNIX server,use ctxgrab or ctxcapture to copy and paste graphics between the ICA session andthe local desktop. These utilities are configured and deployed from the MetaFramefor UNIX server.

Using ctxgrabThe ctxgrab utility is a simple tool you can use to copy and paste graphics from ICAapplications to applications running locally on the client device. This utility isavailable from the command prompt or, if you are using a published application,from the Citrix window manager.

" To access the ctxgrab utility from the Citrix window manager

1. In seamless mode, right click the ctxgrab button in the top, left hand corner ofthe screen to display a menu and choose the screengrab option.

In full screen mode, left click to display the ctxwm menu and choose thescreengrab option.

2. When ctxgrab is started, a dialog box is displayed.

" To copy from an application in an ICA Client window to a local application

1. From the ctxgrab dialog box, click From screen.

2. To:



Disconnect the session but leave theapplication running

Disconnect

Disconnect the session and terminatethe application

Exit


• Cancel the selection: click the right mouse button. While dragging, cancelthe selection by clicking the right mouse button before releasing the firstbutton.

3. Use the appropriate command in the local application to paste the object.

Using ctxcaptureThe ctxcapture utility is a more fully-featured utility for cutting and pastinggraphics between ICA applications and applications running on the client device.

With ctxcapture you can:

• Grab dialog boxes or screen areas and copy them between an application in anICA Client window and an application running on the local client device,including non-ICCCM-compliant applications.

• Copy graphics between the ICA Client and the X graphics manipulation utilityxv.

If you are connected to a published desktop, ctxcapture is available from thecommand prompt. If you are connected to a published application, and theMetaFrame server administrator has made it available, you can access ctxcapturethrough the ctxwm window manager.

" To access the ctxcapture utility from the Citrix window manager

1. In seamless mode, right click the ctxcapture button in the top, left hand cornerof the screen. Choose screengrab from the displayed menu.

In full screen mode, left-click to display the Citrix window manager menu andchoose the screengrab option.

2. When ctxcapture is started, a dialog box is displayed.

" To copy from a local application to an application in an ICA Client window

1. From the ctxcapture dialog box, click From screen.

2. To:



• Cancel the selection: click the right mouse button. While dragging, cancelthe selection by clicking the right mouse button before releasing the firstbutton.

3. From the ctxcapture dialog box, click To ICA. The ctxcapture button changescolor to indicate that it is processing the information.


4. When the transfer is complete, use the appropriate command in the localapplication to paste the information.

" To copy from an application in an ICA Client window to a local application

1. From the application in the ICA Client window, copy the graphic.

2. From the ctxcapture dialog box, click From ICA.

3. When the transfer is complete, use the appropriate command in the localapplication to paste the information.

" To copy from xv to an application in an ICA Client window or localapplication

1. From xv, copy the graphic.

2. From the ctxcapture dialog box, click From xv and To ICA.

3. When the transfer is complete, use the appropriate command in the ICA Clientwindow to paste the information.

" To copy from an application in an ICA Client window to xv

1. From the application in the ICA Client window, copy the graphic.

2. From the ctxcapture dialog box, click From ICA and To xv.

3. When the transfer is complete, use the paste command in xv.

Setting up Extended Parameter PassingYou can now integrate MetaFrame published applications into desktop UNIXenvironments by associating a file type on a client device with an applicationpublished on a MetaFrame XP server. Command line parameters from the desktopare passed to the server via the ICA Client to start an application session.

The desktop configuration file must be modified as detailed below for each file typeassociation you require. This type of command line enables the user to open anassociated MetaFrame published application in an ICA session directly from a filein a file management application, or directly from a desktop icon.

To make use of this capability from within your window manager, you need to tellthe window manager how and when to start the client. The mechanism for doingthis varies between UNIX desktops. See available documentation for your desktopenvironment.

Drives used for client mapping must not be remapped on the server.


Note The following command line arguments are stored in the $ICAROOTdirectory — this makes them available to all clients that use wfica program after thechange. Individual client settings can be made in the $HOME directory for eachclient.

You have to set up file association between desktop filename extensions and theMetaFrame applications you want to use with them. The ICA Client will accept ascommand line arguments:

• The name of an ICA file specifying a connection to be made ($ICAROOT/wficaconnection.ica).

• A string to be passed unchanged to a published application ($ICAROOT/wfica-desc application -param string).

• The full path of a file to be passed to a published application ($ICAROOT/wfica-desc application -fileparam filepath).

Note The file must be one included in one of the client drive mappings for theserver to have access to it. From the full filepath the client will determine whichmapped directory to use and translate the path accordingly.

If necessary, the -param and the -fileparam options can be repeated to produce acombined string which will be passed to the published application. For example:-param "/C " -fileparam $HOME/src/file -param " /L:" -fileparam /tmp/out.log

might pass the following to the application:/C H:src\file /L:T:out.log

Note For the published application to receive the filename passed from the client,the Published Application Manager must specify a command line containing %*eg, D:\WINNT\system32\notepad.exe %*

Setting up Server-Client Content RedirectionServer-client content redirection allows you to specify that URLs in a publishedapplication are opened using a local application. For example, double-clicking alink to a Web page while using Microsoft Outlook in an ICA session opens therequired file using the browser on the client device (by default, this is Netscape).Server-client content redirection allows administrators to allocate MetaFrameresources more efficiently, thereby providing users with better performance.

The following types of URL can be redirected:


• HTTP (Hypertext Transfer Protocol)

• HTTPS (Secure Hypertext Transfer Protocol)

• RTSP (Real Player)

• RTSPU (Real Player)

• PNM (Older Real Players)

If the client does not have an appropriate application, or cannot directly access thecontent, the URL is opened using the server application.

Server-client content redirection is configured on the server and enabled by defaulton the client provided that the UNIX path includes Netscape and RealPlay.

Note Real Player for Linux and some UNIX systems can be obtained fromhttp://proforma.real.com/real/player/unix/unix.html.

" To enable server-client content redirection if Netscape and RealPlay are not inthe UNIX path:

1. Open the configuration file wfclient.ini.

2. At the CRBrowserPath setting, enter the path to Netscape.

3. At the CRPlayPath setting, enter the path to RealPlay.


" To turn off server-client content redirection from the client

1. Open the configuration file wfclient.ini.

2. Change the CREnabled setting to Off.



Common ProblemsThis section provides solutions to the most commonly encountered problems whenusing the Citrix ICA Client.

I cannot connect to a MetaFrame server using its full Internet name

If you do not have a DNS (Domain Name Server) configured on your network andon your workstation, it may not be possible to resolve the server name to an IPaddress. Alternatively, you can specify the server by its IP address, rather than by itsname.

I experience problems with overscrolling when using published applications

Users may experience problems with overscrolling when using certain publishedapplications.

" To prevent overscrolling

1. Open the configuration file, wfclient.ini, in the $HOME/.ICAClient directory

2. In the [Thinwire 3.0] section of the file, type:TW2StopwatchMinimum=100


The lowest effective value is likely to be 100, but you may need to experiment withthis value to find the optimum solution.

Error MessagesAn error occurred. The error code is 11 (E_MISSING_INI_SECTION).Please refer to the documentation. Exiting.

When running the client from the command line, this usually means thedescription given on the command line was not found in the appsrv.ini file.

The option "..." is not valid.Missing argument for option "...".

The option "..." has an invalid argument: "...".The configuration file has been edited directly, or is corrupt.

Error in configuration file: "..." Cannot find section "...".The configuration file has been edited directly, or is corrupt.

Error in configuration file. Section "..." must contain an entry "...".The configuration file has been edited directly, or is corrupt.

Cannot find keyboard mapping file "...".The keyboard mapping file specified in the Preferences page of the


Settings dialog box is invalid or cannot be located.

A server must be entered.A server name must be entered in the Network page of the Propertiesdialog box.

Cannot write file: "..."There was a problem saving the connection database; for example, no diskspace.

Cannot create file: "..."There was a problem creating a new connection database.

Invalid Error: Cannot start Wfica with this connection.The connection entry is invalid.

Cannot find selected connection.The configuration file is corrupt. Create a new configuration file.

Cannot find specified connection.The configuration file is corrupt. Create a new configuration file.

Error in configuration file: "..." Missing section: "..."The configuration file is corrupt. Create a new configuration file.

Inconsistency in configuration file: "..." Missing section: "..."The configuration file is corrupt. Create a new configuration file.

This description is already in use. The Description must be unique.The Description field in the Network page of the Properties dialog boxmust be unique.

Cannot get address for server "..."The server name cannot be resolved.

Unable to perform update: not running as superuser.You must be running as superuser to perform a client update.

Unable to perform update: client is not on local filesystem.The client cannot update an installation on a non-local (for example NFS-mounted) file system.

Unable to perform update: not running $ICAROOT/wfica.The client cannot update an installation other than its own.

Error in configuration file: "..." Bad Key "..."The X Server vendor information in the configuration file is corrupt.Create a new configuration file.

Error in configuration file: "..." Bad Value "..."The X Server vendor information in the configuration file is corrupt.Create a new configuration file.

Error in configuration file: "..." Bad Vendor Range "..."The X Server vendor information in the configuration file is corrupt.


Create a new configuration file.

Error loading dynamic module: "..."The client could not dynamically load an object module. Some clientfunctionality (such as audio) may be missing.

Command-line ParametersThe table below lists the UNIX Client command-line parameters.

Note A list of the parameters can be obtained by typing at the command line wfica- ?, wfica -help, or wfica -h.

To Use the command

Specify the connection to use from the Connection File. -desc description

Specify the connection to use from the Connection File. -description description

Specify a Connection File. This allows the use of an alternativeappsrv.ini.

-file connection filename

Set alternative protocol file. This allows the use of analternative module.ini.

-protocolfile filename

Set alternative client configuration file. This allows the use ofan alternative wfclient.ini.

-clientfile filename

Set the location of Client Installation files. This is equivalent tosetting the ICAROOT environment variable.

-icaroot directory

Specify a string to be added to a published application. -param string

Specify the UNIX path to be accessed via Client Drive Mappingby a published application.

-fileparam unixpath

Specify a username. -username username

Specify a password. -password password

Specify a clear text password. -clearpassword clear password

Specify a domain. -domain domain

Specify an initial program. -program program

Turn on sound. -sound

Turn off sound. -nosound

Use private colormap. -private


Note You can use a connection file simply by typing it after wfica without any ofthe above options.

Use shared colormap. -shared

Set drive mapping overrides. These are of the form A$=<path>where <path> can contain an environment variable, forexample A$=$HOME/tmp. This option must be repeated foreach drive to be overridden. Note that in order for the overrideto work, there must be an existing mapping, though it need notbe enabled.

-drivemap string

Show this list of parameters. -help

Turn off the splash screen. -nosplash

Display version information. -version

Suppress connection dialogs. -quiet

Set session geometry. -geometry WxH+X+Y

Show error numbers. -errno

Index 91

IndexAAdding Citrix ICA Clients to the Client Update Database

31Alt Key Combinations 68Application Publishing

Support 16Using the Window Manager 79

Applications 58Approximate Colors 59, 64Audio Mapping 52Auto Client Reconnect 20, 64

BBandwidth Reduction

Bitmap Caching 56Data Compression 56Disk Caching 62SpeedScreen 57

Bitmap Caching 56, 62Business Recovery 17, 66

CCache Settings 62Caching Bitmaps 62Changing a Connection Entry 53Citrix on the World Wide Web 11Citrix Secure Gateway Support 21Citrix Window Manager 79Client Auto Update 16Client Device Mapping 14Client Drive Mapping 15Client Printer Mapping 15Client Update Database 26

Adding and Removing Citrix ICA Clients 31Changing the Properties of a Citrix ICA Client in the

Database 33Configuring Properties 30Creating a New Database 29Setting a Default Database 29

Clipboard 16Color

Approximation 59Mapping 59, 64

Common Problems 86

ConfiguringApplication Properties 58Auto Client Reconnect 64Client Update Database 28Default Settings 61Default Window Settings 64Hotkeys 68Network Properties 54Network Protocol 66Preferences 69Smart Card Support 41the Citrix ICA UNIX Client 39Window Properties 59

Connecting Through a Proxy Server 72Connection Entries

Changing 53Creating New 39Default Settings 61Running Applications 58

Content Redirection 20Conventions 10Creating

a Connection Entry 39a New Client Update Database 29

ctxcapture 82ctxgrab 81ctxwm 79–80

DData Compression 15, 56Deploying the Citrix ICA UNIX Client 23Disk Cache 62Disk Caching 15Drive Mapping 44

EEditing a Connection Entry 53Enabling

Alert Sounds 69Smart Card Support 41

Encryption 17, 20, 75Enhanced Proxy Support 21Error Messages 86Extended Parameter Passing 83

FFinding More Information 11Full Screen Seamless Mode 79


HHotkeys 16, 68How to Use this Guide 9

IICA to X proxy 35ICA UNIX Client Hotkeys 16Improving Performance 55Installing the ICA UNIX Client 24Introduction to the Citrix ICA UNIX Client 13

KKeyboard Layout 69

LLaunching a Connection 42Logon Parameters 54

MMapping

Client Audio 52Client Devices 43Client Drives 44Client Printers 48

NNetwork Properties 54Network Protocol 66New Connection Entries 39

OOpening a Connection Entry 42Operating Systems Supported 24

PPasting Between Applications 16Platforms Supported 24Preferences 69Printer Mapping 48Proxy Server Support 21, 72Published Applications 16, 54Publishing Applications

Using the Window Manager 79

RRedirecting Client Output 35Remote Desktop Windows 79Removing

Citrix ICA Clients from the Client Update Database31

the Citrix ICA UNIX Client 35Roaming User Reconnect 20

SScreen Grabs 16Seamless Windows 79

MetaFrame for UNIX 79Overview 18

Security 72–75, 78–79Server Location 66Server Name 54Server Side ICA 35Server-Client Content Redirection 20Setting Up

Extended Parameter Passing 83the Citrix ICA UNIX Client 39

Shortcut Keys 68Smart Card Support 19, 41Sound Support 52SpeedScreen

Change Settings 57Overview 17

Startinga Connection Session 42the Citrix ICA UNIX Client 23the ICA UNIX Client 26

System Requirements 24

TTCP/IP+HTTP 68TLS Encryption 20Transparent Clipboard Access 16True Color Desktop Support 18

UUninstalling the Citrix ICA UNIX Client 35UNIX Platforms 24User-to-User Shadowing 21

WWho Should Use this Manual 9

Index 93

Window Manager 79–80Window Properties 59Window Settings 64Windows

Remote Desktop 79Seamless 79

Xxcapture 16, 70X11 deployment 35

Administrator’s Guide · deploying, and maintaining Citrix ICA Clients for UNIX (also called the...

Documents

Transcript of Administrator’s Guide · deploying, and maintaining Citrix ICA Clients for UNIX (also called the...