Before you Begin


Who Should Use This Manual

This manual is for system administrators responsible for installing, configuring, deploying, and maintaining Citrix ICA Clients for 32-bit Windows (also called the Citrix ICA Win32 Clients). This manual assumes knowledge of:

Citrix MetaFrame Application Server for Windows or Citrix WINFRAME

The operating system on the client computer (Windows 95, Windows 98, or Windows NT)

Installation, operation, and maintenance of network and asynchronous communication hardware, including serial ports, modems, and device adapters


How to Use this Guide

To get the most out of the Citrix ICA Client Administrator's Guide, review the table of contents to familiarize yourself with the topics discussed.

This guide contains the following sections:

Chapter	Contents
Chapter 1, "Introduction to the Citrix ICA Win32 Client"	Gives a detailed list of features.
Chapter 2, "Deploying the Citrix ICA Win32 Client"	Describes how to install and update the Citrix ICA Win32 Client.
Chapter 3, "Configuring the Citrix ICA Win32 Client"	Describes how to configure connection properties and device mappings for the Citrix ICA Win32 Client.


Conventions

The following conventional terms, text formats, and symbols are used throughout the printed documentation:

Convention	Meaning
Bold	Indicates boxes and buttons, column headings, command-line commands and options, icons, dialog box titles, lists, menu names, tabs, and menu commands.
Italic	Indicates a placeholder for information or parameters that you must provide. For example, if the procedure asks you to type filename, you must type the actual name of a file. Italic also indicates new terms and the titles of other books.
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 password with the command. Type only the information within the brackets, not the brackets themselves.
...(ellipsis)	Indicates a command element can be repeated.
Monospace	Represents examples of screen text or entries that you can type at the command line or initialization files.
	Indicates a procedure with sequential steps.
•	Indicates a procedure with only one step.
	Indicates a list of related information, not procedural steps.
The Citrix ICA Clients allow users to connect to MetaFrame servers and WINFRAME servers. When describing a feature or procedure common to MetaFrame and WINFRAME servers, this manual uses the term Citrix server. When describing a feature unique to a MetaFrame or WINFRAME server, this manual specifies either a MetaFrame or WINFRAME server.


Finding More Information

This manual contains conceptual information and installation and configuration steps for the Citrix ICA Win32 Client. For additional information, consult the following manuals:

The Citrix ICA Client Quick Reference Cards give users step-by-step instructions for using the Citrix ICA Clients to connect to Citrix servers and run published applications.

The Citrix ICA Client Administrator's Guides for the ICA DOS, Win16, Java, Web, Macintosh, and UNIX Clients.

For instructions on installing, configuring, and maintaining your Citrix servers, see the documentation included in your MetaFrame or WINFRAME package.

This book and other Citrix documentation is available in Adobe PDF format in the documentation directory of your MetaFrame or WINFRAME CD-ROM. Using the Adobe Acrobat Reader, you can view and search the documentation electronically or print it for easy reference. To download the Adobe Acrobat Reader for free, please go to Adobe's Web site at http:\\www.adobe.com.

Important  Always consult the Readme.txt files for MetaFrame, WINFRAME, and the Citrix ICA Clients for any last-minute updates, installation instructions, and corrections to the documentation.


Citrix on the World Wide Web

Citrix offers online Technical Support Services at http://www.citrix.com that include the following:

Downloadable Citrix ICA Clients, available at http://download.citrix.com

A Frequently Asked Questions page with answers to the most common technical issues

An FTP server containing the latest service packs and hotfixes for download

An Online Knowledge Base containing an extensive collection of technical articles, troubleshooting tips, and white papers

Interactive online support forums


Year 2000 Readiness

For a detailed description of the Year 2000 Readiness of Citrix products, see our Web site at http://www.citrix.com/misc/y2000.htm.


Introduction to the ICA Win32 Client

Overview

When connected to a Citrix server, the Citrix ICA Win32 Client provides additional features that make remote computing just like running applications on a local desktop. The Citrix ICA Win32 Client has the following features:

Program Neighborhood

Video support

TAPI support

Seamless windows

Client device mapping

Sound support

Dialing prefixes

Encryption

Client Auto Update

Windows clipboard integration

Low bandwidth requirements

Disk caching and data compression

Business recovery

Wheel mouse support


Program Neighborhood

With the introduction of Program Neighborhood, server-based applications can now be pushed to the Program Neighborhood client, integrated into the local 32-bit Windows desktop, or pushed directly to the client's Start menu.

Similar in concept to Windows Network Neighborhood, Program Neighborhood provides complete administrative control over application access and local desktop integration, with client configuration required. .


Video Support

VideoFrame in conjunction with MetaFrame 1.8 enables the production and deployment of custom video applications to 32-bit Windows ICA Clients using an innovative intelligent compression and a streaming extension to the ICA protocol.


TAPI Support

The Citrix ICA Win32 Client includes TAPI modem support for dial-up connections to Citrix servers. TAPI support allows the Win32 Client to detect the presence of TAPI Version 1.4 or greater modems on the client computer (TAPI is present on Windows NT 4.0 and Windows 95). Users need not manage separate modem entries for their local communications programs and Remote Application Manager.

When a TAPI modem is detected, the ICA Win32 Client can use the modem installation and configuration utilities built into Windows to manage the modem. If the client computer is not TAPI-capable, the ICA Win32 Client is able to use its own modem installation and configuration utilities.


Seamless Windows

The Citrix ICA Win32 Client now supports the seamless integration of local and remote applications on the local Windows 95 or Windows NT 4.0 desktop. By selecting the Seamless Windows option when configuring a connection to a Citrix server, a user no longer needs to access an entire remote desktop to run remote Windows applications. With a single session a user can gain access to multiple applications, have fully functional local keyboard controls (such as ALT+TAB), switch between local and remote applications on the local taskbar, define remote application icons on the local desktop, and even tile and cascade between local and remote Windows applications.


Client Device Mapping

The Citrix ICA Clients support client device mapping. Client device mapping allows a remote application running on the Citrix server to access printers, disk drives, and COM port devices attached to the local client computer.

Client drive mapping for all ICA Clients is transparent. Accessing a local drive on a client computer requires no manual configuration by the user of the client computer.

Client drive mapping

Client printer mapping

Client COM port mapping


Client Drive Mapping

Client drive mapping allows drive letters on the Citrix server to be redirected to drives that exist on the client computer; for example, drive H in a Citrix user session can be mapped to drive C of the local computer running the Citrix ICA Client. These mappings can be used by the File Manager or Explorer and your applications just like any other network mappings.


Client Printer Mapping

Client printer mapping allows a remote application running on the Citrix server to access printers attached to the client computer. Any printers detected when you connect to a Citrix server are automatically added to the Print Manager. Client printers can be browsed and connected to in the same way as network printers. Users who access a Citrix server with the Citrix ICA Client can transparently access their local printers and disk drives (fixed and removable). The drive letters used for drive mapping are configurable and long filenames are supported.


Client COM Port Mapping

The ICA Client COM port redirector gives Citrix ICA Client users access to virtually any peripheral that requires a COM port for operations. COM port mapping is similar to printer and drive mapping, and allows users to access a COM port on the client computer as if it were connected to the Citrix server.


Sound Support

ICA Client sound support allows a client computer with a Sound Blaster 16-compatible sound card to play sound files on the server and present them on the local client computer's sound system. Client computers can play 8- or 16-bit mono or stereo Windows .wav files at 8, 11.025, 2.25, and 44.1 KHz. Audio support can be configured to use one of three different sound compression schemes. Each scheme provides different sound quality and bandwidth usage.


Dialing Prefixes

The Citrix ICA Clients support dialing prefixes. Dialing prefixes allow a user to easily add special dialing codes as required by different telephone systems for dialing out and accessing a remote Citrix server.

The most common use of dialing prefixes is defining different dialing methods for different telephone systems. For example, a user with a laptop computer may need to dial 9 to get an outside line at the office and need to dial 1 plus the area code when working on the road or at home. In this case, the user can define a dialing prefix named Office for use when dialing out from the office and a prefix called Remote for use when dialing in from the road or at home.


Encryption

The Citrix ICA Clients support encryption using Citrix SecureICA Services. This server extension (available in North American and Global versions) adds advanced RSA RC5 encryption to the Citrix server and clients. See the SecureICA Services documentation for more information.


Client Auto Update

The Client Auto Update feature allows administrators to update ICA Client installations from a central location instead of having to manually install new client versions on each client computer. New versions of Citrix ICA Clients are stored in a central Client Update Database. The latest versions of the ICA Client software are downloaded to ICA Client devices when users connect to the Citrix server.

ICA Client Auto Update works with all transport types supported by ICA (TCP/IP, IPX, NetBIOS, and serial).

ICA Client Auto Update supports the following features:

Automatically detects older client files

Transparently copies new files over any ICA connection

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


Windows Clipboard Integration

Users can cut and paste data between ICA sessions and local applications using the Windows clipboard.


Low Bandwidth Requirements

The highly efficient Citrix ICA protocol typically uses 20K of bandwidth for each session.


 Disk Caching and Data Compression

These features increase performance over low speed asynchronous and WAN connections. Disk caching stores commonly used portions of your screen (such as icons and bitmaps) locally, increasing performance by avoiding retransmission of locally cached data. Data compression reduces the amount of data sent over the communications link to the client computer.


Business Recovery

The Citrix ICA Client includes the additional intelligence to support multiple server sites (such as a primary and hot backup) with different addresses for the same published application name.

This feature provides for consistent connections to published applications in the event of a primary server disruption. Users now have an even higher level of fault tolerance and seamless user experience.


Wheel Mouse Support

If you run applications that take advantage of a wheel mouse, the Citrix ICA Win32 Client transmits the wheel mouse movements in the same manner that it transmits other mouse data. ICA Win32 Client wheel mouse support requires MetaFrame1.8 Service Pack 1 or later and a local client device that supports wheel mouse functionality.


Deploying the Citrix ICA Win32 Client

Overview

This chapter explains how to install and update the Citrix ICA Win32 Client. Topics covered in this chapter include:

System requirements

Installation methods

Creating client installation diskettes

Installing the Citrix ICA Win32 Client

Configuring the Client Update Database


System Requirements

Computers used with the ICA Win32 Client must meet the following requirements:

Standard PC architecture, 80386 processor or greater as required for the operating system

Windows 95, Windows 98, or Windows NT 3.5 or greater

8MB RAM or greater for Windows 95, 16MB RAM or greater for Windows NT 3.51 or 4.0

Microsoft mouse or 100% compatible mouse

VGA or SVGA video adapter with color monitor

High-density 3.5-inch diskette drive and available hard disk space

Sound Blaster 16-compatible sound card for sound support (optional)

For serial connections to the Citrix server, an internal modem or serial port and external modem using a 16550 Universal Asynchronous Receiver/Transmitter (UART) is recommended

For network connections to the WINFRAME server or MetaFrame application server, a network interface card (NIC) and the appropriate network transport software are required. Supported network transports are:

NetBIOS

IPX

SPX

TCP/IP


Installation Methods

You can install the Citrix ICA Win32 Client from:

The  %SystemRoot%\System32\Clients\Ica directory on your Citrix server machine

The MetaFrame or WINFRAME CD-ROM

Client installation diskettes created with the ICA Client Creator utility

For more information, see the "Creating Client Installation Diskettes" and "Installing the Citrix ICA Win32 Client" sections later in this chapter.


Preconfiguring ICA Client Settings

You can create ICA Client installation diskettes with preconfigured client settings. For more information about creating customized client diskettes, see the Readme.txt file in the Customize directory of your server CD-ROM.


Creating Client Installation Diskettes

Use the ICA Client Creator to create client installation disks.

To create Citrix ICA Client installation disks

1.	Have the required number of 3.5-inch disks on hand.

2.	From a MetaFrame server: On the Start menu, point to Program, then point to MetaFrame Tools. Click ICA Client Creator. The Make Installation Disk Set dialog box appears.

From a WINFRAME server: In the Administrative Tools folder, double-click ICA Client Creator. The Make Installation Disk Set dialog box appears.

3.	In the Network Client or Service list, click the desired Citrix ICA Client. Select the Format Disks check box to format the disks when creating the installation media. Click OK.

4.	Follow the directions on screen.


Installing the Citrix ICA Win32 Client

To install the ICA Win32 Client

1.	Make sure the client computer is properly configured and cabled. Make sure any previous installations of the Citrix ICA Client (including the ICA Connection Center, whose icon appears in the system tray in the task bar if it is active) are not running.

2.	If you are installing from diskettes, insert ICA Win32 Client Setup diskette #1 in drive A (or other appropriate drive) of the client computer. For Windows 95 and Windows NT 4.0 client computers, run a:setup using the Run option on the Start menu. For Windows NT 3.5x client computers, execute a:setup using the Run option on the File pull-down menu of Program Manager.

If you are installing from the CD-ROM, insert the CD-ROM into the client's CD-ROM drive. When the startup screen appears, click Setup ICA Client

If you are installing from a Citrix server, go to %SystemRoot%\System32\Clients\Ica \Ica32\disks\disk1, and run setup.exe.

The Welcome screen appears. Read the information on this screen and click Next.

The installation program searches your client computer for previously installed versions of the ICA Win32 Client. If an older version is detected, the screen in Step 3 appears. If no older version is detected, you will see the screen shown in Step 4.

3.	The Choose Installation Type screen appears:

The Choose Installation Type screen lets you choose to either upgrade the existing client or create a new and separate installation of the ICA Win32 Client in a new location. The default value is Upgrade the existing client. Click Next.

If you choose to create a new installation, go to Step 4. If you choose to upgrade the existing client, go to Step 6.

4.	The Choose Destination Location screen appears:

You can change the displayed path if desired by clicking Browse. Click Next to accept the displayed path and continue installation.

5.	The Select Program Folder appears:

You can choose to use the default Citrix ICA Client folder, specify the name of a new program folder, or add the ICA Win32 Client icons to an existing folder. The program folder you specify is created if it does not already exist. Click Next to continue.

6.	The ICA Client Name screen appears:

Specify a unique client name for your client computer. Citrix servers use the client name to manage client printers and other system resources. If you do not give your client computers unique client names, device mapping and application publishing may not operate correctly. When you are done, click Next to continue. A progress window appears displaying the file names as they are copied to your hard drive.

7.	If you are installing from diskette, the Setup Needs the Next Disk dialog box appears. Remove the first ICA Win32 Client diskette from drive A (or other appropriate drive) and insert the second diskette. Click OK.

8.	When the Citrix ICA Client finishes copying the program files, the Information dialog box appears. Click OK to exit this window.

The Citrix ICA Client program group appears on your desktop:

The ICA Win32 Client can be used immediately.


The Client Update Database

Use the Client Auto Update feature to store new versions of Citrix ICA Clients are stored in a central Client Update Database. The latest versions of the ICA Client software are downloaded to ICA Client devices when users connect to the Citrix server.

ICA Client Auto Update works with all transport types supported by ICA (TCP/IP, IPX, NetBIOS, and serial).

ICA Client Auto Update supports the following features:

Automatically detects older client files

Transparently copies new files over any ICA connection

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  Client Auto Update can update client files to newer versions of the same product and model. For example, it can be used to update the Citrix ICA Win32 Client. It cannot be used to update a Citrix ICA Win16 Client to the Citrix ICA Win32 Client.


The Citrix ICA Client Update Process

Each Citrix ICA Client has a product number, model number, and version number. The ICA Client product and model numbers uniquely identify the Citrix ICA Client.

Product/Model number	Platform
1/1	Citrix ICA Client for DOS
1/2	Citrix ICA Client for Win16
1/3	Citrix ICA Client for Win32
The version number is the release number of the Citrix ICA Client.

The process of updating Citrix ICA Clients with new versions uses the standard ICA protocol.

The Citrix server queries the ICA Client when the user logs on. If the Citrix server detects that the ICA Client is up-to-date, it continues the log on transparently.

If an update is needed, by default, the Citrix server informs the user of the new client and asks to perform the update. You can specify that the update occurs without informing the user and without allowing the user to cancel the update.

By default, the user can choose to wait for the client files to finish downloading or to download the files in the background and continue working. Users connecting to the Citrix server with a modem get better performance waiting for the client update to complete. You can force the client update to complete before allowing the user to continue.

During the client update, new Citrix ICA Client files are copied to the ICA Client device. The administrator can force the user to disconnect and complete the update before continuing the session. The user must log on to the Citrix server again to continue working.

After disconnecting from the server, the Citrix ICA Client completes the update. All client programs must be closed before the Citrix ICA Client can be updated.

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

In case of a problem, the existing ICA Client files are saved to a folder called Backup in the Citrix ICA Client directory.


Configuring the Client Update Database

During Citrix server setup, a client update database is created that contains the Citrix ICA Win32, Win16, and DOS Clients. By default, the update database is configured to update older client versions.

You can configure a client update database on each Citrix server in a server farm, or a single client update database on a central network share. With a single database, you can configure updates once for all Citrix servers.

Use the ICA Client Update Configuration utility to:

Create a new client update database

Set a default client update database

Configure database properties

Add Citrix ICA Clients to the update database

Remove Citrix ICA Clients from the update database

Configure client update options

To start the ICA Client Update Configuration utility

1.	From a MetaFrame server: Click the Start button, point to Programs, and then point to MetaFrame Tools. Click ICA Client Update Configuration.

From a WINFRAME server: In the Administrative Tools folder, double-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 Citrix server uses to update Citrix ICA Clients. The main window shows the ICA Clients currently configured in the database.


Creating a New Client Update Database

The 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 a shared network drive. Multiple Citrix servers can be configured to use one shared client update database.

To create a new client update database

1.	From the Database menu, click New. The Path for the new Client Update Database 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 new database is opened.


Setting a Default Database

An existing client update database can be used by multiple Citrix servers. If the client update database is on a shared network drive, use the ICA Client Update Configuration utility to configure all Citrix servers to use the shared database.

To specify a new default database for one or more Citrix servers

1.	From the Database menu, click Open. The Open Existing Database dialog box 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 dialog box appears:

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

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

5.	Click OK.


Configuring the Properties of the Client Update Database

Use the Database Properties dialog box to configure the current client update database.

To configure the properties of the Client Update Database

•	On the Database menu, click Properties. The Database Properties dialog box appears:

Clear the Enabled check box to disable this client update database. Citrix ICA Clients are not updated if the database is not enabled.

The Default update properties for clients options specify the default behavior for Citrix ICA Clients added to the update database. If you change the properties of an individual client in the database, those properties will override the default properties.

In Client Download Mode, click Ask user to allow the user to choose to accept or postpone the client update. Click Notify user to notify the user of the client update and require the update. Click Transparent to update the user's ICA Client without notifying the user.

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

In Update Mode, select the Force Disconnection check box to require users to disconnect and complete the update. By default, users can choose whether to disconnect and complete the client update after the new client files are downloaded. Clear the Allow background download check box to force users to wait for all client files to download before continuing. By default, users can choose whether to download new client files in the background and continue working.

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

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 Citrix server. When the specified number of client updates are occurring, new client connections are not updated. When the number of client updates drops below the specified maximum, new client connections are updated.


Adding and Removing Citrix ICA Clients

Use the ICA Client Update Configuration utility to add Citrix ICA Clients to and remove them from the database.

To add a new Citrix ICA Client to the client update database

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

Enter the path to the client installation file in Client Installation File or click Browse.

The client installation file, Update.ini, is located in %SystemRoot%\System32\Clients\Ica\ica32\disks\disk1.

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 any changes, click Next to continue.

3.	The Update Options dialog box appears.

The Update Options dialog box controls how the client update occurs. These options for each client override the settings specified for the database as a whole on the Database Properties dialog box.

In Client Download Mode, click Ask user to give the user the option to accept or postpone the client update. Click Notify user to notify the user of the client update and require the update. Click Transparent to update the user's ICA Client without notifying the user.

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

By default, users can choose to disconnect and complete the client update after the new client files are downloaded. Select the Force Disconnection check box to require users to disconnect and complete the update.

By default, users can choose to download new client files in the background and continue working. Clear the Allow Background Download check box to force users to wait for all client files to download before continuing.

You can optionally enter a message in Display this message on the user terminal. The user can view this message at the start of the client update by clicking 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 NT event log to report status messages and update errors.

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

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.

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 the auto client update.

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

6.	Click Finish to copy the Citrix ICA Client installation files into the client update database.

To remove a Citrix ICA Client from the database

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

2.	From the Client menu, click Delete. A dialog box displays the selected client information and asks for confirmation. Click OK to remove the client.

The Citrix ICA Client is removed from the database.


Changing the Properties of a Citrix ICA Client in the Database

Use the Properties dialog box to maintain the configuration of a Citrix ICA Client in the client update database. The Properties dialog box contains four tabs: the Description tab, the Update Options tab, the Event Log tab, and the Client Files tab.

To modify the properties of a Citrix ICA Client in the database

1.	In ICA Client Update Configuration, click on the Citrix 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. The Product, 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 Citrix ICA Clients to this client. All other clients of the same product, model, and version are disabled.

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 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 to accept or postpone the client update. Click Notify user to notify the user of the client update and require the update. Click Transparent to update the user's ICA Client without notifying the user.

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

By default, users can choose whether to disconnect and complete the client update after the new client files are downloaded. Select the Force Disconnection check box to require users to disconnect and complete the update.

By default, users can choose to whether to download new client files in the background and continue working. Clear the Allow Background Download check box to force users to wait for all client files to download before continuing.

You can optionally enter a message in Display this message on the user terminal. The user can view this message at the start of the client update by clicking 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 status messages and update errors.

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

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.

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

The client update database stores the File Name, Group, Flags, FileSize, and File CRC for each file of a Citrix ICA Client.


Configuring the Citrix ICA Win32 Client


Overview

This chapter describes how to configure the ICA Win32 Client. Topics in this chapter include:

Mapping client devices

Mapping client drives

Mapping client printers

Mapping client COM ports

Mapping client audio

Connection Types

Configuring connections to Citrix servers and published applications


Mapping Client Devices

The Citrix ICA Client supports mapping devices on client computers so they are available to the user from within an ICA session. You do not need a network or RAS connection to use ICA client device mapping. Users can:

Transparently access local drives, printers, and COM ports

Cut and paste between the ICA session and the local Windows clipboard

Hear audio (system sounds and .wav files) played from the ICA session

During logon, the ICA Client informs the Citrix server of the available client drives, COM ports, and LPT ports. By default, client drives are mapped to server drive letters and server print queues are created for Windows ICA Client printers so they appear to be directly connected to the Citrix server. These mappings are available only for the current user during the current session. They are deleted when the user logs off and recreated the next time the user logs on.

You can use the net use and change client commands to map client devices not automatically mapped at logon. See the MetaFrame Administrator's Guide or the WINFRAME System Guide for information about the change client command.


Turning Off Client Device Mappings

On a MetaFrame server, specify client device mapping options in the Client Settings dialog box in Terminal Server Connection Configuration. On a WinFrame server, specify client device mapping options in Citrix Connection Configuration.

The Connection options control whether drives and printers are mapped to client drives and printers. If these options are cleared, the devices are still available but must be mapped to drive letters and port names manually.

Use the Client Mapping Overrides to disable client device connections.

Option	Description
Connect client drives at Logon	If this option is checked, the client computer's drives are automatically mapped at logon.
Connect client printers at Logon	If this option is checked, the client computer's printers are automatically mapped at logon. This option applies only to Windows clients and maps only printers already configured in Print Manager on the client computer. DOS printers must be manually mapped.
Default to main client printer	If this option is checked, the user's default client printer is configured as the default printer for the ICA session.
(inherit user config)	If this option is checked, the per-user settings in User Manager override these settings.


Mapping Client Drives

Client drive mapping allows drive letters on the Citrix server to be redirected to drives that exist on the client computer; for example: drive H in a Citrix user session can be mapped to drive C of the local computer running the Citrix ICA Client.

Client drive mapping is transparently built into the standard Citrix device redirection facilities. These mappings can be used by the File Manager or Explorer and your applications just like any other network mappings.

The Citrix server can be configured during installation to automatically map client drives to a given set of drive letters. The default installation mapping maps drive letters assigned to client drives starting with V and works backwards, assigning a drive letter to each fixed disk and CD-ROM. (Floppy drives are assigned their existing drive letters.) This method yields the following drive mappings in a client session:

Client drive letter	Is accessed by the Citrix server as:
A	A
B	B
C	V
D	U
The Citrix server can be configured so that the server drive letters do not conflict with the client drive letters; in this case the Citrix server drive letters are changed to higher drive letters. For example, changing Citrix server drives C to M and D to N allows client computers to access their C and D drives directly. This method yields the following drive mappings in a client session:

Client drive letter	Is accessed by the Citrix server as:
A	A
B	B
C	C
D	D
The drive letter used to replace the Citrix server drive C is defined during Setup. All other fixed disk and CD-ROM drive letters are replaced with sequential drive letters (for example; C->M, D->N, E->O). These drive letters must not conflict with any existing network drive mappings. If a network drive is mapped to the same drive letter as a Citrix server drive letter, the network drive mapping is not valid.

When an ICA Client computer connects to a Citrix server, client mappings are re-established unless automatic client device mapping is disabled. Automatic client device mapping can be configured for ICA connections and users. In the Client Settings dialog box, you can enable or disable automatic client device mapping for an ICA connection. The User Configuration dialog box in User Manager for Domains allows you to enable or disable automatic client device mapping for a user.


Mapping Client Printers

The Citrix ICA Win32 Client supports auto-created printers. With auto-created printers, users find their local printers mapped to their sessions and ready for use as soon as they connect.

After connecting to a Citrix server, users can view their local printers using Windows utilities.

Published applications and ICA server connections configured to run a specified initial program offer users the same access to their local printers, although users cannot use Windows utilities to view local printers. When connected to published applications, users can print to local printers in the same way they would print to a local printer when using locally run applications.

If the Connect Client Printers at Logon check box is checked in the terminal connection or user profile, the client printers are automatically connected when users log on and are deleted when they log off if the printers do not contain any print jobs. If print jobs are present, the printer (and its associated jobs) is retained.

If users do not want the automatically created printers deleted when they log off, use Print Manager in the ICA session to view the Properties dialog box for the client printer. This dialog box contains a Comment field (on MetaFrame servers) or a Description field (on WINFRAME servers) that contains the string Auto Created Client Printer for automatically created client printers. If you modify or delete this description, the printer is not deleted at logoff. Subsequent logons will use the printer already defined and not modify it. If users change the Windows printer settings, they will not automatically be set in this case. One reason for not wanting them deleted may be the use of custom print settings.

If your user and terminal connection profile do not specify Connect Client Printers at Logon, you can use Print Manager to connect to a client printer. These printers are not automatically deleted when you log off.

To view mapped client printers when connected to a MetaFrame server

•	While connected to the MetaFrame server, double-click My Computer on the remote desktop and then double-click Printers. The Printers dialog box appears:

The Printers screen displays the local printers mapped to the ICA session. The name of the printer takes the form clientname#printername, where clientname is the unique name given to the client computer during ICA Client Setup and printername is the Windows printer name. In this example ICA session, a client machine called "Snoop40" has access to its local printer named "Laser." This name cannot be changed and is used to locate the specific printer. Because the Windows printer name is used and not the port name (as with DOS Client printing), multiple printers can share a printer port without conflict.

To view mapped client printers when connected to a WINFRAME server

•	While connected to the WINFRAME server, double-click Print Manager in the Main program group. The Print Manager appears:

Print Manager displays the local printers mapped to the ICA session. The name of the printer takes the form clientname#printername, where clientname is the unique name given to the client computer during ICA Client setup and printername is the Windows printer name. In this example ICA session, a client machine called "Snoop40" has access to its local printer named "Laser." This name cannot be changed and is used to locate the specific printer. Because the Windows printer name is used and not the port name (as with DOS Client printing), multiple printers can share a printer port without conflict.


Mapping Client COM Ports

Client COM port mapping allows devices attached to the client computer's COM ports to be used during ICA sessions on a Citrix server. These mappings can be used just like any other network mappings.

To map a client COM port

1.	Start the ICA Client and log on to the Citrix server.

2.	Start a DOS command prompt: on WINFRAME, double-click Command Prompt in the Main program group. On MetaFrame, click Start, then click Programs, then click Command Prompt.

3.	At the prompt, type net use comx: \\client\comz: where x is the number of the COM port on the server (ports 1 through 9 are available for mapping) and z is the number of the client COM port you want to map. Press ENTER.

4.	To confirm the operation, type net use at the prompt. The list that appears contains mapped drives, LPT ports, and mapped COM ports.

To use this COM port in a session on a Citrix server, install your device to the mapped name. For example, if you map COM1 on the client to COM5 on the server, install your COM port device on COM5 during the session on the server. Use this mapped COM port as you would a COM port on the client computer.

Note  COM port mapping is not TAPI-compatible. TAPI devices cannot be mapped to client COM ports.


Mapping Client Audio

Client audio mapping enables applications running on the Citrix server to play sounds through a Sound Blaster Pro-compatible sound device installed on the client computer. You can control the amount of bandwidth used by client audio mapping.

To configure ICA Client audio on a MetaFrame server

1.	Click ICA Settings in Terminal Server Connection Configuration.

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

To configure ICA Client audio on a WINFRAME server

1.	Click ICA Settings in Citrix Connection Configuration.

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

Client Audio Mapping can cause excessive load on the Citrix servers and the network. The higher the audio quality, the more bandwidth is required to transfer the audio data. Higher quality audio also uses more server CPU to process. Three different audio quality settings are available, or client audio mapping can be disabled completely.

Important  You can set audio quality on a per connection basis, but users can also set it on the client computer. If the client and server audio quality settings are different, the lower of the two qualities is used.

The Client Audio Quality options are:

High. This setting is recommended only for connections where bandwidth is plentiful and sound quality is important. This setting allows clients to play a sound file at its native data rate. Sounds at the highest quality level require about 1.3Mbps of bandwidth to play clearly. Transmitting this amount of data can result in increased CPU utilization and network congestion.

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

Low. This setting is recommended for low-bandwidth connections, including most modem connections. This setting causes any sounds sent to the client to be compressed to a maximum of 16Kbps. This compression results in a significant decrease in the quality of the sound. The CPU requirements and benefits of this setting are similar to those of the Moderate setting; however, the lower data rate allows reasonable performance for a low-bandwidth connection.


Connection Types

Using the Citrix ICA Win32 Client, users can connect to a Citrix server in the following ways:

By dialing into a Citrix server using the modem installed on the client PC. This method uses a serial connection to a Citrix server. (Custom ICA Connections only)

Over a direct serial cable connection to a Citrix server. This method uses a serial connection to a Citrix server. (Custom ICA Connections only)

Over the local or wide-area network connection between the client PC and the Citrix server. This method uses one of the following network protocols:

TCP/IP

IPX

SPX

NetBIOS

You can also use Microsoft's Remote Access Service (RAS) or Dial-Up Networking (DUN) in combination with the Citrix ICA Client to connect a client PC with a Citrix server. This type of connection requires:

The RAS or third-party serial PPP software is installed on the client PC.

The RAS server is in the same Microsoft network as the Citrix server.

The user dials into the RAS server to establish a connection between the client PC and the RAS server.

The user defines a network connection entry in Remote Application Manager for the network protocol that exists between the RAS server and the Citrix server.


Configuring a SOCKS Proxy Connection

You can configure the ICA Win32 Client to connect to a Citrix server through a SOCKS proxy server. This section describes:

Why you use a SOCKS proxy server

Where to locate your SOCKS proxy server


Using SOCKS to Direct ICA Traffic Through Firewalls

To limit access into and out of your Citrix servers, configure a SOCKS proxy server to handle connections between clients and the server. You can place the proxy server on either side of the firewall, or in some situations, on both sides of the firewall.

The benefits of using a SOCKS proxy server include:

Information hiding, where system names inside the firewall are not made known to systems outside the firewall through DNS (Domain Name System)

Authentication between an ICA Client and SOCKS proxy servers

Authentication between two SOCKS proxy servers

Relaying between two SOCKS proxy servers

Channeling different TCP connections through one connection

Proxying UDP broadcasts through a directed UDP transmission

The general procedure for connecting the ICA Win32 Client through a proxy is:

1.	Be sure that your firewall is configured and working properly.

2.	Install your SOCKS proxy server and test that it works with Web browsers.

3.	Configure and deploy the ICA Win32 Client.


Locating Your Proxy Server

You can locate your proxy server on either side of your firewall. In some situations, you may want to locate the proxy server on both sides of the firewall. Typical SOCKS proxy configurations are described below. See your proxy documentation for further details about placement and implementation of your proxy server.


Setting Up a Proxy between Clients and a Firewall (for Outbound Connections)

To restrict clients from connecting directly to servers outside your firewall, install a proxy server between the client systems and the firewall, as shown below.

The proxy server uses its authentication features to determine whether ICA Clients can access networks outside the firewall. Configure the firewall to pass only network traffic that comes from the firewall.


Setting Up a Proxy Between Citrix Servers and a Firewall (for Inbound Connections)

To protect your Citrix servers, install a proxy server between your servers and the firewall. You can configure the firewall in two ways:

Maximize Trust. Configure the firewall to pass only network traffic that is directed to the SOCKS proxy server. The proxy server performs the authentication of the ICA Client.

Minimize Risk. Configure the firewall to allow only connections from specific machines in addition to passing only network traffic that is directed to the SOCKS proxy server.


Setting Up a Virtual Private Network Using Two Proxy Servers

You can create a Virtual Private Network (VPN) between two sites by configuring a proxy server inside the firewall at both the client and server sites. Set up the firewalls to allow only directed UDP traffic between the two SOCKS proxy servers and TCP on the SOCKS port. For additional security, configure the SOCKS proxy server on the ICA client side to authenticate with the SOCKS proxy server on the Citrix server side. To obtain the address of a SOCKS proxy server within an outside firewall, contact the system administrator responsible for configuring that firewall.

For more information about configuring the ICA Win32 Client to use with a SOCKS proxy server, see "Configuring Firewall Settings for Application Sets" and "Configuring Firewall Settings for Custom ICA Connections" later in this chapter.


Configuring Connections to Citrix Servers and Published Applications

This section describes how to configure connections to Citrix servers and published applications. Program Neighborhood offers the user two methods of connection:

Connecting to Citrix servers and published applications using application sets

Connecting to Citrix servers and published applications using custom ICA connections

Applications are published on Citrix servers using Published Application Manager. For detailed information on application publishing, see your Citrix server documentation.


Using Application Sets

An application set is a user's view of the applications published on a given server farm, which that user is authorized to access. Applications published in an application set are pre-configured for such session properties as window size and colors and supported level of encryption, audio, and video. If these settings are not required to run the published application (such as a required level of encryption), they can be changed on the client machine at the application set level.

The following procedures describe how to configure the properties and settings of an application set.

Configuring connection properties for application sets

Configuring default options for application sets

Configuring login properties for application sets

Configuring general settings for application sets

Configuring bitmap caching for application sets

Configuring hotkeys for application sets

Configuring event logging for application sets


Configuring Connection Properties for Application Sets

To configure the connection properties for application sets:

1.	Start Program Neighborhood

2.	Select an application set

3.	In the Program Neighborhood toolbar, click Properties. The Properties dialog box appears.

4.	Click the Connection tab to display the Connection page.

From the Connection page, you can configure the following:

Connection Type: Choose a connection type for the application set. Select Local Area Network to connect to the Citrix server over a local network that covers a confined geographical area (such as an office building or complex). Select Wide Area Network to connect to the Citrix server over a network that covers a wide geographical area.

Server Location: Server location (also called the ICA Browser or server browsing) provides a method for a user at a network-connected Citrix ICA Client computer to view a list of all Citrix servers on the network that have ICA connections configured for that network protocol (IPX/SPX, TCP/IP, or NetBIOS) and a list of all published applications. Each network protocol maintains a separate and independent Master ICA Browser.

Tip  Set a specific server address for the Citrix server that functions as the Master ICA Browser when your network configuration uses routers or gateways, or to eliminate broadcasts on your network.

Network Protocol:  The Network Protocol field instructs the Citrix ICA Client what low-level network protocol to use to connect to the Citrix server.  The protocol that you select must be installed on both your local computer and the Citrix server to which you want to connect.

Server Group:  Use the Server Group and Address List fields to create lists of specific servers that you want to designate as primary and backup servers for connecting to application sets. Backup server groups provide business recovery for your client in the event that you cannot contact any servers in your primary group.

You can define up to three groups of Citrix 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 group for your client, the client attempts to contact all the servers within that group simultaneously (broadcasting) and the first server to respond is the one you connect to.

Use this field to designate whether the servers entered in the Address List field belong to your Primary, first backup (Backup 1), or second backup (Backup 2) group.

Address List: Use the address list field to view and change the list of Citrix servers used in the selected server group. If you have not selected any servers, [Auto-Locate] is selected by default.

Click Add to add a Citrix server to your server group's address list.

Click Delete to remove the selected Citrix server from the Address List.

If (Auto-Locate) is selected, the first server is located automatically.

Firewalls:  Click Firewalls to display the Firewall Settings page. Use the Firewall Settings page to configure the ICA Win32 Client to connect to a Citrix server through a SOCKS proxy server, or to use an alternate address to browse for Citrix servers or published applications that are inside a firewall from a client machine that is outside the firewall.

To configure the Firewall Settings for application sets

1.	Click Firewalls on the Connection properties page.

2.	Select Use alternate address for firewalls to browse for Citrix servers or published applications that are inside a firewall from a client machine that is outside the firewall. The firewall and the Citrix servers must be configured to map the internal network addresses of Citrix servers to external Internet addresses. Enter the external Internet address in the Address List.

3.	Click the check box next to Connect via SOCKS proxy. Enter the SOCKS proxy's IP address in the Address of proxy to use box. Enter the port number of the SOCKS proxy server (if different than 1080) in the Port box. See the online help for more information.

Note  Because you can enter only one SOCKS proxy server address,  you cannot configure separate SOCKS settings for primary and backup servers.

For more information, see "Configuring a SOCKS Proxy Connection".


Configuring Default Options for Application Sets

To configure the Options for application sets:

1.	Start Program Neighborhood

2.	Select an application set

3.	In the Program Neighborhood toolbar, click Properties. The Properties dialog box appears.

4.	Click the Default Options tab to display the Default Options page.

From the Default Options page, you can configure the following:

Use data compression: Data compression reduces the amount of data that needs to be transferred but requires additional processor resources to compress and decompress the data.  If your connection is bandwidth-limited, enabling data compression increases performance.

Use disk cache for bitmaps: Bitmap caching to disk stores commonly-used graphical objects such as bitmaps in a local cache on the client's hard disk space. If your connection is bandwidth-limited, enabling disk caching increases performance. If your client is on a high-speed LAN, you do not need disk caching. Dial-in connections have disk caching enabled by default.

Queue mouse movements and keystrokes: Queuing causes the client to send mouse and keyboard updates less frequently to the Citrix server. Check this option to reduce the number of network packets sent from the ICA Client to the Citrix server. Leaving this option unchecked makes the session more responsive to keyboard and mouse movements. Checking this option improves performance if you dial in to RAS and then use a network to connect.

Turn off desktop integration for this application set: You can configure Program Neighborhood to create desktop shortcuts and add items to the Start menu for published applications. If users do not want published applications sent directly to the desktop, they can select this checkbox.

Enable sound: Check this box to enable sound support. The client computer must have a Sound Blaster 16-compatible sound card installed. Published applications can then play sounds on the client.

Select one of the following values for Quality:

High. This setting is recommended only for connections where bandwidth is plentiful and sound quality is important. This setting allows clients to play a sound file at its native data rate. Sounds at the highest quality level require about 1.3Mbps of bandwidth to play clearly. Transmitting this amount of data can result in increased CPU utilization and network congestion.

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

Low. This setting is recommended for low-bandwidth connections, including most modem connections. This setting causes any sounds sent to the client to be compressed to a maximum of 16Kbps. This compression results in a significant decrease in the quality of the sound. The CPU requirements and benefits of this setting are similar to those of the Moderate setting; however, the lower data rate allows reasonable performance for a low-bandwidth connection.

Encryption Level: Select the level of encryption for the ICA connection. The default level is Basic. Strong encryption using the RC5 algorithm is available with SecureICA Services. SecureICA Services enables RSA RC5 encryption with 40, 56, or 128-bit session keys. Select RC5 128-bit Login Only to use encryption during authentication.

The Citrix server must be configured to allow the selected encryption level or greater. For example, if the Citrix server is configured to allow RC5 56-bit connections, the ICA client can connect with RC5 56 or 128-bit encryption.

Note  Selecting RC5 encryption disables automatic logon to the Citrix server.

Window Size: This field specifies the window size that a published application runs in.

If you select Seamless Windows, the published application appears on your local desktop in a separate, seamless window.

Window Colors: This field specifies the number of colors displayed.

If the server-configured default settings are being used by any of the properties, the Use Server Default box is checked. To change the settings, de-select this check box and choose new settings from the drop-down menu. Click OK to save these settings.


Configuring Login Properties for Application Sets

To configure login properties for application sets

1.	Start Program Neighborhood

2.	Select an application set

3.	From the Program Neighborhood toolbar, click Properties. The Properties dialog box appears.

