Citrix Systems, Inc.

Read Me
=======
ICA Win32 Clients (ICA 32-bit Windows Clients) for Citrix MetaFrame
Application Server product family
Products:

ICA Win32 Program Neighborhood Agent (Ica32a.exe, Ica32a.msi)

ICA Win32 Program Neighborhood Client (Ica32.exe, Ica32.msi, Wfica.c

ab)
ICA Win32 Web Client (Ica32t.exe, Wficac.cab, Wficat.cab)
Version:

7.0

Replaces:

All versions prior to February 2003

Date:

May 01, 2003

Language:

English (US)

Copyright 2001-2003, Citrix Systems, Inc. All rights reserved.

All other trademarks and registered trademarks are the property of
their owners.
Introduction
============
This document contains last-minute information about the ICA Win32
Clients, and includes descriptions of the issues that are resolved
in this version.
Where to Find Documentation
===========================
For more information about the ICA Win32 Clients, see the ICA Win32
Clients Administrator's Guide (ICA_Win32_Guide.pdf), located in the
ICAClientDoc folder of your Components CD. To view, search, and
print the documentation, you need Acrobat Reader 4 or above. You can
download Acrobat Reader from the Adobe Web site at
http://www.adobe.com/.
For the latest updates to Citrix documentation, visit the Citrix Web
site at
http://www.citrix.com/.
Viewing or Printing this Document
=================================
When viewing this document in Notepad, if the text does not wrap in
the window, choose Edit > Word Wrap (Windows NT 4) or Format > Word
Wrap (Windows 2000).
Before printing this document, adjust the window width to fit your
printer paper.
Overview of the ICA Win32 Clients

=================================
ICA Clients are the components of MetaFrame XP that users run on
their computers to access applications running on MetaFrame XP servers.
ICA Clients combine ease of deployment and use, and offer quick,
secure access to applications, content, and entire computer desktops
published on MetaFrame XP servers.
Each ICA Win32 Client offers a robust and easy-to-manage solution for
delivering your published resources to 32-bit Windows desktops. To
decide which ICA Client or Clients best fit your needs, see Chapter 2
of the ICA Win32 Clients Administrator's Guide (ICA_Win32_Guide.pdf),
located in the ICAClientDoc folder of your Components CD.
Supported Windows Operating Systems
----------------------------------The ICA 32-bit Windows Clients support the following platforms:
Windows XP
Windows 2000
Windows Me
Windows 98
Windows 95
Windows NT 4.0
Windows NT 3.51 (ICA Win32 Program Neighborhood Client and Web
Client only)
ICA Win32 Program Neighborhood Agent
-----------------------------------If you want users to access your published resources entirely from
within their familiar Windows desktop environment, use the ICA Win32
Program Neighborhood Agent.
In conjunction with the new Web Interface for MetaFrame XP, you can
transparently integrate your published resources with users
desktops. Users access your resources by clicking icons on their
Windows desktop, in the Start menu, in the Windows System Tray, or
any combination thereof. The configuration data for all Program
Neighborhood Agents is defined in a single configuration file. As a
result, you can dynamically manage and control your client population
network-wide from a single location.
ICA Win32 Web Client
-------------------If you want users to access your published resources from within their
familiar Web browser, use the ICA Win32 Web Client.
You can use the ICA Web Client with the new Web Interface for
MetaFrame XP to create an application portal on your corporate
intranet or the Internet that presents users with links to your
published resources. Users access your portal with a standard Web
browser. The ICA Web Client provides the engine needed to launch
published applications.
ICA Win32 Program Neighborhood Client
------------------------------------If you want users to access your published resources without the new

Web Interface for MetaFrame XP, use the ICA Win32 Program
Neighborhood Client:
Using the ICA Program Neighborhood Client, users browse for application
sets or create custom ICA connections to MetaFrame servers or to
individual published resources. Icons representing application sets
and custom ICA connections appear in the ICA Client s Program
Neighborhood window. You can configure numerous settings before you
deploy the client software to users. This allows users to install the
client and begin using it immediately, without having to configure
settings.
Installation Instructions for the ICA Win32 Clients
===================================================
For step-by-step instructions for installing the ICA Win32 Clients,
see the ICA Win32 Clients Administrator's Guide (ICA_Win32_Guide.pdf),
located in the ICAClientDoc folder of your Components CD.
Note: To install the ICA Client software using the Windows Installer
(.Msi) package, the Windows Installer Service must be installed on the
client device. This service is present by default on Windows 2000
systems. To install ICA Clients on client devices running earlier
versions of the Windows operating system, you must use the
self-extracting executable or install the Windows Installer 2.0
Redistributable for Windows, available for download at
http://www.microsoft.com/.
Limitations and Known Issues
============================
1. Multiple monitor support limitations
When running an ICA session on a computer with multiple monitors
running at different color depths, moving the ICA session window
between monitors corrupts the display.
Workaround: Set all monitors to the same color depth.
When running an application in seamless mode on a computer with
multiple monitors, the application may open a desktop window that
covers the entire screen area, across displays.
Workaround:
- The numbered displays must appear in ascending order (1-2-3)
- The left-most display must be marked as the primary display
- The extreme upper-left pixel of the virtual desktop must not be
covered by any other display.
[#29858]
2. Netscape
If you install a Web browser after installing the ICA Win32 Web
Client, you must reinstall the ICA Win32 Web Client if you are
using the Netscape Plugin. The Netscape Plugin must be registered
with the browser so that when you select an ICA file in an HTML
file, the browser knows what to run to invoke the ICA file.
If you uninstall the ICA Win32 Client shortly after using Netscape

to connect to a published application using NFuse, the Npican.dll

file is not removed from the Netscape Plugin folder. As a result,
the NFuse Login page does not display the ICA Client download links.
Workaround: Manually remove the Npican.dll file, or reinstall the
ICA Win32 Client using a method other than the NFuse Login page.
If you are using Netscape 6.x, and if you download and install the
Netscape Plugin Client (Wfplug32.exe) from an ICA file or from an
HTML page, the Npican.dll file installs into the wrong folder of
your client device. As a result, Netscape does not recognize that
the plugin was installed.
Workaround: Locate and copy the file Npican.dll to the following
folder:
Program Files\Netscape\Netscape6\Plugins.
3. Pass-through authentication with higher than Basic encryption
level in mixed version MetaFrame server/ICA Client environments
If you want to use pass-through authentication along with an
encryption level higher than Basic,
-andIf you are connecting to a server running MetaFrame XP, Version
1.0, Feature Release 2, Service Pack 2, or higher using an
ICA Client earlier than Version 7.0 (this version)
-orIf you are connecting to a server running a version earlier than
MetaFrame XP, Version 1.0, Feature Release 2, Service Pack 2,
using an ICA Client Version 7.0 (this version)
You must add the following line to the Appsrv.ini file:
AutoLogonAllowed=on
4. You cannot connect to a MetaFrame server using the IPX, SPX, or
NetBIOS protocols after installing Version 7.0 of the ICA Win32
Client (this version) in the following circumstances:
* If you install Version 7.0 of the ICA Win32 Client on a client
device and then install an earlier version of the ICA Win32
Client. Attempting to connect using the earlier version of the
ICA Win32 Client fails.
* If you install and then uninstall Version 7.0 of the ICA Win32
Client and then install an earlier version of the ICA Win32
Client.
5. To use Version 7.0 (this version) of the ICA Win32 Client with
MetaFrame for Windows Version 1.8 on Windows 2000 servers, the
server must be running Service Pack 2 for MetaFrame 1.8. If you
use Version 7.0 of the ICA Win32 Client to connect to a MetaFrame
1.8 server that is at Service Pack level 1, the connection will be
dropped the next time you attempt to connect.
6. If the color depth of your local desktop is set to High or True

Color, running a 256-color ICA Client session causes a bold border

around modified cells in Microsoft Excel 97 and Excel 2000.
Workaround: Adjust the color depth of your local desktop to match
that of the ICA Client.
7. You can reduce a Win32 Client session window to a minimum of 64
pixels in width. However, the Windows operating system may enforce
a greater limit based on the prevailing desktop scheme, which
overrides the ICA Win32 Client scaling limit.
8. On ICA Win32 client devices running Windows 9x or Windows Me, Off
Screen Surface (OSS) functionality is disabled by default.
OSS functionality directs the ICA Client to draw screen updates
to an in-memory bitmap rather than to the screen. Because this
functionality improves bandwidth efficiency, you may want to enable
it if users connect to MetaFrame servers across a WAN.
To enable OSS functionality before you deploy the ICA Win32 Client
software to users:
A. Extract the ICA Win32 Client files from the ICA Win32 Client
executable (.Exe).
B. Open Module.ini in any text editor.
C. Change the line EnableOssOnWin9xMe= in the [Thinwire3.0]
section to
EnableOssOnWin9xMe=on.
D. Save and close Module.ini.
E. Repackage the ICA Win32 Client files for distribution to your
users.
9. If you have both the ICA Win32 Program Neighborhood Agent and the
ICA Win32 Program Neighborhood Client on the same client device,
and if you uninstall the ICA Win32 Program Neighborhood Agent, file
type association for .ica-type files is lost. As a result, the ICA
Client is unable to connect to MetaFrame servers.
Workaround: To restore file type association for .ica-type files,
type the following command at a command prompt:
wfica32.exe /setup
10. If you want to use Citrix Extranet with the Program Neighborhood
Agent on a Windows 95, Windows 98, or Windows Me system, you must
use Version 2.5 of both the Extranet Client and the Extranet Server.
Earlier versions of Citrix Extranet installed on a client device
running Windows 9x can cause the Program Neighborhood Agent to
hang, even if you are not using Extranet when you are running the
Program Neighborhood Agent.
11. When you double-click a file whose filename contains spaces, the
extended parameter passing feature may open the associated
published application, but not the file itself.

Workaround: Open the file by browsing to it from within the

application's File > Open... dialog.
12. For users of NFuse Version 1.5: If you have populated the Client
Update Database with the ICA Clients from the Components CD
included in your MetaFrame XP media pack, users may receive
unnecessary update notifications. The client detection code of
an NFuse 1.5 Web site (either a site produced by the NFuse 1.5 Web
Site wizard or an example Web site provided by Citrix) may
incorrectly notify the user that the client device does not have
the latest ICA Client installed, and prompt the user to update the
ICA Client.
Workaround: Select the Do not show this window at login option in
the update message box to prevent the message from appearing again.
The client detection process was corrected with the release of
NFuse Version 1.51. You can also download NFuse Classic from the
Citrix Web site at
http://www.citrix.com/download/.
13. Roaming User Reconnect does not work in multiple-server MetaFrame
XPs deployments.
14. If you cannot use the Secure Gateway or otherwise connect to a
MetaFrame server through a Secure proxy using SSL, particularly
Microsoft ISA Server 2000, you will most likely need to change
your proxy server or firewall configurations to allow non-SSL
tunneled connections to the targeted MetaFrame server(s) and
port(s). Consult your proxy server or firewall documentation for
details.
15. "Seamless within seamless" (that is, seamless windows via passthrough mode) is not a supported configuration for the ICA Win32
Clients. Because the ICA Win32 Clients support seamless windows
natively, it is not necessary to use pass-through mode. Pass-through
mode is intended to facilitate seamless windows for ICA Clients
that do not support seamless windows natively, and should only be
used from a fixed-size window session on the client device.
16. On Windows 98 systems using Microsoft Internet Explorer, server-toclient content redirection requires Internet Explorer Version 5.5
with Service Pack 2.
17. If you are logged on using pass-through authentication (with
credentials set A), and then want to log on with a different set
of credentials (set B), you must log off the ICA Client and log
on again for the client to pass credentials set B to the server.
18. The Program Neighborhood and Program Neighborhood Agent
ICA Clients (as shipped with Feature Release 2) installed using
an MSI package cannot be upgraded to the client shipped with
Feature Release 3 using the .EXE installation package.
[#53542, 53228]
19. Netscape 7 requires a reboot of the client device to recognize
that the ICA Win32 Web Client is installed. The client device
can connect to a MetaFrame server and launch published
applications, but an error message may appear noting that the

client software is not installed. Rebooting the client device

will remove this message.
[#55173]
20. To upgrade a client device Windows NT 3.51 from Program
Neighborhood version 6.20.986.13.2 to Program Neighborhood
version 7.0, you must copy the file
msvcrt20.dll
to
%system root%\system32
[#57031]
21. Users without administrative rights on client devices running
Windows 2000 Professional or Windows XP cannot change the
name of the client device.
[#57446, 57024]
22. Certificate revocation checking is supported only on client
devices running Windows XP and Windows 2000 operating systems.
[#59459]
23. If the Program Neighborhood Agent uses UPN credentials for SSON
(pass-through authentication), the Web Interface must be
configured to use NT authentication. If the Web Interface is set
to force UPN authentication (that is, the ForceLoginDomain
parameter present but with empty value), Program Neighborhood Agent
users will not be able to log on using UPN credentials for SSON.
[#62657]
24. An error message page may be displayed when accessing the
Web Interface Admin tool and the Program Neighborhood Agent Admin
tool from a system that has been upgraded to Windows Server 2003
from Windows 2000. To access the Admin tool on the Windows
Server 2003 platform:
1. Open the Internet Information Services Snap-in tool.
2. Navigate to the Default Web Site/Citrix/MetaFrameXP/WIAdmin
directory.
3. Right-click on WIAdmin and choose Properties.
4. In the Directory tab, change Application Protection from
High to Low and click Apply.
5. Close any existing Internet Explorer browser windows.
Open a new browser window and enter the Admin tool URL.
Once this procedure is complete, the Application Protection
can be switched back to High.
25. If you install the Win32 ICA Client using an MSI package and
do not select "Use machine name as client name" during the
installation process, the installation will need to be repaired
if an end user later selects "Enable Dynamic Client Name" in
Program Neighborhood.
To allow repair of the installation, the MSI package must be
available to the client machine and user from its original
installation location.
[#63146]

26. Dynamic Client Name

Each time a user changes the client or client device name,
they must close and re-start the Win32 ICA Client for the
name change to take effect.
[#63158]

CONTACT INFORMATION
===================
Citrix Systems, Inc.
851 West Cypress Creek Road
Fort Lauderdale, Florida 33309 USA
954-267-3000
http://www.citrix.com