WARNING! Several of the procedures below require that you make changes to the
registry. Using Registry Editor incorrectly can cause serious problems that may
require you to reinstall your operating system. Citrix cannot guarantee that
problems resulting from the incorrect use of Registry Editor can be solved. Use
Registry Editor at your own risk.

Make sure you back up the registry before you edit it.

1. In an ICA session, the period (.) key did not work on servers and Linux
Client devices configured with an Italian keyboard layout. Pressing the
period (.) key produced a comma (,) instead.

This occurred because the key code for a period from a UNICODE client was
not mapped to the correct Windows scan code.

The scan code for an Italian keyboard has been corrected and pressing the
period key now produces a period on screen. [#50852]

2. Diacritic keys did not work on UNIX and Linux Clients configured with a
Swiss French keyboard layout. This occurred because the diacritic key
UNICODE mappings were not properly defined or were missing in the Swiss
French keyboard (.kbd) file.

The Swiss French keyboard file now contains the correct UNICODE mappings
and the diacritic keys behave correctly. [#50858]

3. Servers sometimes experienced a fatal system error caused by Wdica.sys with
error code 0x50:

"PAGE_FAULT_IN_NONPAGED_AREA"

Certain string pointers in Wdica.sys were not always initialized before
being used and, therefore, pointed to random memory. Wdica.sys copied this
random memory into the local buffer, destroying the call stack and
causing the fatal system error.

Now the string pointers are always initialized before being used. This
prevents the call stack from being destroyed and the fatal system error no
longer occurs. [#52031]

4. The Program Neighborhood service was losing 800 bytes of memory if a user
clicked "Cancel" in the Credentials dialog box while doing an application
set refresh using the Program Neighborhood Client.

This occurred because certain buffers were not being freed under the above
condition.

A change allows the program to free the memory buffer under the above
condition and the Program Neighborhood service no longer loses memory.
[#56002]

5. The IME 2002 toolbar did not appear in a non-desktop session. Ctfmon.exe
was not running in the non-desktop session and IME 2002 did not appear
without the existence of Ctfmon.exe.

If the session's active input locale is IME 2002 and Ctfmon.exe is in the
registry, Seamls20.dll creates the process of Ctfmon.exe. When this occurs,
the IME 2002 toolbar appears in the non-desktop session. [#56935]

6. The MetaFrame XP server returned an IP address of a network that was not
accessible by the master ICA browser. When the client attempted to connect,
a connection error similar to the following appeared:

"No Route to Subnet."

If ICA browser traffic is not desired on specific networks, you can disable
the traffic using the networks' IP addresses. Make the following changes to
the registry.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ICABrowser\Parameters
\DisabledTcpAddress
REG_SZ:x.x.x.x y.y.y.y

where x.x.x.x and y.y.y.y (separated by a space) designate two IP
addresses for which to disable ICA browser traffic. [#234737]

7. In MetaFrame 1.8, domain administrators were unable to use Published
Application Manager to move servers to a farm if both the following were
true:
* The farm was outside their domain
* The farm already contained published applications
Published Application Manager did not perform this function correctly.
Also, published application information is stored in the registry and
remote registry calls fail unless administrators have access to the domain.

Published Application Manager has been fixed to allow administrators to
move servers to a remote farm to which they have access. You can give
domain administrators access by adding them to the local administrators
group of each server in the farm in the target domain. [#257710]

8. An imported print queue stores the print driver information within the data
store. If the print driver was modified on the print server, the data store
could not be "refreshed" with the new information. Having the wrong driver
information in the data store prevented the printer from being autocreated.

This fix allows the print driver information to be updated in the data
store to reflect changes made at the print server. Printers will be
autocreated.
[#30912]

9. When attempting to shadow a session under the Management Console on a
MetaFrame XP server with an ICA port number of something other than the
default 1494, the following error message appeared:

"The Citrix server is not accepting connections."

When shadowing a session using the Management Console on a MetaFrame XP
server, a new ICA session was established by using an automatically
generated ICA file. This new file did not reflect the new ICA port
number so connection to a new session was attempted using the default port
number of 1494 and connection failed.

Modifications were made to the automatically generated ICA to add an entry
(ICAPortNumber=xxxx) to indicate the different port number. With this
modification, connection will succeed with the alternate port number.
[#43919]

10. Diacritic dead keys such as acute, grave, circumflex, diaeresis, and
cedilla did not work properly when using an English language client
connected (with the ICA keyboard set to Server Default) to a MetaFrame
server with a Dutch keyboard layout. This occurred because the diacritic
key UNICODE mappings were not properly defined in the Dutch keyboard (.kbd)
file.

The Dutch keyboard file now contains the correct UNICODE mappings and the
diacritic keys behave as dead keys. When a diacritic key is pressed, no
output is displayed until the next key is pressed. [#46164]

11. After migrating from MetaFrame 1.8 to MetaFrame XP, the master ICA browser
settings "Master ICA Browser Update Delay" (seconds) and "Refresh Interval"
(seconds) appeared to be reversed when viewed using the Management Console.

Note: These settings are visible only when running MetaFrame XP in
Interoperability mode.

This occurred because the numeric entry fields for the master ICA browser
settings were placed next to the wrong descriptions in the User Interface
(UI). Modifications were made so the appropriate numeric entry field is
placed next to the correct description.

When viewing the master ICA browser settings in the Management Console, the
values are consistent whether being viewed prior to migration or after
migration. [#46554]

12. The IMA Service occasionally experienced a fatal error when an
administrator browsed server session information using the Management
Console.

This occurred because the code dealing with the server session information
was not handling out of memory errors correctly. When out of memory errors
occurred, some of the memory buffer was deleted but the program was still
trying to access the deleted memory buffer.

A modification was made to handle out of memory errors properly in the code
that deals with server session information and the IMA Service performs
correctly. [#54603]

13. The IMA Service randomly experienced a fatal error on the data collectors.
The error also occurred occasionally when opening the Management Console on
the data collectors.

This occurred when an append exception on IMA buffer was thrown and not
caught.

This fix catches the append exception when allocation fails and writes the
information to an event log. A new data collector with sufficient memory is
elected and the IMA Service no longer experiences a fatal error. [#56229]

14. When using the SetZoneRanking function referenced in the MFCOM SDK to
change the zone ranking of a server in the farm, the server's zone ranking
did not actually change and no error was returned from the function call.

The zone ranking can now be changed using the SetZoneRanking function
referenced in the MFCOM SDK. [#249955]

15. Running an application whose associated small icon (which appears in the
task bar) frequently changed in seamless sessions caused the session to
stop accepting the icon change.

An internal function in the seamless engine, which changes the handle of
icons associated with an application, was not deleting the GDI object used
in that function.

New logic was added to that function to prevent the GDI handle leak and
icon changes in a seamless session works continuously. [#45336]

16. When an ICA session with an application accessing a smart card reader is
disconnected and reconnected, the application could detect a problem but
could not recover. The application did not function properly after
reconnecting. Client device mapping is used to enable an application
running on a MetaFrame server to access a smart card reader connected to a
client device. The device mapping was not properly reestablished when the
disconnected session was reconnected.

The smart card device mapping was modified so that it is properly
reestablished when a disconnected session is reconnected. When an ICA
session with an application accessing a smart card reader is disconnected
and reconnected, the application will resume normal operation if proper
recovery steps are taken within the application. [#59489]

17. The XML Service could go into an endless loop, causing a Web Interface
(formerly NFuse) page to hang during enumeration of applications. As a
result, users could not enumerate published applications or connect to
published applications. The XML Service used in the Web Interface
configuration settings was requesting tickets from remote XML servers that
were failing to respond.

This fix implements a ticket request time-out to prevent the XML Service
from going into an endless loop on failed connections. If the request times
out, the request fails and an event message is sent notifying the
administrator that a remote server failed. The default time-out for
connection attempts is set to five minutes (300000 milliseconds). To modify
this time-out to a lower value, you need to add the following to the
registry:

HKEY_LOCAL_MACHINE\SYSTEM\Services\CtxHttp
Value: SocketTimeout
REG_DWORD: Time-out number value in milliseconds
[#61737]