4.	Click the Login Properties tab.

5.	Enter a valid username, domain, and password for this application set.

6.	To save this password after you exit Program Neighborhood and close all connections, select Save password. If you leave this box unchecked, this password is only retained as long as Program Neighborhood and all current connections are open.

7.	Click OK.


Preventing Users from Saving Passwords

Program Neighborhood provides administrators with the ability to disable password saving for a single application set or all application sets. By setting a parameter in one of two Program Neighborhood Ini files, you can prevent the Save Password checkbox from appearing in the Login Properties tab of an application set's properties and in the initial logon screen a user sees when authenticating to an application set.

To disable password saving, you must add a parameter and value to one of two Program Neighborhood Ini files located in the Program Neighborhood installation directory. The file you choose to add the parameter and value to determines which application sets prohibit password saving. Add the parameter and value to:

Appsrv.ini to prevent all application sets from saving password information

Pn.ini to prevent individual application sets from saving password information

Note  If you add the parameter to both files, the parameter in Appsrv.ini overrides the Pn.ini entry if the Appsrv.ini entry is set to On. If the entry in Appsrv.ini is set to Off or if it does not exist, the entry in Pn.ini is used (if it exists). Setting an entry equal to Off and leaving it out of the Ini files both result in Save Password checkboxes appearing in the Program Neighborhood user interface.

To disable password saving for all application sets

1.	Exit Program Neighborhood if it is running. Make sure all Program Neighborhood components, including the Connection Center, are closed.

2.	Load the file Appsrv.ini in a text editor.

3.	Locate the section named [WFClient].

4.	Add the following text to the list of parameters and values in [WFClient]:

NoSavePwordOption=On

If the parameter already exists, make sure its value is set to On.

5.	Save the file and exit the text editor.

6.	Start Program Neighborhood.

Adding this parameter and setting it equal to On prevents users from saving passwords for all application sets. Any existing cached passwords are deleted.

To disable password saving for individual application sets

1.	Exit Program Neighborhood if it is running. Make sure all Program Neighborhood components, including the Connection Center, are closed.

2.	Load the file Pn.ini in a text editor.

3.	Locate the section name that corresponds to the application set on which you want to disable password saving; for example, [MyAppSet].

4.	Add the following text to the list of parameters in the section:

NoSavePwordOption=On

If the parameter already exists, make sure its value is set to On.

5.	Add the parameter and value to each application set section as desired.

6.	Save the file and exit the text editor.

7.	Start Program Neighborhood.

Adding this parameter and setting it equal to On prevents users from saving passwords for the specified application set(s). Any existing cached passwords are deleted.


Configuring General Settings  for Application Sets

To configure the general settings for application sets

1.	Start Program Neighborhood

2.	Select an application set

3.	From the Tools menu, click Settings to display the Settings dialog box.

4.	Click the General tab.

From the General  page, you can configure the following settings:

Client Name: This field allows you to change the name of the client computer. The Citrix server uses the client name to uniquely identify resources (such as mapped printers and disk drives) associated with a given client PC. The client name must be unique for each computer running the Citrix ICA Client.

Serial Number: This is the serial number of the ICA Client software. This field is necessary only when you are using the Citrix ICA Client with a product such as WINFRAME Host/Terminal, which requires each client to have a Citrix PC Client Pack serial number in order to connect to the server. If a serial number is required, you must enter it exactly as it appears on the Serial Number card. The Serial Number field is not used by MetaFrame servers.

Keyboard Layout: Allows you to specify the keyboard layout of your client computer. The Citrix server uses the keyboard layout information to configure your user session for your keyboard layout. The default value of (User Profile) uses the keyboard layout specified in your user profile.

Keyboard Type: Allows you to specify the keyboard type of your client computer. The Citrix server uses the keyboard type information to configure your user session for your keyboard type. Use the default value of Default for most English and European keyboards. When used with a Japanese keyboard, Default auto-detects the keyboard type.

Display Connect To screen when making Dial-in Connections: Check this checkbox to display the Connect To screen when you make a dial-in connection.

Display terminal window when making Dial-in Connections: Check this box if your dial-in configuration includes third-party products, such as security devices and X.25 PADs, that require an ASCII dialog before connecting to the Citrix server.

Allow automatic client updates: Check this box to allow the Citrix server to update your Citrix ICA Client software when newer versions become available. When the Citrix server detects an outdated client version, it notifies you that a newer version is available and replaces the ICA Client files.


Configuring Bitmap Caching for Application Sets

To configure the general settings for application sets

1.	Start Program Neighborhood

2.	Select an application set

3.	From the Tools menu, click Settings to display the Settings dialog box.

4.	Click the Bitmap Cache tab.

From the Bitmap Cache page, you can configure the following settings:

Amount of disk space to use: Use this tool to configure the amount of disk space as a percentage of the partition containing the caching directory.

Bitmap cache directory: The default directory where the cached data is stored is displayed in this field.

Change Directory: If you want to specify a new directory for cached data, click Change Directory button to display the Change Bitmap Cache Directory dialog box.

Minimum size bitmap to be cached: The size of the smallest bitmap to be cached to disk.

Clear cache: Click this button to remove all cached data from the directory.

Tip  It is not recommended to clear the cache if there are any ICA connections open. Before clearing the cache, verify that all ICA connections are closed.


Configuring Hotkeys for Application Sets

To configure the hotkeys for application sets

1.	Start Program Neighborhood

2.	Select an application set

3.	From the Program Neighborhood menu bar, click Settings. The Settings dialog box appears.

4.	Click the Hotkeys tab.

5.	For each hotkey in the list, select a shift state and a key.

6.	You can disable the hotkey by selecting (none) for the key.

Hotkeys are used to control the behavior of the Win32 client, and as substitutes for the standard Windows hotkeys for a published application.

The fields on the Hotkeys page are:

Task List: The Task List hotkey displays the Windows Task List for your local Windows NT 3.51 computer or the local Start menu if your local machine is a Windows NT 4.0 or Windows 95/98 computer.

Close Remote Application: The Close Remote Application hotkey disconnects the published application from the Citrix server and closes the Citrix ICA Client window. The behavior of this hotkey is the same as choosing Close from the system menu of the ICA Client window.

Closing the published application in this manner either leaves the associated application in a disconnected state on the Citrix server, or exits the application on the Citrix server, depending on how the server is configured.

Toggle Title Bar: This hotkey causes the ICA Client window to alternately display and hide its title bar. When the title bar is displayed, the ICA Client window can be moved or closed.

Tip  This hotkey must be used to return to a seamless window after accessing the Windows NT Security dialog box using the CTRL+ALT+DEL hotkey.

CTRL-ALT-DEL:  This hotkey causes the CTRL-ALT-DEL key sequence to be sent to the serverthat is running the published application.  In Windows NT, the CTRL-ALT-DEL key sequence causes a Windows NT session to switch to the Windows NT Security desktop.

CTRL-ESC: This hotkey causes the CTRL-ESC key sequence to be sent to the server that is running the published application. CTRL-ESC is a standard Windows hotkey.  Refer to your Windows documentation for more information on the CTRL-ESC hotkey.

ALT-ESC: This hotkey causes the ALT-ESC key sequence to be sent to the server that is running the published application.  ALT-ESC is a standard Windows hotkey.  Refer to your Windows documentation for more information on the ALT-ESC hotkey.

ALT-TAB: This hotkey causes the ALT-TAB key sequence to be sent to the server that is running the published application.  ALT-TAB is a standard Windows hotkey.  Refer to your Windows documentation for more information on the ALT-TAB hotkey.

ALT-BACKTAB: This hotkey causes the ALT-SHIFT-TAB key sequence to be sent to the server that is running the published application.  ALT-SHIFT-TAB is a standard Windows hotkey.  Refer to your Windows documentation for more information on the ALT-SHIFT-TAB hotkey.

CTRL-SHIFT-ESC:  This hotkey causes the CTRL-SHIFT-ESC key sequence to be sent to the server that is running the published application.  CTRL-SHIFT-ESC is a standard Windows NT 4.0 hotkey.  Refer to your Windows NT 4.0 documentation for more information on the CTRL-SHIFT-ESC hotkey.


Configuring Event Logging for Application Sets

The Event Logging page allows you to instruct the Citrix ICA Client whether or not to keep a log of various events that occur while running published applications.

To configure event logging for your application set:

1.	Start Program Neighborhood

2.	Select an application set

3.	From the Program Neighborhood menu bar, click Settings. The Settings dialog box appears.

4.	Click the Event Logging tab.

From the Event Logging page, you can configure the following settings:

Event Log File: Enter the name of the file to log Citrix ICA Client events to in the Name field.

Select the Overwrite existing event log button to cause the event log file to be overwritten with new events when a published application is run.

Select the Append to existing event log button to keep old events and add new ones to the end of the file.

Log Events: Use these buttons to select the event categories that you want to log.  If no events are selected, no logging takes place.

Five event categories can be selected for logging:

Connections and Disconnections: Logs an event whenever the Citrix ICA Client connects and disconnects from a Citrix Server.  This category is selected by default.

Errors: Logs an event whenever an error is encountered by the Citrix ICA Client.  This category is selected by default.

Data Transmitted: Logs an event for each packet of information sent by the Citrix ICA Client to the Citrix server. This is intended primarily for technical support purposes.

Data Received: Logs an event for each packet of information received by the Citrix ICA Client from the Citrix server. This category is intended primarily for technical support purposes.

Keyboard and Mouse Data: Logs an event whenever you press a key on the keyboard or move the mouse.  This category is intended for technical support purposes.


Using Custom ICA Connections

A custom ICA connection is a connection to an existing Citrix server outside of a server farm scope of management, or to an application published prior to the installation of MetaFrame 1.8  and WINFRAME 1.8 that cannot be migrated into a server farm. Applications published in this way are not enabled for automatic configuration of Program Neighborhood sessions.

The following procedures describe how to configure the properties and settings of custom ICA connections from the Win32 client:

Configuring connection properties for custom ICA connections

Configuring server location properties for custom ICA connections

Configuring options for custom ICA connections

Configuring default options for custom ICA connections

Configuring login properties for custom ICA connections

Configuring application properties for custom ICA connections

Configuring general settings for custom ICA connections

Configuring bitmap caching for custom ICA connections

Configuring hotkeys for custom ICA connections

Configuring event logging for custom ICA connections


Configuring Connection Properties for Custom ICA Connections

Connection settings for custom ICA connections are configured per published application or published server desktop.

To configure the connection properties for a custom ICA connection

1.	Start Program Neighborhood

2.	Double-click Custom ICA Connections.

3.	Select the custom ICA connection to configure.

4.	Select the custom ICA connection you want to configure.

5.	From the Program Neighborhood toolbar, click Properties. The Properties dialog box appears.

6.	Click the Connection tab to display the Connection page.

The Connection page has the following fields:

 Connection Type: Choose a Network or Dial-In connection type for the application set. Select Local Area Network to connect to the Citrix server over your local network. Select Wide Area Network to connect to the Citrix server from a remote location. Select ICA Dial-in to connect to the Citrix server using a modem.

Network Protocol:  The Network Protocol field instructs the Citrix ICA Client what low-level network protocol to use to connect to the Citrix server.  The protocol that you select must be installed on the local computer and must also be in use on the Citrix server that you wish to connect to.

Server: When the Server radio button is selected, this field specifies the Citrix server that will be used to connect and run the published application.

Note  If the list box is empty or the name of the Citrix server you want to connect to is not present in the list, you may need to enter an address for the Citrix server, based on the Network Protocol selected.  For a TCP/IP Network Protocol, type in the IP address of the Citrix server, for example: 128.128.1.50.  For a IPX or SPX Network Protocol, type in the network : node of the Citrix server, for example: AA:0000E8C046BF.

Published Application: Select this radio button to connect to a published application.  Choose a published application from the drop-down list.


Configuring Server Location Settings for Custom ICA Connections

Although connection properties are configured on a per application basis, you can configure the server location settings for all custom ICA connections.

To configure the server location settings for all custom applications:

1.	Right-click in the Custom ICA Connections window of Program Neighborhood.

2.	Select Properties from the shortcut menu. The Connection tab of the Custom ICA Connections Properties dialog box appears.

Server Location: Server location (also called the ICA Browser or server browsing) provides a method for a user at a network-connected Citrix ICA Client computer to view a list of all Citrix servers on the network that have ICA connections configured for that network protocol (IPX/SPX, TCP/IP, or NetBIOS) and a list of all published applications. Each network protocol maintains a separate and independent Master ICA Browser.

Tip  Set a specific server address for the Citrix server that functions as the Master ICA Browser when your network configuration uses routers or gateways, or to eliminate broadcasts on your network.

Network Protocol:  The Network Protocol field instructs the Citrix ICA Client what low-level network protocol to use to connect to the Citrix server.  The protocol that you select must be installed on your local computer and must also be in use on the Citrix server that you wish to connect to.

Server Group:  Use the Server Group and Address List fields to create lists of specific servers that you want to designate as primary and backup servers for connecting to application sets. Backup server groups provide business recovery for your client in the event that you cannot contact any servers in your primary group.

You can define up to three groups of Citrix 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 group for your client, the client attempts to contact all the servers within that group simultaneously (broadcasting) and the first server to respond is the one you connect to.

Use this field to designate whether the servers entered in the Address List field belong to your Primary, first backup (Backup 1), or second backup (Backup 2) group.

Address List: Use the address list field to view and change the list of Citrix servers used in the selected server group. If you have not selected any servers, [Auto-Locate] is selected by default.

Click Add to add a Citrix server to your server group's address list.

Click Delete to remove the selected Citrix server from the Address List.

If (Auto-Locate) is selected, the first server is located automatically.

Connect via SOCKS proxy: Click the check box next to Connect via SOCKS proxy to configure the ICA Win32 Client to connect to a Citrix server through a SOCKS proxy server.  Enter the IP address of the SOCKS proxy server in the Address of proxy to use box. Enter the port number of the SOCKS proxy server (if different than 1080) in the Port box.


Configuring Options for Custom ICA Connections

To configure the options for a custom ICA connection:

1.	Start Program Neighborhood

2.	Double-click Custom ICA Connections.

3.	Select the custom ICA connection to configure.

4.	Select the custom ICA connection you want to configure.

5.	In the Program Neighborhood toolbar, click Properties. The Properties dialog box appears.

6.	Click the Options tab to display the Options page.

From the Options page, you can configure the following:

Use data compression: Data compression reduces the amount of data that needs to be transferred but requires additional processor resources to compress and decompress the data.  If your connection is bandwidth-limited, enabling data compression increases performance.

Use disk cache for bitmaps: Bitmap caching to disk stores commonly-used graphical objects such as bitmaps in a local cache on the client's hard disk space. If your connection is bandwidth-limited, enabling disk caching increases performance. If your client is on a high-speed LAN, you do not need disk caching. Dial-in connections have disk caching enabled by default.

Queue mouse movements and keystrokes: Queuing causes the client to send mouse and keyboard updates less frequently to the Citrix server. Check this option to reduce the number of network packets sent from the ICA Client to the Citrix server. Leaving this option unchecked makes the session more responsive to keyboard and mouse movements. Checking this option improves performance if you dial in to RAS and then use a network to connect.

Enable sound: Check this box to enable sound support. The client computer must have a Sound Blaster 16-compatible sound card installed. Published applications can then play sounds on the client.

Select one of the following values for Quality:

High. This setting is recommended only for connections where bandwidth is plentiful and sound quality is important. This setting allows clients to play a sound file at its native data rate. Sounds at the highest quality level require about 1.3Mbps of bandwidth to play clearly. Transmitting this amount of data can result in increased CPU utilization and network congestion.

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

Low. This setting is recommended for low-bandwidth connections, including most modem connections. This setting causes any sounds sent to the client to be compressed to a maximum of 16Kbps. This compression results in a significant decrease in the quality of the sound. The CPU requirements and benefits of this setting are similar to those of the Moderate setting; however, the lower data rate allows reasonable performance for a low-bandwidth connection.

Encryption Level: Select the level of encryption for the ICA connection. The default level is Basic. Strong encryption using the RC5 algorithm is available with SecureICA Services. SecureICA Services enables RSA RC5 encryption with 40, 56, or 128-bit session keys. Select RC5 128-bit Login Only to use encryption during authentication.

The Citrix server must be configured to allow the selected encryption level or greater. For example, if the Citrix server is configured to allow RC5 56-bit connections, the ICA client can connect with RC5 56 or 128-bit encryption.

Note  Selecting RC5 encryption disables automatic logon to the Citrix server.

Window Size: This field specifies the window size that a published application runs in.

If you select Seamless Windows, the published application appears on your local desktop in a separate, seamless window.

Window Colors: This field specifies the number of colors displayed.

If the server-configured default settings are being used by any of the properties, the Use Custom Default box is checked. To change the settings, de-select this check box and choose new settings from the drop-down menu. Click OK to save these settings.


Configuring Default Options for all Custom ICA Connections

You can configure default option settings for all custom ICA connections. The user can disable these settings for a particular custom ICA connection by de-selecting the Use Custom Default checkbox.

To configure the default options for all custom applications:

1.	Right-click in the Custom ICA Connections window of Program Neighborhood.

2.	Select Properties from the shortcut menu to display the Custom ICA Connections Properties page.

3.	Click the Default Options tab.

The following default options can be configured:

Enable sound

Encryption level

Window colors

Window size

For details on these properties, see the topic "Configuring Options for Custom ICA Connections" earlier in this section.


Configuring Login Properties for Custom ICA Connections

To configure login properties for a custom ICA connection

1.	Start Program Neighborhood

2.	Double-click Custom ICA Connections.

3.	Select the custom ICA connection to configure.

4.	In the Program Neighborhood toolbar, click Properties. The Properties dialog box appears.

5.	Click the Login Properties tab.

6.	Enter a valid username, domain, and password for this ICA Connection.

7.	Click OK.


Configuring General Settings for Custom ICA Connections

To configure the general settings for custom ICA connections

1.	Start Program Neighborhood

2.	Double-click Custom ICA Connections.

3.	Select a custom ICA connection

4.	From the Tools menu, click Settings to display the Settings dialog box.

5.	Click the General tab.

From the General  page, you can configure the following settings:

Client Name: This field allows you to change the name of the client computer. The Citrix server uses the client name to uniquely identify resources (such as mapped printers and disk drives) associated with a given client PC. The client name must be unique for each computer running the Citrix ICA Client.

Serial Number: The serial number of your Citrix ICA Client software is only necessary when you are using the version of the Citrix ICA Client supplied with the Citrix PC Client Pack, in which case you must enter the Client License number supplied with the PC Client Pack before you are allowed to access the Citrix server.

Keyboard Layout: Allows you to specify the keyboard layout of your client computer. The Citrix server uses the keyboard layout information to configure your user session for your keyboard layout. The default value of (User Profile) uses the keyboard layout specified in your user profile.

Keyboard Type: Allows you to specify the keyboard type of your client computer. The Citrix server uses the keyboard type information to configure your user session for your keyboard type. Use the default value of Default for most English and European keyboards. When used with a Japanese keyboard, Default auto-detects the keyboard type.

Display Connect To screen when making Dial-in Connections: Check this checkbox to display the Connect To screen when you make a dial-in connection.

Display terminal window when making Dial-in Connections: Check this box if your dial-in configuration includes third-party products, such as security devices and X.25 PADs, that require an ASCII dialog before connecting to the Citrix server.

Allow automatic client updates: Check this box to allow the Citrix server to update your Citrix ICA Client software when newer versions become available. When the Citrix server detects an outdated client version, it notifies you that a newer version is available and replaces the ICA Client files.


Configuring Bitmap Caching for Custom ICA Connections

To configure the general settings for custom ICA connections

1.	Start Program Neighborhood

2.	Double-click Custom ICA Connections.

3.	Select a custom ICA connection

4.	From the Tools menu, click Settings to display the Settings dialog box.

5.	Click the Bitmap Cache tab.

From the Bitmap Cache page, you can configure the following settings:

Amount of disk space to use: Use this tool to configure the amount of disk space as a percentage of the partition containing the caching directory.

Bitmap cache directory: The default directory where the cached data is stored is displayed in this field.

Change Directory: If you want to specify a new directory for cached data, click Change Directory button to display the Change Bitmap Cache Directory dialog box.

Minimum size bitmap to be cached: The size of the smallest bitmap to be cached to disk.

Clear cache: Click this button to remove all cached data from the directory.

Tip  It is not recommended to clear the cache if there are any ICA connections open. Before clearing the cache, verify that all ICA connections are closed.


Configuring Hotkeys for Custom ICA Connections

To configure the hotkeys for custom ICA connections

1.	Start Program Neighborhood

2.	Double-click Custom ICA Connections.

3.	Select a custom ICA connection

4.	From the Program Neighborhood menu bar, click Settings. The Settings dialog box appears.

5.	Click the Hotkeys tab.

6.	For each hotkey in the list, select a shift state and a key.

7.	You can disable the hotkey by selecting (none) for the key.

Hotkeys are used to control the behavior of the Win32 client, and as substitutes for the standard Windows hotkeys for a published application.

The fields on the Hotkeys page are:

Task List: The Task List hotkey displays the Windows Task List for your local Windows NT 3.51 computer or the local Start menu if your local machine is a Windows NT 4.0 or Windows 95/98 computer.

Close Remote Application: The Close Remote Application hotkey disconnects the published application from the Citrix server and closes the Citrix ICA Client window. The behavior of this hotkey is the same as choosing Close from the system menu of the ICA Client window.

Closing the published application in this manner either leaves the associated application in a disconnected state on the Citrix server, or exits the application on the Citrix server, depending on how the server is configured.

Toggle Title Bar: This hotkey causes the ICA Client window to alternately display and hide its title bar. When the title bar is displayed, the ICA Client window can be moved or closed.

Tip  This hotkey must be used to return to a seamless window after accessing the Windows NT Security dialog box using the CTRL+ALT+DEL hotkey.

CTRL-ALT-DEL:  This hotkey causes the CTRL-ALT-DEL key sequence to be sent to the serverthat is running the published application.  In Windows NT, the CTRL-ALT-DEL key sequence causes a Windows NT session to switch to the Windows NT Security desktop.

CTRL-ESC: This hotkey causes the CTRL-ESC key sequence to be sent to the server that is running the published application. CTRL-ESC is a standard Windows hotkey.  Refer to your Windows documentation for more information on the CTRL-ESC hotkey.

ALT-ESC: This hotkey causes the ALT-ESC key sequence to be sent to the server that is running the published application.  ALT-ESC is a standard Windows hotkey.  Refer to your Windows documentation for more information on the ALT-ESC hotkey.

ALT-TAB: This hotkey causes the ALT-TAB key sequence to be sent to the server that is running the published application.  ALT-TAB is a standard Windows hotkey.  Refer to your Windows documentation for more information on the ALT-TAB hotkey.

ALT-BACKTAB: This hotkey causes the ALT-SHIFT-TAB key sequence to be sent to the server that is running the published application.  ALT-SHIFT-TAB is a standard Windows hotkey.  Refer to your Windows documentation for more information on the ALT-SHIFT-TAB hotkey.

CTRL-SHIFT-ESC:  This hotkey causes the CTRL-SHIFT-ESC key sequence to be sent to the server that is running the published application.  CTRL-SHIFT-ESC is a standard Windows NT 4.0 hotkey.  Refer to your Windows NT 4.0 documentation for more information on the CTRL-SHIFT-ESC hotkey.


Configuring Event Logging for Custom ICA Connections

To configure event logging for custom ICA connections

1.	Start Program Neighborhood

2.	Double-click Custom ICA Connections.

3.	Select a custom ICA connection

4.	From the Program Neighborhood menu bar, click Settings. The Settings dialog box appears.

5.	Click the Event Logging tab.

From the Event Logging page, you can configure the following settings:

Event Log File: Enter the name of the file to log Citrix ICA Client events to in the Name field. The default value is Wfcwin32.log in the directory containing the Win32 Client.

Select the Overwrite existing event log button to cause the event log file to be overwritten with new events when a published application is run.

Select the Append to existing event log button to keep old events and add new ones to the end of the file.

Log Events: Use these buttons to select the event categories that you want to log.  If no events are selected, no logging takes place.

Five event categories can be selected for logging:

Connections and Disconnections: Logs an event whenever the Citrix ICA Client connects and disconnects from a Citrix Server.  This category is selected by default.

Errors: Logs an event whenever an error is encountered by the Citrix ICA Client.  This category is selected by default.

Data Transmitted: Logs an event for each packet of information sent by the Citrix ICA Client to the Citrix server. This is intended primarily for technical support purposes.

Data Received: Logs an event for each packet of information received by the Citrix ICA Client from the Citrix server. This category is intended primarily for technical support purposes.

Keyboard and Mouse Data: Logs an event whenever you press a key on the keyboard or move the mouse.  This category is intended for technical support purposes.