[THIN] Re: RE New Ica Client 6.31.051

  • From: "Rowlandson, John" <John.Rowlandson@xxxxxxxxxxxxx>
  • To: <thin@xxxxxxxxxxxxx>
  • Date: Fri, 18 Oct 2002 10:56:24 +1000

Issues Resolved with this Client
 1. This item pertains only to the English ICA Win32 Clients.
    If a user opened a new window or menu item repeatedly, the=20
    operating system's Graphical Device Interface (GDI) resources=20
    were reduced, and eventually, when GDI Resources were depleted,=20
    the operating system became unstable.=20
    GDI resource areas keep track of items that the operating system=20
    uses to draw graphics: pens, brushes, fonts, palettes, and so on.=20
    Each time a window is opened, it receives an allocation of GDI=20
    resources. When the window is closed, these GDI resources are=20
    released, freeing memory in the GDI resource area for other=20
    applications and windows. =20
    The ICA Client did not properly track the GDI brush resource=20
    and lost memory each time a new window was opened.=20
    The client now properly tracks the GDI brush resource, releasing=20
    its allocated memory when windows are closed.=20
 2. This item pertains only to the English ICA Win32 Clients.
    In seamless mode, sections of an application window disappeared=20
    from view if you made the window size larger than the desktop=20
    By default, an ICA Client window for a published application is=20
    limited to the height and width of the client device desktop.  =20
    The client now uses window sizing information from the seamless=20
    host engine to extend the allowable size of a seamless-mode=20
    window if the default limit is exceeded. The result is that a=20
    seamless application window is displayed correctly, even if you=20
    make it larger than the size of the desktop.=20
 3. This item pertains only to the English ICA Win32 Clients.
    On an ICA Client running without the Windows Explorer desktop,=20
    sessions froze when users moved minimized icons of seamless=20
    application windows around the desktop.=20
    When a seamless window runs without the Windows Explorer desktop,=20
    minimized application windows appear on the desktop area instead=20
    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=20
    minimized window if the Windows Explorer desktop isn't being=20
    used. Users can now move these minimized windows.=20
 4. This item pertains only to the English ICA Win32 Clients.
    Seamless applications launched with pass-through authentication=20
    disappeared if minimized.=20
    With this client, if the Windows Explorer desktop exists when=20
    a seamless session is created, the MetaFrame server is updated=20
    with the new position of any minimized windows. Seamless sessions=20
    no longer freeze if users move the minimized window icons.=20
    Minimized applications in seamless mode no longer disappear.=20
 5. This item pertains only to the English ICA Win32 Clients.
    On a computer with an existing ICA session to a MetaFrame server=20
    farm, if a published application was launched connecting to=20
    the same server farm with a user principle name (for example,=20
    user1@xxxxxxxxxx), session sharing was allowed and the application=20
    launched in the existing ICA session, regardless of the user name=20
    used to start the existing session.=20
    A function that checked if session sharing was allowed improperly=20
    ignored the user names if the connecting user name contained the=20
    at (@) character.
    The portion of a user principle name to the left of the at=20
    (@) character is now compared with the user name of all current=20
    sessions. Session sharing is allowed only if the names match.
    When launching a published application using a user principle=20
    name, session sharing occurs only if the portion of the user=20
    principle name to the left of the "@" symbol is identical to the=20
    user name used to start an existing session on the same MetaFrame=20
    server farm. Otherwise, the application launches in a separate=20
 6. This item pertains only to the English ICA Win32 Clients.
    When using key combinations with the ALT key to display a menu=20
    (such as ALT+F to display the File menu), the menu appeared=20
    and then quickly disappeared.=20
    If a window received keyboard focus, the client then sent=20
    the window a pressed-key event for any ALT, SHIFT, and CTRL=20
    key that was pressed. For example, when the user pressed ALT+F,=20
    the File menu window appeared and received keyboard focus. The=20
    client then sent another pressed-key event for the ALT key=20
    (because the user was still pressing the ALT key), which closed=20
    the menu.=20
    Now, if a window receives keyboard focus, the server's current=20
    key state is compared with the actual state of the ALT, CTRL, and=20
    SHIFT keys. Pressed-key or released-key events are sent to the=20
    server only if the server's state differs from the actual state of=20
    the keyboard. Menus do not flicker when you use a hotkey=20
 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=20
    for the Npican.dll file.=20
    The error was generated because the Netscape plug-in directory to=20
    which the Npican.dll file was being copied was physically removed=20
    but remained listed in the registry. The ICA Win32 Web Client=20
    installer checked the registry to determine if Netscape was=20
    installed, but did not ensure that the Netscape plug-in directory,=20
    indicated in the registry, actually existed before attempting to=20
    copy the Npican.dll file into the directory. Because the directory=20
    did not exist, the "File Copy Failed" error message was generated.=20
    Now the installer checks whether the Netscape plug-in directory=20
    indicated in the registry actually exists on the hard drive. If=20
    the directory doesn't exist, the Npican.dll file is not needed and=20
    not copied. The "File Copy Failed" error does not occur.=20
 8. This item pertains only to the English ICA Win32 Clients.
    Users experienced irregular synchronization of the NUM LOCK and=20
    CAPS LOCK keys between the ICA Win32 Client and the MetaFrame=20
    server. If on the client both NUM LOCK and CAPS LOCK were turned=20
    on when a new ICA Session was opened, pressing one of the keys=20
    turned both of them off. Users also found that pressing a letter=20
    key turned off NUM LOCK on the client, but not on the server.=20
    This issue was fixed by verifying the NUM LOCK and CAPS LOCK states=20
    between the client and server. After installing the new ICA Win32=20
    Client, NUM LOCK and CAPS LOCK remain in synchronization on the=20
    client and server.=20
    [#254066, 252274]=20
 9. If an ICA Client's DNS server was configured to use round-robin=20
    DNS to map to a set of MetaFrame XP servers, the client did not=20
    cycle through the list of resolved addresses. The client attempted=20
    to connect only to the first IP address returned by DNS. If the=20
    server at the first IP address was unavailable, the client did not=20
    try the other IP addresses in the set, and failed to connect.=20
    The solution ensures that the client connects, if there is at
    least one MetaFrame server running in the round-robin DNS set.  =20
    [#215235] =20
10. The ICA Win32 Client could not connect to published applications=20
    if you changed the TCP/IP port number on the server and then=20
    specified that same port number in the properties of a custom ICA=20
    connection on the client. The port number was changed on the server=20
    using the ICAPORT utility. On the client, the new port number=20
    setting was added in the Properties dialog box of the custom ICA=20
    connection as "ApplicationName:nnnn," where "ApplicationName"=20
    is the name of the application and "nnnn" is the port number.=20
    The Appsrv.ini file holds configuration and settings information=20
    for a custom ICA connection. The client incorrectly translated=20
    the new port information from the ICA connection Properties into=20
    the Initial Program setting of the Appsrv.ini file, including the=20
    colon and port number appended at the end of the program name.=20
    Instead of reading the Initial Program as "ApplicationName," the=20
    client included the port number and interpreted the Initial Program=20
    as "ApplicationName:nnnn." When the client tried to locate the=20
    application for the ICA connection, it incorrectly looked for=20
    "ApplicationName:nnnn" instead of "ApplicationName."=20
    This issue was resolved so that the client can connect to a=20
    published application after the application name and port number=20
    in the Properties of the custom ICA connection are changed.=20
11. If a user uninstalled the ICA Win32 Web Client and then reinstalled=20
    it on the same system without first restarting the machine, the=20
    Web client could not be uninstalled after the computer was
    The uninstall program cannot remove files that are in use, so it=20
    marks them to be removed the next time the system starts. Because=20
    the user did not restart the computer before reinstalling the=20
    client, the installation program installed files over existing=20
    files that were marked for removal. The next time the computer was=20
    started, those files were removed, and the uninstall program could=20
    not run. This solution renames files before they are marked for=20
    removal. When the system starts, the renamed files are removed=20
    instead of the newly installed files.
    Another installation-related issue occurred when a user without=20
    administrative privileges installed the ICA Win32 Web Client on=20
    a Windows NT workstation. The ICA Win32 Web Client did not appear
    in the Add/Remove Programs panel, and as a result, the user=20
    could not uninstall the client.=20
    The user did not have permission to access the registry. Now a=20
    user without administrative privilege can access the registry=20
    on a Windows NT workstation in such a way that the client appears=20
    in the Add/Remove Programs panel. The user can then uninstall the=20
    [#256929, 256930]=20
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=20
    Client Version 6.20.986) to 15 seconds (using ICA Client Version=20
    When you use a proxy server and a network name to identify a=20
    MetaFrame server, the IMA browser database is polled three times=20
    with a time-out of five seconds to resolve the IP address of the=20
    server before a reverse DNS lookup is attempted. In cases where
    a proxy server is not used and a real machine name is supplied=20
    for the server, the IMA database request fails and the reverse=20
    DNS lookup provides the IP address. However, the IMA database=20
    time-out value was changed from one second to five seconds for=20
    all IMA requests, so the portion of the time-out caused by the=20
    IMA database query increased from three seconds to 15 seconds=20
    when not using a proxy server.
    If the connection does not use a proxy server, the IMA time-out=20
    value is set to one second. The result is that the time required=20
    to connect to a MetaFrame server when not using a proxy server=20
    is significantly improved.
    [#250839, 257227]=20
13. ICA Win32 Client users who set the Mouse Properties of their=20
    Windows profile to use a left-handed mouse button configuration=20
    experienced right-handed mouse behavior in published applications=20
    after installing Version 6.30.1050 of the client. The same users=20
    had successfully experienced left-handed mouse button behavior=20
    when using client Version 6.20.986. This issue arose from a=20
    change that was made in client Version 6.30.1050.=20
    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=20
    are allowed to use their roaming profile. Users may be assigned to=20
    anonymous profiles or user profiles local on the server. If users=20
    are assigned anonymous or server profiles, they typically have no=20
    way to access and change the user settings, including mouse=20
    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.=20
    An option has been added to the ICA Settings dialog box, which is=20
    accessed from the Tools menu of Program Neighborhood, to allow=20
    users to switch the behavior of the mouse buttons. Switching the=20
    mouse behavior now works regardless of whether or not a user's=20
    client and server profiles are the same.=20
    Users who want to switch the current right- or left-handed behavior=20
    of their mouse can select "Swap Mouse Buttons" in the ICA Settings=20
    dialog box.
14. When attempting to open a custom ICA connection using the Program=20
    Neighborhood Client, users received the following error message:
    "The c:\WINNT\WFCLIENT.INI file is missing or corrupt (cannot find=20
     the [WFClient] section). The connection is aborted."
    This error message was generated because the custom ICA=20
    connection's executable file looked for the Wfclient.ini file in=20
    the Windows root directory before it checked the user's=20
    Application Data folder.=20
    There can be multiple instances of the Wfclient.ini file. If the=20
    custom ICA connection opens the wrong Wfclient.ini, the expected=20
    content is not found within the file and the error message is=20
    generated.  The Wfclient.ini file for a custom ICA connection is=20
    typically stored in the Application Data folder of the user's=20
    profile and not in the Windows root directory.=20
    The issue was solved by programming the custom ICA connection to=20
    first search for Wfclient.ini in the Application Data folder of=20
    the user's profile.=20
15. On client devices running Windows 95 or 98, an error occurred=20
    while running the ICA Client Update Utility if a Web browser was=20
    left open during the auto-update. Users received an error message=20
    that a backup version of the Wfica.ocx file could not be saved.=20
    The error occurred because the open Web browser was using the=20
    Wfica.ocx file, and its file attributes did not allow it to be=20
    saved if in use. The problem was solved by allowing the file to=20
    be moved even if it is in use. If a previous backup file is found,=20
    it is first removed so that the Wfica.ocx can be renamed.=20
    The error message that reported this issue also contained an error.=20
    The message incorrectly reported the path where the auto-update=20
    attempted to save the Wfica.ocx file. The error message indicated=20
    that the path to the backup file version was "C:\Program Files\
    Citrix\C:\Program Files\Citrix\Backup\Wfica.ocx." The correct path=20
    is "C:\Program Files\Citrix\Backup\Wfica.ocx." The incorrect path=20
    was created by a function within the error message that added the=20
    file's directory, even if the file path was already an absolute=20
    path. This error in the message no longer appears, because the=20
    message function first checks whether or not the file path is=20
    already absolute before converting it to an absolute path.=20
16. If the EventLog service was set to log events for an ICA file=20
    running remote desktop applications, the published applications=20
    ran correctly, but an event log was not created. If the=20
    applications were launched in seamless mode, the event log was=20
    created as expected.=20
    This ICA Client provides functionality to create an event log for=20
    an ICA file running in a remote desktop window.=20
17. On an ICA Client for Windows 95 or 98, when a user pressed=20
    CTRL+ALT+DELETE to display the Close Program dialog box, and=20
    then pressed the ESC key to return keyboard focus to a published=20
    seamless application, the CTRL and ALT keys remained virtually=20
    "stuck" in the DOWN position. All subsequent key pressing acted as=20
    if the CTRL and ALT keys were still pressed.=20
    The ICA Client cannot detect a change in the state of the CTRL=20
    or ALT keys if the application does not have keyboard focus. The=20
    client synchronizes the key states each time the application gains=20
    keyboard focus. When the Close Program dialog box opens, Windows=20
    does not inform the seamless application that it has lost keyboard=20
    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=20
    while the Close Program dialog box had focus.
    The client now monitors the state of the ALT key each time a key=20
    is pressed to re-synchronize the key states in case they=20
    changed unexpectedly.=20
    [#255238] =20
18. When the ICA Client File Security dialog box opened for an=20
    application being launched in seamless mode, users could still=20
    interact with other seamless windows running in the background,=20
    causing modality to be lost from the dialog box. If the dialog box=20
    was open and the user minimized another seamless application=20
    running in the background, the minimized application window could=20
    not afterward be maximized, used, or closed. The application=20
    running in the minimized window had to be reset by an administrator=20
    or closed in the Connection Center.=20
    A truly modal dialog box does not allow other windows to be used=20
    until the dialog box is closed. =20
    The issue was fixed by blocking messages from other windows while=20
    the File Security dialog box is open. =20
19. After the Client Auto Update feature updates the Program =20
    Neighborhood Client for a user who is not an administrator and is
    using Windows NT with pass-through authentication, two Program=20
    Neighborhood shortcut icons appear on the user's desktop after=20
    restarting the client device.=20
    The update process creates two shortcuts, and the second shortcut=20
    overwrites the first one. If registry entries needed for the=20
    update process already existed from a previous installation or=20
    update, then a file permissions issue prevented the second shortcut=20
    overwriting the first one, and both shortcuts appeared on the=20
    The Client Auto Update feature now checks if the registry entries=20
    already exist. This check prevents the permissions issue and the=20
    update process creates only one shortcut icon. =20
    To ensure proper updating, add this ICA Win32 Client version to=20
    the client update database on your MetaFrame servers.=20
20. If the Client Auto Update feature attempted to update a version=20
    of the ICA Client previous to Version 6.20.985, then Windows NT=20
    non-administrator users with pass-through authentication received=20
    errors when connecting to a MetaFrame server.=20
    An initial error message reported that pass-through authentication=20
    (Ssonsvr.exe) would be terminated. Another error message reported=20
    that a required .dll file (Pnipcn.dll) was not found.
    After restarting and running the Program Neighborhood Client, users=20
    repeatedly received a message stating, "The update of the Citrix=20
    ICA Client is complete. You must reboot your machine." Users had=20
    to manually delete the Reboot.lck file to stop the repeated=20
    If the Reboot.lck file is not deleted, the user repeatedly receives=20
    a message to reboot. The pass-through authentication feature in=20
    ICA Clients older than Version 6.20.985 does not provide permission=20
    to mark the Reboot.lck file for deletion. This ICA Client version=20
    renames the Reboot.lck file so that it can be deleted, allowing
    Client Auto Update to run successfully.=20
21. This item pertains only to the English ICA Win32 Clients.
    An unintended string was added automatically to the URL string=20
    that a customer specified as the Citrix Nfuse Classic server,    =20
    because a memory buffer was not being initialized. The buffer=20
    is now initialized to zero, and the extra string is not added
    to the NFuse server URL.
22. This item pertains only to the English ICA Win32 Clients.
    Users could not interact by keyboard with the Program Neighborhood=20
    user interface dialog box. Users could interact successfully with=20
    a mouse. The problem occurred because the dialog box incorrectly=20
    disabled keyboard focus control.=20
    This client correctly sets the keyboard focus and allows users to=20
    use a keyboard to interact with the dialog box.
23. This item pertains only to the English ICA Win32 Clients.
    NEC PC98 keyboards did not work in an Nfuse Classic session. The=20
    ICA Win32 Client was modified to support the NEC PC98 keyboard.=20
24. This item pertains only to the English ICA Win32 Clients.
    Pass-through authentication for a desktop connection did not work,=20
    requiring users to enter a password for every application. This=20
    issue occurred because the pass-through mechanism attempted=20
    to open a required file, Wfapi.dll, with its full path name,=20
    If WINNT\system32\wfapi.dll cannot be loaded, the client loads=20
    the Wfapi.dll file from the directories that are specified by=20
    the PATH environment. This solution allows pass-through=20
    authentication to work.
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.
26. Connecting to a published application from a Citrix Linux Client=20
    using the pass-through client on a MetaFrame server with 128-bit=20
    encryption generated an error. The error message reported that,=20
    "The application is enabled, but is not available. A higher=20
    encryption level is required, which the client does not support."=20
    The published application was set to a minimum requirement of=20
    128-bit encryption.
    The pass-through client Program Neighborhood detected the wrong=20
    encryption level for non-Windows clients by determining the level=20
    from the client's protocol driver encryption module name. This=20
    method does not work because the protocol driver encryption module=20
    name may not be the same across client platforms.=20
    The pass-through client Program Neighborhood now queries the=20
    terminal session for the client encryption level and allows you=20
    to successfully connect to a published application with 128-bit=20
27. Some applications that enumerate printers responded slowly when=20
    run from an ICA session if the default printer on the client=20
    device was a network printer. Users who specified a Novell=20
    Distributed Print Services (NDPS) print queue experienced a=20
    slow print rate when printing reports. Users also reported that=20
    logging on to an ICA session was slow if the default printer on=20
    the client device was a network printer. This issue was caused by=20
    the ICA Client attempting to open a file with an incorrect file=20
    name. The file name inconsistency has been corrected, and users=20
    experience faster response or logon rates when using a network=20
    printer as the default printer.=20
    If a client device's Printer.ini file contained the setting,=20
    "RawDataOnly=3DYES," some printer settings on the client device were =

    incorrrectly cleared in the printer settings of the auto-created=20
    printer for the ICA session. Because the print settings were
    some applications using the auto-created printer did not print=20
    properly. The issue was corrected by preserving other printer=20
    settings when the "RawDataOnly" option is set to "YES" in the=20
    client device's Printer.ini file.=20
    [#256297, 256477]
28. After auto-updating the Web Client, the Program Neighborhood=20
    shortcut icon showed up on a user's desktop even if the Program=20
    Neighborhood executable file (Pn.exe) didn't exist. The client now=20
    does not create the Program Neighborhood icon if the Pn.exe file=20
    doesn't exist.=20
29. If Secure Sockets Layer (SSL) was used, the Program Neighborhood=20
    Agent used up to 97% of available CPU when running four or more=20
    A timing window in the network transport code resulted in an=20
    invalid amount of available data being reported. Because the Program

    Neighborhood Agent code expected more data from the network=20
    transport layer than was actually available, it continued to issue=20
    reads attempting to retrieve additional data. This loop caused the=20
    high CPU utilization.
    The method used to determine when all available data is read=20
    was modified in the Program Neighborhood Agent. The modification=20
    eliminates continual reads attempting to retrieve additional data=20
    that does not exist. As a result, the high CPU utilization is=20
    Program Neighborhood Agent now operates with normal CPU utilization=20
    when using SSL and starting four or more applications.
30. Users experienced incorrect processing of mouse clicks after=20
    reconnecting to a disconnected session. In some applications users=20
    needed to click three times to achieve a double-click operation.=20
    The issue occurred in applications that modify the double-click=20
    time-out at runtime, because the double-click variable was not being

    restored after reconnecting. Double-click message processing has=20
    been moved to the server, and the mouse functions as expected.
    After installing this client, you should verify that the=20
    ClientMouseDoubleClickDetect option is set to "false" in the=20
    [WFCLIENT] section of either the Appsrv.ini file or the ICA file.=20
    [#257792, 258420]
31. If IntelliPoint mouse software was installed on a device running=20
    a Windows 2000 or previous operating system, and the "Hide pointer=20
    while typing" option was selected in the IntelliPoint settings,=20
    the mouse pointer disappeared while typing but did not reappear=20
    again when the mouse was moved.=20
    A hook procedure in the IntelliPoint software is now called and=20
    utilized to solve this issue. If the mouse pointer is set to=20
    disappear while typing, it now correctly reappears when you move=20
    the mouse.
    [#257924, 258517]=20
32. In a seamless session with only one window, if you minimized=20
    the window and then opened another window, the new window could
    lose keyboard focus. The client failed to place the newly-opened=20
    window in the foreground if there was no active seamless window=20
    in the session.=20
    With this client version, a window created from a minimized window=20
    receives keyboard focus.
33. When using content redirection with the Program Neighborhood Agent,=20
    associated file types displayed the Program Neighborhood Agent=20
    icon rather than the icon for the associated program. For example,=20
    if .doc files were associated with Microsoft Word, then .doc files=20
    on the client displayed with a Program Neighborhood Agent icon=20
    rather than a Microsoft Word icon.
    The operating system uses the HKEY_CLASSES_ROOT\<file
    registry key to select the icon to display for a file type. If=20
    there is no such key present, it then shows the icon of the=20
    application associated with it, which in this case happens to be=20
    the Program Neighborhood Agent.=20
    To resolve the problem, the Program Neighborhood Agent was=20
    modified to display icon files based on the data received from the=20
    server for each file type associated through content redirection,=20
    and to create the "DefaultIcon" registry key.=20
    After you install the new client version, file types associated=20
    through content redirection display the correct icons.=20
34. Program Neighborhood user-specified credentials for custom=20
    connections were ignored when pass-through authentication and=20
    the "Use local credentials to log on" option were enabled. The=20
    user-specified credentials were overridden by the local user=20
    If "Use local credentials to log on" is enabled, the local=20
    credentials are used regardless of the request flag=20
    (UseLocalUserAndPassword) in the Appsrv.ini file.
    This issue was resolved with a mechanism that checks the state
    of UseLocalUserAndPassword to select between local user=20
    credentials or user-specified credentials.=20
35. By default, the Program Neighborhood Agent client uses Internet=20
    Explorer's proxy settings for access to the Nfuse Classic Web=20
    server. However, if the client is directed to a proxy server that=20
    requires authentication or the Web server itself requests HTTP=20
    authentication for the Nfuse content, then the client cannot=20
    download configuration settings or enumerate applications.=20
    When receiving an HTTP status code indicating that authentication=20
    is required, the Program Neighborhood Agent did not take any=20
    action, resulting in the failure of the HTTP request.=20
    The Program Neighborhood Agent now handles both 401 and 407 HTTP=20
    status codes by collecting credentials from the user, adding=20
    the required authorization headers, and then retrying the HTTP=20
    When accessing an Nfuse Classic server through a proxy server that=20
    requires authentication, users are prompted to supply user=20
    credentials. If valid credentials are presented, the proxy server=20
    forwards the request to the Nfuse-enabled Web server,=20
    allowing the configurations settings to be read and applications=20
    to be enumerated.=20
36. If proxy auto-detection was enabled and Netscape Version 6.2.1=20
    or higher was used as the default Web browser, the ICA Win32=20
    Client failed to use the proxy server settings set in Netscape.
    An ICA Client with proxy auto-detection enabled uses the proxy=20
    settings of the client device's default Web browser. To determine=20
    which is the default browser, the client checks the file-type=20
    association in the system registry. If the registry associates=20
    Netscape 4 or higher with HTML files, the client uses the=20
    Netscape proxy settings. Otherwise, the client uses the proxy=20
    settings managed by Internet Explorer.=20
    Recent versions of Netscape (6.2.1 and higher) changed how=20
    Netscape registers itself to handle HTML files. This change=20
    caused the ICA Client to fail to detect Netscape as the default=20
    browser, resulting in Internet Explorer proxy settings being=20
    applied rather than the expected Netscape proxy settings.=20
    The ICA Win32 Client uses an updated method to determine which=20
    browser is registered to handle HTML files. Windows clients=20
    with proxy auto-detection enabled and Netscape 6.2.1 or higher=20
    as the default browser see the Netscape proxy settings applied=20
    instead of Internet Explorer proxy settings.=20
37. On client devices running Windows 95, 98, or ME, the ICA Client=20
    did not use the Netscape proxy server settings as expected when=20
    proxy auto-detection was enabled and Netscape 6.0 or higher was=20
    set as the user's default Web browser. The client could not find=20
    the Netscape proxy settings and used Internet Explorer settings=20
    instead. This issue was caused by a change in the directories that=20
    Netscape uses to hold user configuration files on Windows 9x=20
    The ICA Win32 Client now searches a wider range of possible=20
    directories to find the appropriate Netscape user configuration=20
    files, and correctly applies the Netscape proxy settings. =20
38. Pass-through authentication of Windows NT credentials does not=20
    work on a Windows NT workstation that belongs to a workgroup and=20
    has the Novell client installed. The client device passes to the=20
    MetaFrame server authentication credentials that contain the=20
    device's workgroup name instead of the MetaFrame server's domain=20
    After installing this ICA Win32 Client Version 6.31, you can=20
    modify the registry to override the pass-through authentication=20
    credentials that include the workgroup name. The registry value=20
    you add is used as the domain name credential during pass-through=20
    WARNING! Using Registry Editor incorrectly can cause serious=20
    problems that might require you to reinstall your operating system.=20
    Use Registry Editor at your own risk. Make sure you back up the=20
    registry before you edit it.
    A. Open the Registry Editor and navigate to the following registry=20
    B. From the Edit menu, choose Add Value and enter the following=20
       Value Name: Domain
       Data Type: REG_SZ
    C. Click OK and, in the String text box, enter the server's domain=20
       name (for Windows NT domain authentication). If you want to set=20
       up authentication only for local users of the MetaFrame server=20
       and not for domain users, enter the server's name.=20
    After you modify the registry, you can use Windows NT credentials=20
    with pass-through authentication on client devices that are Windows=20
    NT workstations, belong to a workgroup, and have the Novell client=20
39. A silent-user installation was not entirely free of user=20
    When you install the ICA Win32 Web Client (Ica32t.exe), a message=20
    box requiring a user response appears at the end of the setup.=20
    The message box states, "Setup completed successfully. You may=20
    need to restart your Web browser to activate changes." You=20
    must click OK to clear the message.=20
    For an unattended user installation of the ICA Win32 Web client,=20
    you limit user interaction by configuring the Ctxsetup.ini file=20
    to suppress dialogs or messages that require a user response.=20
    Previously you could suppress all other message boxes during the=20
    installation, but not this message box at the end of the=20
    You can now suppress the message with a setting that is included=20
    in the Ctxsetup.ini file. By default, the new "DisplayStatusMsg=3D1" =

    setting causes the message to appear. To suppress the message,=20
    you can change the "DisplayStatusMsg" setting to "0." After you=20
    make this configuration change, it is possible to completely=20
    install the Web Client with no user interaction.
40. When using the pass-through client, users were unable to log off=20
    the MetaFrame server if an ICA session was open. All pass-through=20
    ICA sessions had to be closed before users could log off the=20
    The pass-through client is an ICA Win32 Program Neighborhood=20
    Client published on a MetaFrame server. Connecting to the=20
    pass-through client allows users of different ICA Client=20
    platforms to access all published applications in the server farm=20
    regardless of platform. =20
    If you want to provide users with the ability to log off the=20
    server without first closing all pass-through ICA sessions, you=20
    can modify the registry of the MetaFrame server that publishes=20
    the pass-through client. When a user attempts to log off, this=20
    registry setting forces all open ICA sessions into a disconnected=20
    state and then allows the user to log off.=20
    WARNING! Using Registry Editor incorrectly can cause serious=20
    problems that might require you to reinstall your operating system.=20
    Use Registry Editor at your own risk. Make sure you back up the=20
    registry before you edit it.
    A. Open the Registry Editor and navigate to the following registry=20
       HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ICA Client\Pass Through
    B. From the Edit menu, choose Add Value and enter the following=20
       Value Name: QuickLogOff
       Data Type: REG_DWORD
       Data: 1
       Radix: Hex
    After you modify the registry, users can log off a MetaFrame=20
    server without first having to close all ICA sessions launched=20
    with the pass-through client.=20
41. The Program Neighborhood Agent passes incorrect credentials if=20
    the Novell Client is installed on the client device and=20
    pass-through authentication is being used. Because of the=20
    incorrect credentials, users cannot obtain a list of applications=20
    from the Citrix NFuse Classic server.=20
    If a client device uses Novell Directory Services (NDS) and=20
    pass-through authentication, the Program Neighborhood Agent sends=20
    NDS credentials to the Citrix MetaFrame server. If NDS is not=20
    configured on the MetaFrame server, the authentication fails.
    A new logon method, NT_SSON, has been added to the Config.xml=20
    file and the Program Neighborhood Agent to use in determining=20
    the type of credentials to use. If NT_SSON is defined, the server=20
    and Program Neighborhood Agent can use Windows NT credentials=20
    for authentication.
    If you have Novell Client installed on the client device and want=20
    to use Windows NT credentials with pass-through authentication,=20
    you must modify the value of the XML tag <LogonMethod> in the=20
    Config.xml file to NT_SSON. The Config.xml file is in the=20
    Inetpub\wwwroot\Citrix\PNAgent directory. The default Logon Method=20
    is SSON.
42. Application icons and shortcuts that were placed on the desktop=20
    or in the Start menu by the Program Neighborhood Agent on one=20
    client device were copied to the user's roaming profile and=20
    appeared on the desktop and in the Start menu when the user=20
    logged onto another client device where Program Neighborhood=20
    Agent was not installed. As a result, the application shortcuts=20
    did not work because Citrix client software was not installed on=20
    the client device.
    The shortcuts were placed into the user's profile by the Program=20
    Neighborhood Agent and were not being deleted when the user logged=20
    off from Windows. These shortcuts are now deleted from the desktop=20
    and the Start menu before Windows finishes logging off the user.
    To activate this feature in the Program Neighborhood Agent, the=20
    <Exit> value in the <FileCleanup> section of the Config.xml file=20
    on the Citrix NFuse Web server must be set to "true" and then the=20
    NFuse Web server must be rebooted.
    After you activate this feature, application icons and shortcuts=20
    are deleted from the desktop and the Start menu when a user logs=20
    off from Windows. When the user logs onto Windows, the icons and=20
    shortcuts reappear if the Program Neighborhood Agent starts up.
43. When using a pass-through ICA Client, client printers were not=20
    always auto-created with the correct name, causing some=20
    applications to fail to print. The pass-through client retrieved=20
    its name from a registry setting that is writable by any other=20
    ICA Client running on the same system. The registry setting for=20
    a client name was, therefore, not always consistent.
    Pass-through ICA clients now query their terminal session=20
    rather than the registry for the Client Name, ensuring that each=20
    client uses a consistent name and that printer names are built=20
    correctly by the MetaFrame server during auto-creation.=20
    The registry setting "HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\
    ICA Client\PASS THROUGH\PASS THROUGH" must be set to 1 on the=20
    pass-through server.=20
    Printers for pass-through clients are now auto-created with=20
    correct names.=20

-----Original Message-----
From: Michael Earley [mailto:Michael.Earley@xxxxxxxxxxxxxx]=20
Sent: Friday, October 18, 2002 10:50 AM
To: 'thin@xxxxxxxxxxxxx'
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

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

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

This weeks sponsor Emergent Online
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
For Archives, to Unsubscribe, Subscribe or=3D3D20
set Digest or Vacation mode use the below link.

This weeks sponsor Emergent Online
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
For Archives, to Unsubscribe, Subscribe or=3D3D20
set Digest or Vacation mode use the below link.


This weeks sponsor Emergent Online
Visit Jim Kenzig of thethin.net at the
Emergent Online Booth #221 at Citrix Iforum 2002!
Register now at:
For Archives, to Unsubscribe, Subscribe or=3D20
set Digest or Vacation mode use the below link.

This weeks sponsor Emergent Online
Visit Jim Kenzig of thethin.net at the
Emergent Online Booth #221 at Citrix Iforum 2002!
Register now at:
For Archives, to Unsubscribe, Subscribe or=20
set Digest or Vacation mode use the below link.

This weeks sponsor Emergent Online
Visit Jim Kenzig of thethin.net at the
Emergent Online Booth #221 at Citrix Iforum 2002!
Register now at:
For Archives, to Unsubscribe, Subscribe or=20
set Digest or Vacation mode use the below link.

This weeks sponsor Emergent Online
Visit Jim Kenzig of thethin.net at the
Emergent Online Booth #221 at Citrix Iforum 2002!
Register now at:
For Archives, to Unsubscribe, Subscribe or 
set Digest or Vacation mode use the below link.


Other related posts: