[THIN] Re: RE New Ica Client 6.31.051

  • From: "Daniel Barichello" <Daniel.Barichello@xxxxxxxxxxxxxxxxxxxxx>
  • To: thin@xxxxxxxxxxxxx
  • Date: Fri, 18 Oct 2002 11:00:25 +1000


Here you go,.

Citrix Systems, Inc.


Read Me
=3D=3D=3D=3D=3D=3D=3D
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, wf=
ica.cab)
            ICA Win32 Web Client (Ica32t.exe, wficat.cab)

Version:    6.31

Replaces:   All versions prior to September 2002

Date:       September 2002

Language:   English (US)

Copyright 2001-2002, Citrix Systems, Inc. All rights reserved.
All other trademarks and registered trademarks are the property of
their owners.


Introduction
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
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
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D
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
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D
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
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D
ICA Clients are the client-side software components of the MetaFrame
Application Server product family. Combining the ease of use you expect
with the security features you require, ICA Clients offer point-and-click,
secure access to applications, content, and entire computer desktops
published on MetaFrame 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 NFuse Classic, 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 and
in real time.


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 NFuse Classic 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 NFuse
Classic, 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
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D
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
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
 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.

 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,

    -and-

    If you are connecting to a server running MetaFrame XP, Version
    1.0, Feature Release 2, Service Pack 2, using an ICA Client earlier
    than Version 6.31 (this version)

    -or-

    If 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 6.31 (this version)

    You must add the following line to the Appsrv.ini file:

             AutoLogonAllowed=3Don

 4. You cannot connect to a MetaFrame server using the IPX, SPX, or
    NetBIOS protocols after installing Version 6.31 of the ICA Win32
    Client (this version) in the following circumstances:

    *  If you install Version 6.31 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 6.31 of the ICA Win32
       Client and then install an earlier version of the ICA Win32
       Client.

 5. To use Version 6.31 (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 6.31 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=3D in the [Thinwire3.0]
        section to

               EnableOssOnWin9xMe=3Don.

    D. Save and close Module.ini.

    E. Repackage the ICA Win32 Client files for distribution to your
       users.

 9. On low-end client devices or systems running multiple, simultaneous
    ICA connections, CPU utilization may run higher than expected when
    there is no activity between the client and the server.
    Workaround: Change the poll time-out value on the client device.
    The default poll time-out value is 1 millisecond. To enter a greater
    poll time-out value:

    A.  Open the individual's user-level Appsrv.ini file (default folder:
        %User Profile%\Application Data\ICAClient) in a text editor.

    B.  Add the following parameter to the [WFCLIENT] section:

               IdlePollDelay=3Dn

        where n is the desired polling interval, in milliseconds.

    C.  Save and close the Appsrv.ini file.

10. 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

11. 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.

12. 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.

13. 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/.

14. Roaming User Reconnect does not work in multiple-server MetaFrame
    XPs deployments.

15. If you cannot use Citrix 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.

16. "Seamless within seamless" (that is, seamless windows via pass-
    through 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.

17. On Windows 98 systems using Microsoft Internet Explorer, server-to-
    client content redirection requires Internet Explorer Version 5.5
    with Service Pack 2.

18. 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.


Issues Resolved with this Client
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D

 1. This item pertains only to the English ICA Win32 Clients.

    If a user opened a new window or menu item repeatedly, the
    operating system's Graphical Device Interface (GDI) resources
    were reduced, and eventually, when GDI Resources were depleted,
    the operating system became unstable.

    GDI resource areas keep track of items that the operating system
    uses to draw graphics: pens, brushes, fonts, palettes, and so on.
    Each time a window is opened, it receives an allocation of GDI
    resources. When the window is closed, these GDI resources are
    released, freeing memory in the GDI resource area for other
    applications and windows.

    The ICA Client did not properly track the GDI brush resource
    and lost memory each time a new window was opened.

    The client now properly tracks the GDI brush resource, releasing
    its allocated memory when windows are closed.
    [#248109]

 2. This item pertains only to the English ICA Win32 Clients.

    In seamless mode, sections of an application window disappeared
    from view if you made the window size larger than the desktop
    size.

    By default, an ICA Client window for a published application is
    limited to the height and width of the client device desktop.

    The client now uses window sizing information from the seamless
    host engine to extend the allowable size of a seamless-mode
    window if the default limit is exceeded. The result is that a
    seamless application window is displayed correctly, even if you
    make it larger than the size of the desktop.
    [#252058]

 3. This item pertains only to the English ICA Win32 Clients.

    On an ICA Client running without the Windows Explorer desktop,
    sessions froze when users moved minimized icons of seamless
    application windows around the desktop.

    When a seamless window runs without the Windows Explorer desktop,
    minimized application windows appear on the desktop area instead
    of the Windows taskbar. The ICA Client did not previously provide
    functionality for moving these minimized windows around the desktop.

    The solution updates the server with the new position of a
    minimized window if the Windows Explorer desktop isn't being
    used. Users can now move these minimized windows.
    [#251010]

 4. This item pertains only to the English ICA Win32 Clients.

    Seamless applications launched with pass-through authentication
    disappeared if minimized.

    With this client, if the Windows Explorer desktop exists when
    a seamless session is created, the MetaFrame server is updated
    with the new position of any minimized windows. Seamless sessions
    no longer freeze if users move the minimized window icons.
    Minimized applications in seamless mode no longer disappear.
    [#257426]

 5. This item pertains only to the English ICA Win32 Clients.

    On a computer with an existing ICA session to a MetaFrame server
    farm, if a published application was launched connecting to
    the same server farm with a user principle name (for example,
    user1@xxxxxxxxxx), session sharing was allowed and the application
    launched in the existing ICA session, regardless of the user name
    used to start the existing session.

    A function that checked if session sharing was allowed improperly
    ignored the user names if the connecting user name contained the
    at (@) character.

    The portion of a user principle name to the left of the at
    (@) character is now compared with the user name of all current
    sessions. Session sharing is allowed only if the names match.

    When launching a published application using a user principle
    name, session sharing occurs only if the portion of the user
    principle name to the left of the "@" symbol is identical to the
    user name used to start an existing session on the same MetaFrame
    server farm. Otherwise, the application launches in a separate
    session.
    [#249702]

 6. This item pertains only to the English ICA Win32 Clients.

    When using key combinations with the ALT key to display a menu
    (such as ALT+F to display the File menu), the menu appeared
    and then quickly disappeared.

    If a window received keyboard focus, the client then sent
    the window a pressed-key event for any ALT, SHIFT, and CTRL
    key that was pressed. For example, when the user pressed ALT+F,
    the File menu window appeared and received keyboard focus. The
    client then sent another pressed-key event for the ALT key
    (because the user was still pressing the ALT key), which closed
    the menu.

    Now, if a window receives keyboard focus, the server's current
    key state is compared with the actual state of the ALT, CTRL, and
    SHIFT keys. Pressed-key or released-key events are sent to the
    server only if the server's state differs from the actual state of
    the keyboard. Menus do not flicker when you use a hotkey
    combination.
    [#253026]

 7. This item pertains only to the English ICA Win32 Clients.

    While installing the ICA Win32 Web Client self-extracting executable
    (Ica32t.exe), users received a "File Copy Failed" error message
    for the Npican.dll file.

    The error was generated because the Netscape plug-in directory to
    which the Npican.dll file was being copied was physically removed
    but remained listed in the registry. The ICA Win32 Web Client
    installer checked the registry to determine if Netscape was
    installed, but did not ensure that the Netscape plug-in directory,
    indicated in the registry, actually existed before attempting to
    copy the Npican.dll file into the directory. Because the directory
    did not exist, the "File Copy Failed" error message was generated.

    Now the installer checks whether the Netscape plug-in directory
    indicated in the registry actually exists on the hard drive. If
    the directory doesn't exist, the Npican.dll file is not needed and
    not copied. The "File Copy Failed" error does not occur.
    [#246457]

 8. This item pertains only to the English ICA Win32 Clients.

    Users experienced irregular synchronization of the NUM LOCK and
    CAPS LOCK keys between the ICA Win32 Client and the MetaFrame
    server. If on the client both NUM LOCK and CAPS LOCK were turned
    on when a new ICA Session was opened, pressing one of the keys
    turned both of them off. Users also found that pressing a letter
    key turned off NUM LOCK on the client, but not on the server.

    This issue was fixed by verifying the NUM LOCK and CAPS LOCK states
    between the client and server. After installing the new ICA Win32
    Client, NUM LOCK and CAPS LOCK remain in synchronization on the
    client and server.
    [#254066, 252274]

 9. If an ICA Client's DNS server was configured to use round-robin
    DNS to map to a set of MetaFrame XP servers, the client did not
    cycle through the list of resolved addresses. The client attempted
    to connect only to the first IP address returned by DNS. If the
    server at the first IP address was unavailable, the client did not
    try the other IP addresses in the set, and failed to connect.

    The solution ensures that the client connects, if there is at
    least one MetaFrame server running in the round-robin DNS set.
    [#215235]

10. The ICA Win32 Client could not connect to published applications
    if you changed the TCP/IP port number on the server and then
    specified that same port number in the properties of a custom ICA
    connection on the client. The port number was changed on the server
    using the ICAPORT utility. On the client, the new port number
    setting was added in the Properties dialog box of the custom ICA
    connection as "ApplicationName:nnnn," where "ApplicationName"
    is the name of the application and "nnnn" is the port number.

    The Appsrv.ini file holds configuration and settings information
    for a custom ICA connection. The client incorrectly translated
    the new port information from the ICA connection Properties into
    the Initial Program setting of the Appsrv.ini file, including the
    colon and port number appended at the end of the program name.
    Instead of reading the Initial Program as "ApplicationName," the
    client included the port number and interpreted the Initial Program
    as "ApplicationName:nnnn." When the client tried to locate the
    application for the ICA connection, it incorrectly looked for
    "ApplicationName:nnnn" instead of "ApplicationName."

    This issue was resolved so that the client can connect to a
    published application after the application name and port number
    in the Properties of the custom ICA connection are changed.
    [#253234]

11. If a user uninstalled the ICA Win32 Web Client and then reinstalled
    it on the same system without first restarting the machine, the
    Web client could not be uninstalled after the computer was restarted.

    The uninstall program cannot remove files that are in use, so it
    marks them to be removed the next time the system starts. Because
    the user did not restart the computer before reinstalling the
    client, the installation program installed files over existing
    files that were marked for removal. The next time the computer was
    started, those files were removed, and the uninstall program could
    not run. This solution renames files before they are marked for
    removal. When the system starts, the renamed files are removed
    instead of the newly installed files.

    Another installation-related issue occurred when a user without
    administrative privileges installed the ICA Win32 Web Client on
    a Windows NT workstation. The ICA Win32 Web Client did not appear
    in the Add/Remove Programs panel, and as a result, the user
    could not uninstall the client.

    The user did not have permission to access the registry. Now a
    user without administrative privilege can access the registry
    on a Windows NT workstation in such a way that the client appears
    in the Add/Remove Programs panel. The user can then uninstall the
    client.
    [#256929, 256930]

12. This item pertains only to the English ICA Win32 Clients.

    When connecting to a MetaFrame server without going through a
    proxy server, connection time degraded from 3 seconds (using ICA
    Client Version 6.20.986) to 15 seconds (using ICA Client Version
    6.30.150).

    When you use a proxy server and a network name to identify a
    MetaFrame server, the IMA browser database is polled three times
    with a time-out of five seconds to resolve the IP address of the
    server before a reverse DNS lookup is attempted. In cases where
    a proxy server is not used and a real machine name is supplied
    for the server, the IMA database request fails and the reverse
    DNS lookup provides the IP address. However, the IMA database
    time-out value was changed from one second to five seconds for
    all IMA requests, so the portion of the time-out caused by the
    IMA database query increased from three seconds to 15 seconds
    when not using a proxy server.

    If the connection does not use a proxy server, the IMA time-out
    value is set to one second. The result is that the time required
    to connect to a MetaFrame server when not using a proxy server
    is significantly improved.
    [#250839, 257227]

13. ICA Win32 Client users who set the Mouse Properties of their
    Windows profile to use a left-handed mouse button configuration
    experienced right-handed mouse behavior in published applications
    after installing Version 6.30.1050 of the client. The same users
    had successfully experienced left-handed mouse button behavior
    when using client Version 6.20.986. This issue arose from a
    change that was made in client Version 6.30.1050.

    Mouse behavior is part of a user's profile of settings. With roaming
    profiles, a user's settings are available wherever the user logs on.
    The user settings that take effect when a user logs onto a MetaFrame
    server to access published applications depends upon whether users
    are allowed to use their roaming profile. Users may be assigned to
    anonymous profiles or user profiles local on the server. If users
    are assigned anonymous or server profiles, they typically have no
    way to access and change the user settings, including mouse
    behavior. The mouse behavior that shows up in published applications
    depends on the congruity or incongruity of the user profile settings
    between the server and client.

    An option has been added to the ICA Settings dialog box, which is
    accessed from the Tools menu of Program Neighborhood, to allow
    users to switch the behavior of the mouse buttons. Switching the
    mouse behavior now works regardless of whether or not a user's
    client and server profiles are the same.

    Users who want to switch the current right- or left-handed behavior
    of their mouse can select "Swap Mouse Buttons" in the ICA Settings
    dialog box.
    [#251727]

14. When attempting to open a custom ICA connection using the Program
    Neighborhood Client, users received the following error message:

    "The c:\WINNT\WFCLIENT.INI file is missing or corrupt (cannot find
     the [WFClient] section). The connection is aborted."

    This error message was generated because the custom ICA
    connection's executable file looked for the Wfclient.ini file in
    the Windows root directory before it checked the user's
    Application Data folder.

    There can be multiple instances of the Wfclient.ini file. If the
    custom ICA connection opens the wrong Wfclient.ini, the expected
    content is not found within the file and the error message is
    generated.  The Wfclient.ini file for a custom ICA connection is
    typically stored in the Application Data folder of the user's
    profile and not in the Windows root directory.

    The issue was solved by programming the custom ICA connection to
    first search for Wfclient.ini in the Application Data folder of
    the user's profile.
    [#257282]

15. On client devices running Windows 95 or 98, an error occurred
    while running the ICA Client Update Utility if a Web browser was
    left open during the auto-update. Users received an error message
    that a backup version of the Wfica.ocx file could not be saved.

    The error occurred because the open Web browser was using the
    Wfica.ocx file, and its file attributes did not allow it to be
    saved if in use. The problem was solved by allowing the file to
    be moved even if it is in use. If a previous backup file is found,
    it is first removed so that the Wfica.ocx can be renamed.

    The error message that reported this issue also contained an error.
    The message incorrectly reported the path where the auto-update
    attempted to save the Wfica.ocx file. The error message indicated
    that the path to the backup file version was "C:\Program Files\
    Citrix\C:\Program Files\Citrix\Backup\Wfica.ocx." The correct path
    is "C:\Program Files\Citrix\Backup\Wfica.ocx." The incorrect path
    was created by a function within the error message that added the
    file's directory, even if the file path was already an absolute
    path. This error in the message no longer appears, because the
    message function first checks whether or not the file path is
    already absolute before converting it to an absolute path.
    [#254960]

16. If the EventLog service was set to log events for an ICA file
    running remote desktop applications, the published applications
    ran correctly, but an event log was not created. If the
    applications were launched in seamless mode, the event log was
    created as expected.

    This ICA Client provides functionality to create an event log for
    an ICA file running in a remote desktop window.
    [#241350]

17. On an ICA Client for Windows 95 or 98, when a user pressed
    CTRL+ALT+DELETE to display the Close Program dialog box, and
    then pressed the ESC key to return keyboard focus to a published
    seamless application, the CTRL and ALT keys remained virtually
    "stuck" in the DOWN position. All subsequent key pressing acted as
    if the CTRL and ALT keys were still pressed.

    The ICA Client cannot detect a change in the state of the CTRL
    or ALT keys if the application does not have keyboard focus. The
    client synchronizes the key states each time the application gains
    keyboard focus. When the Close Program dialog box opens, Windows
    does not inform the seamless application that it has lost keyboard
    focus; nor does Windows inform the application that it has re-gained
    keyboard focus when the dialog box is closed. Therefore the seamless
    application could not detect the change in key state that occurred
    while the Close Program dialog box had focus.

    The client now monitors the state of the ALT key each time a key
    is pressed to re-synchronize the key states in case they

    changed unexpectedly.
    [#255238]

18. When the ICA Client File Security dialog box opened for an
    application being launched in seamless mode, users could still
    interact with other seamless windows running in the background,
    causing modality to be lost from the dialog box. If the dialog box
    was open and the user minimized another seamless application
    running in the background, the minimized application window could
    not afterward be maximized, used, or closed. The application
    running in the minimized window had to be reset by an administrator
    or closed in the Connection Center.

    A truly modal dialog box does not allow other windows to be used
    until the dialog box is closed.

    The issue was fixed by blocking messages from other windows while
    the File Security dialog box is open.
    [#257061]

19. After the Client Auto Update feature updates the Program
    Neighborhood Client for a user who is not an administrator and is
    using Windows NT with pass-through authentication, two Program
    Neighborhood shortcut icons appear on the user's desktop after
    restarting the client device.

    The update process creates two shortcuts, and the second shortcut
    overwrites the first one. If registry entries needed for the
    update process already existed from a previous installation or
    update, then a file permissions issue prevented the second shortcut
    overwriting the first one, and both shortcuts appeared on the
    desktop.

    The Client Auto Update feature now checks if the registry entries
    already exist. This check prevents the permissions issue and the
    update process creates only one shortcut icon.

    To ensure proper updating, add this ICA Win32 Client version to
    the client update database on your MetaFrame servers.
    [#257939]

20. If the Client Auto Update feature attempted to update a version
    of the ICA Client previous to Version 6.20.985, then Windows NT
    non-administrator users with pass-through authentication received
    errors when connecting to a MetaFrame server.

    An initial error message reported that pass-through authentication
    (Ssonsvr.exe) would be terminated. Another error message reported
    that a required .dll file (Pnipcn.dll) was not found.

    After restarting and running the Program Neighborhood Client, users
    repeatedly received a message stating, "The update of the Citrix
    ICA Client is complete. You must reboot your machine." Users had
    to manually delete the Reboot.lck file to stop the repeated
    request.

    If the Reboot.lck file is not deleted, the user repeatedly receives
    a message to reboot. The pass-through authentication feature in
    ICA Clients older than Version 6.20.985 does not provide permission
    to mark the Reboot.lck file for deletion. This ICA Client version
    renames the Reboot.lck file so that it can be deleted, allowing
    Client Auto Update to run successfully.
    [#257020]

21. This item pertains only to the English ICA Win32 Clients.

    An unintended string was added automatically to the URL string
    that a customer specified as the Citrix Nfuse Classic server,
    because a memory buffer was not being initialized. The buffer
    is now initialized to zero, and the extra string is not added
    to the NFuse server URL.
    [#253633]

22. This item pertains only to the English ICA Win32 Clients.

    Users could not interact by keyboard with the Program Neighborhood
    user interface dialog box. Users could interact successfully with
    a mouse. The problem occurred because the dialog box incorrectly
    disabled keyboard focus control.

    This client correctly sets the keyboard focus and allows users to
    use a keyboard to interact with the dialog box.
    [#250336]

23. This item pertains only to the English ICA Win32 Clients.

    NEC PC98 keyboards did not work in an Nfuse Classic session. The
    ICA Win32 Client was modified to support the NEC PC98 keyboard.
    [#253969]

24. This item pertains only to the English ICA Win32 Clients.

    Pass-through authentication for a desktop connection did not work,
    requiring users to enter a password for every application. This
    issue occurred because the pass-through mechanism attempted
    to open a required file, Wfapi.dll, with its full path name,
    WINNT\system32\wfapi.dll.

    If WINNT\system32\wfapi.dll cannot be loaded, the client loads
    the Wfapi.dll file from the directories that are specified by
    the PATH environment. This solution allows pass-through
    authentication to work.
    [#253770]

25. If you used the Program Neighborhood Agent with content redirection
    to invoke a version of Microsoft Outlook published on a MetaFrame
    server and clicked a mailto: link in a browser or in a word
    processor, a new Outlook email window did not open.

    Clicking a mailto: link caused Wfcrun32.exe to display a Remote
    Application Runtime message instead.

    A new Outlook email window now launches successfully as expected.
    [#43918]

26. Connecting to a published application from a Citrix Linux Client
    using the pass-through client on a MetaFrame server with 128-bit
    encryption generated an error. The error message reported that,
    "The application is enabled, but is not available. A higher
    encryption level is required, which the client does not support."
    The published application was set to a minimum requirement of
    128-bit encryption.

    The pass-through client Program Neighborhood detected the wrong
    encryption level for non-Windows clients by determining the level
    from the client's protocol driver encryption module name. This
    method does not work because the protocol driver encryption module
    name may not be the same across client platforms.

    The pass-through client Program Neighborhood now queries the
    terminal session for the client encryption level and allows you
    to successfully connect to a published application with 128-bit
    encryption.
    [#257708]

27. Some applications that enumerate printers responded slowly when
    run from an ICA session if the default printer on the client
    device was a network printer. Users who specified a Novell
    Distributed Print Services (NDPS) print queue experienced a
    slow print rate when printing reports. Users also reported that
    logging on to an ICA session was slow if the default printer on
    the client device was a network printer. This issue was caused by
    the ICA Client attempting to open a file with an incorrect file
    name. The file name inconsistency has been corrected, and users
    experience faster response or logon rates when using a network
    printer as the default printer.

    If a client device's Printer.ini file contained the setting,
    "RawDataOnly=3DYES," some printer settings on the client device were
    incorrrectly cleared in the printer settings of the auto-created
    printer for the ICA session. Because the print settings were cleared,
    some applications using the auto-created printer did not print
    properly. The issue was corrected by preserving other printer
    settings when the "RawDataOnly" option is set to "YES" in the
    client device's Printer.ini file.
    [#256297, 256477]

28. After auto-updating the Web Client, the Program Neighborhood
    shortcut icon showed up on a user's desktop even if the Program
    Neighborhood executable file (Pn.exe) didn't exist. The client now
    does not create the Program Neighborhood icon if the Pn.exe file
    doesn't exist.
    [#257923]

29. If Secure Sockets Layer (SSL) was used, the Program Neighborhood
    Agent used up to 97% of available CPU when running four or more
    applications.

    A timing window in the network transport code resulted in an
    invalid amount of available data being reported. Because the Program
    Neighborhood Agent code expected more data from the network
    transport layer than was actually available, it continued to issue
    reads attempting to retrieve additional data. This loop caused the
    high CPU utilization.

    The method used to determine when all available data is read
    was modified in the Program Neighborhood Agent. The modification
    eliminates continual reads attempting to retrieve additional data
    that does not exist. As a result, the high CPU utilization is
    eliminated.

    Program Neighborhood Agent now operates with normal CPU utilization
    when using SSL and starting four or more applications.
    [#254065]

30. Users experienced incorrect processing of mouse clicks after
    reconnecting to a disconnected session. In some applications users
    needed to click three times to achieve a double-click operation.

    The issue occurred in applications that modify the double-click
    time-out at runtime, because the double-click variable was not being
    restored after reconnecting. Double-click message processing has
    been moved to the server, and the mouse functions as expected.

    After installing this client, you should verify that the
    ClientMouseDoubleClickDetect option is set to "false" in the
    [WFCLIENT] section of either the Appsrv.ini file or the ICA file.
    [#257792, 258420]

31. If IntelliPoint mouse software was installed on a device running
    a Windows 2000 or previous operating system, and the "Hide pointer
    while typing" option was selected in the IntelliPoint settings,
    the mouse pointer disappeared while typing but did not reappear
    again when the mouse was moved.

    A hook procedure in the IntelliPoint software is now called and
    utilized to solve this issue. If the mouse pointer is set to
    disappear while typing, it now correctly reappears when you move
    the mouse.
    [#257924, 258517]

32. In a seamless session with only one window, if you minimized
    the window and then opened another window, the new window could
    lose keyboard focus. The client failed to place the newly-opened
    window in the foreground if there was no active seamless window
    in the session.

    With this client version, a window created from a minimized window
    receives keyboard focus.
    [#258566]

33. When using content redirection with the Program Neighborhood Agent,
    associated file types displayed the Program Neighborhood Agent
    icon rather than the icon for the associated program. For example,
    if .doc files were associated with Microsoft Word, then .doc files
    on the client displayed with a Program Neighborhood Agent icon
    rather than a Microsoft Word icon.

    The operating system uses the HKEY_CLASSES_ROOT\<file type>\DefaultIcon\
    registry key to select the icon to display for a file type. If
    there is no such key present, it then shows the icon of the
    application associated with it, which in this case happens to be
    the Program Neighborhood Agent.

    To resolve the problem, the Program Neighborhood Agent was
    modified to display icon files based on the data received from the
    server for each file type associated through content redirection,
    and to create the "DefaultIcon" registry key.

    After you install the new client version, file types associated
    through content redirection display the correct icons.
    [#257520]

34. Program Neighborhood user-specified credentials for custom
    connections were ignored when pass-through authentication and
    the "Use local credentials to log on" option were enabled. The
    user-specified credentials were overridden by the local user
    credentials.

    If "Use local credentials to log on" is enabled, the local
    credentials are used regardless of the request flag
    (UseLocalUserAndPassword) in the Appsrv.ini file.

    This issue was resolved with a mechanism that checks the state
    of UseLocalUserAndPassword to select between local user
    credentials or user-specified credentials.
    [#258081]

35. By default, the Program Neighborhood Agent client uses Internet
    Explorer's proxy settings for access to the Nfuse Classic Web
    server. However, if the client is directed to a proxy server that
    requires authentication or the Web server itself requests HTTP
    authentication for the Nfuse content, then the client cannot
    download configuration settings or enumerate applications.

    When receiving an HTTP status code indicating that authentication
    is required, the Program Neighborhood Agent did not take any
    action, resulting in the failure of the HTTP request.

    The Program Neighborhood Agent now handles both 401 and 407 HTTP
    status codes by collecting credentials from the user, adding
    the required authorization headers, and then retrying the HTTP
    request.

    When accessing an Nfuse Classic server through a proxy server that
    requires authentication, users are prompted to supply user
    credentials. If valid credentials are presented, the proxy server
    forwards the request to the Nfuse-enabled Web server,
    allowing the configurations settings to be read and applications
    to be enumerated.
    [#253374]

36. If proxy auto-detection was enabled and Netscape Version 6.2.1
    or higher was used as the default Web browser, the ICA Win32
    Client failed to use the proxy server settings set in Netscape.

    An ICA Client with proxy auto-detection enabled uses the proxy
    settings of the client device's default Web browser. To determine
    which is the default browser, the client checks the file-type
    association in the system registry. If the registry associates
    Netscape 4 or higher with HTML files, the client uses the
    Netscape proxy settings. Otherwise, the client uses the proxy
    settings managed by Internet Explorer.

    Recent versions of Netscape (6.2.1 and higher) changed how
    Netscape registers itself to handle HTML files. This change
    caused the ICA Client to fail to detect Netscape as the default
    browser, resulting in Internet Explorer proxy settings being
    applied rather than the expected Netscape proxy settings.

    The ICA Win32 Client uses an updated method to determine which
    browser is registered to handle HTML files. Windows clients
    with proxy auto-detection enabled and Netscape 6.2.1 or higher
    as the default browser see the Netscape proxy settings applied
    instead of Internet Explorer proxy settings.
    [#253374]

37. On client devices running Windows 95, 98, or ME, the ICA Client
    did not use the Netscape proxy server settings as expected when
    proxy auto-detection was enabled and Netscape 6.0 or higher was
    set as the user's default Web browser. The client could not find
    the Netscape proxy settings and used Internet Explorer settings
    instead. This issue was caused by a change in the directories that
    Netscape uses to hold user configuration files on Windows 9x
    platforms.

    The ICA Win32 Client now searches a wider range of possible
    directories to find the appropriate Netscape user configuration
    files, and correctly applies the Netscape proxy settings.
    [#253374]

38. Pass-through authentication of Windows NT credentials does not
    work on a Windows NT workstation that belongs to a workgroup and
    has the Novell client installed. The client device passes to the
    MetaFrame server authentication credentials that contain the
    device's workgroup name instead of the MetaFrame server's domain
    name.

    After installing this ICA Win32 Client Version 6.31, you can
    modify the registry to override the pass-through authentication
    credentials that include the workgroup name. The registry value
    you add is used as the domain name credential during pass-through
    authentication.

    WARNING! Using Registry Editor incorrectly can cause serious
    problems that might require you to reinstall your operating system.
    Use Registry Editor at your own risk. Make sure you back up the
    registry before you edit it.

    A. Open the Registry Editor and navigate to the following registry
       key:

       HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ICA Client\

    B. From the Edit menu, choose Add Value and enter the following
       information:

       Value Name: Domain
       Data Type: REG_SZ

    C. Click OK and, in the String text box, enter the server's domain
       name (for Windows NT domain authentication). If you want to set
       up authentication only for local users of the MetaFrame server
       and not for domain users, enter the server's name.

    After you modify the registry, you can use Windows NT credentials
    with pass-through authentication on client devices that are Windows
    NT workstations, belong to a workgroup, and have the Novell client
    installed.
    [#255441]

39. A silent-user installation was not entirely free of user
    interaction.

    When you install the ICA Win32 Web Client (Ica32t.exe), a message
    box requiring a user response appears at the end of the setup.
    The message box states, "Setup completed successfully. You may
    need to restart your Web browser to activate changes." You
    must click OK to clear the message.

    For an unattended user installation of the ICA Win32 Web client,
    you limit user interaction by configuring the Ctxsetup.ini file
    to suppress dialogs or messages that require a user response.
    Previously you could suppress all other message boxes during the
    installation, but not this message box at the end of the
    installation.

    You can now suppress the message with a setting that is included
    in the Ctxsetup.ini file. By default, the new "DisplayStatusMsg=3D1"
    setting causes the message to appear. To suppress the message,
    you can change the "DisplayStatusMsg" setting to "0." After you
    make this configuration change, it is possible to completely
    install the Web Client with no user interaction.
    [#256520]

40. When using the pass-through client, users were unable to log off
    the MetaFrame server if an ICA session was open. All pass-through
    ICA sessions had to be closed before users could log off the
    server.

    The pass-through client is an ICA Win32 Program Neighborhood
    Client published on a MetaFrame server. Connecting to the
    pass-through client allows users of different ICA Client
    platforms to access all published applications in the server farm
    regardless of platform.

    If you want to provide users with the ability to log off the
    server without first closing all pass-through ICA sessions, you
    can modify the registry of the MetaFrame server that publishes
    the pass-through client. When a user attempts to log off, this
    registry setting forces all open ICA sessions into a disconnected
    state and then allows the user to log off.

    WARNING! Using Registry Editor incorrectly can cause serious
    problems that might require you to reinstall your operating system.
    Use Registry Editor at your own risk. Make sure you back up the
    registry before you edit it.

    A. Open the Registry Editor and navigate to the following registry
       key:

       HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ICA Client\Pass Through

    B. From the Edit menu, choose Add Value and enter the following
       information:

       Value Name: QuickLogOff
       Data Type: REG_DWORD
       Data: 1
       Radix: Hex

    After you modify the registry, users can log off a MetaFrame
    server without first having to close all ICA sessions launched
    with the pass-through client.
    [#257433]

41. The Program Neighborhood Agent passes incorrect credentials if
    the Novell Client is installed on the client device and
    pass-through authentication is being used. Because of the
    incorrect credentials, users cannot obtain a list of applications
    from the Citrix NFuse Classic server.

    If a client device uses Novell Directory Services (NDS) and
    pass-through authentication, the Program Neighborhood Agent sends
    NDS credentials to the Citrix MetaFrame server. If NDS is not
    configured on the MetaFrame server, the authentication fails.

    A new logon method, NT_SSON, has been added to the Config.xml
    file and the Program Neighborhood Agent to use in determining
    the type of credentials to use. If NT_SSON is defined, the server
    and Program Neighborhood Agent can use Windows NT credentials
    for authentication.

    If you have Novell Client installed on the client device and want
    to use Windows NT credentials with pass-through authentication,
    you must modify the value of the XML tag <LogonMethod> in the
    Config.xml file to NT_SSON. The Config.xml file is in the
    Inetpub\wwwroot\Citrix\PNAgent directory. The default Logon Method
    is SSON.
    [#257888]

42. Application icons and shortcuts that were placed on the desktop
    or in the Start menu by the Program Neighborhood Agent on one
    client device were copied to the user's roaming profile and
    appeared on the desktop and in the Start menu when the user
    logged onto another client device where Program Neighborhood
    Agent was not installed. As a result, the application shortcuts
    did not work because Citrix client software was not installed on
    the client device.

    The shortcuts were placed into the user's profile by the Program
    Neighborhood Agent and were not being deleted when the user logged
    off from Windows. These shortcuts are now deleted from the desktop
    and the Start menu before Windows finishes logging off the user.

    To activate this feature in the Program Neighborhood Agent, the
    <Exit> value in the <FileCleanup> section of the Config.xml file
    on the Citrix NFuse Web server must be set to "true" and then the
    NFuse Web server must be rebooted.

    After you activate this feature, application icons and shortcuts
    are deleted from the desktop and the Start menu when a user logs
    off from Windows. When the user logs onto Windows, the icons and
    shortcuts reappear if the Program Neighborhood Agent starts up.
    [#41911]

43. When using a pass-through ICA Client, client printers were not
    always auto-created with the correct name, causing some
    applications to fail to print. The pass-through client retrieved
    its name from a registry setting that is writable by any other
    ICA Client running on the same system. The registry setting for
    a client name was, therefore, not always consistent.

    Pass-through ICA clients now query their terminal session
    rather than the registry for the Client Name, ensuring that each
    client uses a consistent name and that printer names are built
    correctly by the MetaFrame server during auto-creation.

    The registry setting "HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\
    ICA Client\PASS THROUGH\PASS THROUGH" must be set to 1 on the
    pass-through server.

    Printers for pass-through clients are now auto-created with
    correct names.
    [#257851]


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





Michael Earley <Michael.Earley@xxxxxxxxxxxxxx>@freelists.org on 18/10/2002
10:50:26 AM

Please respond to thin@xxxxxxxxxxxxx

Sent by:    thin-bounce@xxxxxxxxxxxxx


To:    "'thin@xxxxxxxxxxxxx'" <thin@xxxxxxxxxxxxx>
cc:

Subject:    [THIN] Re: RE New Ica Client 6.31.051



Could you do us a favour and post just the fixes?  Yes, I'm feeling lazy.
;-)

-----Original Message-----
From: Rowlandson, John [mailto:John.Rowlandson@xxxxxxxxxxxxx]
Sent: Friday, 18 October 2002 10:51 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: RE New Ica Client 6.31.051





There are some good fixes in there, I am seeing quite a few of the
issues but have either lived with them and fobbed users off.



-----Original Message-----
From: Dirk Blose [mailto:Dirk.Blose@xxxxxxxxxx]=3D20
Sent: Friday, October 18, 2002 3:09 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: RE New Ica Client 6.31.051




It's in the Readme file all the way at the bottom. I just got done
looking =3D3D through them.

Dirk Blose, MCSE, CCA
Lead Technical Analyst
(919) 765-4791
dirk.blose@xxxxxxxxxx

>>> emann@xxxxxxxxxxxx 10/17/02 10:16AM >>>

Does Citrix ever released an actual file that explains what was fixed?
=3D3D The readme just lists known issues it seems.

-----Original Message-----
From: Jim Kenzig [mailto:jimkenz@xxxxxxxxxxxxxx]=3D3D20
Sent: Thursday, October 17, 2002 10:10 AM
To: thin@xxxxxxxxxxxxx=3D3D20
Subject: [THIN] RE New Ica Client 6.31.051



Gray version is now available  at http://thethin.net/pn631051.zip   All
"gray" versions of previous  PN.exe are also on
http://thethin.net/downloads.cfm=3D3D20

Enjoy,
JK
***********************************************
This weeks sponsor Emergent Online
http://www.go-eol.com=3D3D20
Visit Jim Kenzig of thethin.net at the
Emergent Online Booth #221 at Citrix Iforum 2002!
Register now at: http://www.citrixiforum.com/registerNow.html=3D3D20
***********************************************=3D3D20
For Archives, to Unsubscribe, Subscribe or=3D3D20
set Digest or Vacation mode use the below link.

http://thethin.net/citrixlist.cfm=3D3D20
***********************************************
This weeks sponsor Emergent Online
http://www.go-eol.com=3D3D20
Visit Jim Kenzig of thethin.net at the
Emergent Online Booth #221 at Citrix Iforum 2002!
Register now at: http://www.citrixiforum.com/registerNow.html=3D3D20
***********************************************=3D3D20
For Archives, to Unsubscribe, Subscribe or=3D3D20
set Digest or Vacation mode use the below link.

http://thethin.net/citrixlist.cfm=3D3D20


***********************************************
This weeks sponsor Emergent Online
http://www.go-eol.com
Visit Jim Kenzig of thethin.net at the
Emergent Online Booth #221 at Citrix Iforum 2002!
Register now at:
http://www.citrixiforum.com/registerNow.html
***********************************************=3D20
For Archives, to Unsubscribe, Subscribe or=3D20
set Digest or Vacation mode use the below link.

http://thethin.net/citrixlist.cfm
***********************************************
This weeks sponsor Emergent Online
http://www.go-eol.com
Visit Jim Kenzig of thethin.net at the
Emergent Online Booth #221 at Citrix Iforum 2002!
Register now at:
http://www.citrixiforum.com/registerNow.html
***********************************************
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link.

http://thethin.net/citrixlist.cfm
***********************************************
This weeks sponsor Emergent Online
http://www.go-eol.com
Visit Jim Kenzig of thethin.net at the
Emergent Online Booth #221 at Citrix Iforum 2002!
Register now at:
http://www.citrixiforum.com/registerNow.html
***********************************************
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link.

http://thethin.net/citrixlist.cfm






**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom
they are addressed.=20

If you have received this email in error, you are prohibited from
reading, copying, distributing and using the information. Please
contact the sender immediately by return email and destroy=20
the original message.

You should scan this message and any attachments for viruses.
Under no circumstances do we accept liability for any loss or
damage which may result from your receipt of this message or
any attachments.
**********************************************************************

***********************************************
This weeks sponsor Emergent Online
http://www.go-eol.com
Visit Jim Kenzig of thethin.net at the
Emergent Online Booth #221 at Citrix Iforum 2002!
Register now at:
http://www.citrixiforum.com/registerNow.html
*********************************************** 
For Archives, to Unsubscribe, Subscribe or 
set Digest or Vacation mode use the below link.

http://thethin.net/citrixlist.cfm

Other related posts: