1. Users were sometimes asked if they wanted to make Internet Explorer their
default browser the first time they launched it in an ICA session. If the
users clicked "Yes," content redirection did not always work in that
session. This problem occurred because the code in a .dll did not change
the following registry value as was intended:
HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer \Main
Value Name: Check_Associations
Value Type: REG_SZ
Value: no

The code has been moved to an executable and the registry value is now
always changed. Users are no longer asked if they want to make Internet
Explorer their default browser and content redirection works properly.
[#43971]

2. When logging on from an ICA Client that has networked printers, a Dr.
Watson sometimes occurred when autocreating the client printers. This
occurred because an executable file was not checking for a null pointer.
The executable file has been updated so it will check for the null pointer
and ICA Clients with networked printers can logon to an ICA session without
error. [#43913]

3. If an ICA Client device has printers whose print drivers are not approved
on the server, an error event is sent to the server's application event
log. The following message appears by the ICA Client device: "Printer
Creation." "One or more printers could not be created due to a driver that
has not been approved for use on this server. Please contact your system
administrator." The program has been modified so the error message no
longer appears. [#44092]

4. If a user in an ICA session had client printers created with a universal
printer driver, the user could not print to those printers after
reconnecting to the ICA session. When reconnecting, the server
negotiates with the client about using the printers created with a
universal driver. This negotiation did not take place. This hotfix updates
the server's ability to negotiate print capabilities with the client when
reconnecting. [#258138]

5. Printing to an ICA Client device's networked printer through an ICA session
was sometimes slower in Feature Release 2 than in Feature Release 1. This
occurred when the Feature Release 2 server and the ICA Client were
separated by a wide area network (WAN) and the networked printer was on the
client side of the network. Another problem occurred when the Feature
Release 2 server and the ICA Client device were on two separate networks
and both networks had a networked printer with the same name. Print jobs
that intended to be printed on the networked printer on the client side
were instead sent to the networked printer on the Feature Release 2 server
network instead. When a Feature Release 2 server is separated from the ICA
Client by a wide area network (WAN) and the networked printer is on the ICA
Client side of the network, printing is slower when the server connects
directly to the networked printer, rather than when a Feature Release 2
server creates a client print queue for the networked printer. This occurs
in the first example above because print data is sent using Microsoft's SMB
protocol. In the second example, print data is sent using Citrix' ICA
protocol, which offers data reduction. The hotfix introduces a registry
switch so that you can toggle which functionality you want - direct
connection to network printers from a Feature Release 2 server or the
network printers created as client printers that print through the ICA
Client device. Create the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix
\ClientPrinterAutoCreate
Add the following values:
Value Name: fCreateNetworkPrinter
Value Type: DWORD
Value: 1 (to have network printers created as client printers)
Value: 0 (to retain the Feature Release 2 behavior)

Reboot the system for the value you entered to take effect. With this
feature enabled, network printers are created as client printers in the ICA
session. [#258358]

6. If a user reconnected to an ICA session from a client device that was not
the one used for the original connection, the printers on the new client
device did not get autocreated. Now if the client device used to reconnect
to an ICA session is different from the one used for the original
connection, printer autocreation will occur. If this feature is on when a
user disconnects, all print jobs and printers are deleted. When the user
reconnects, the client printers are autocreated.
NOTE: MetaFrame does not differentiate between a disconnection caused by
the user's intent or one caused by network problems. If sessions can be
dropped constantly because of network problems, Citrix recommends that you
do not turn this feature on.
To turn this feature on, navigate to the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix
\ClientPrinterProperties
Value Name: fReconnectionPrinterReconfig=1
Value Type: REG_DWORD
Restart the system after you change the registry for the change to take
effect.

To turn this feature off: Navigate to the above registry key.
Value Name: fReconnectionPrinterReconfig=0
Value Type: REG_DWORD
Restart the system after you change the registry for the change to take
effect. [#258464]

7. Task Manager showed that Wfshell.exe leaked one handle each time a user
reconnected to an ICA session. Wfshell.exe did not close the handle after
reconnection. Wfshell.exe has been modified so that it will close the
handle after reconnection. This eliminates the handle leak problem.
[#258464]

8. Internet Explorer sometimes did not open in the same window size as it did
when it was last run. This was caused by Content Redirection launching an
instance of Internet Explorer using the SW_SHOW Windows flag. With this
hotfix, Content Redirection launches an instance of Internet Explorer using
the SW_SHOWNORMAL Windows flag. Internet Explorer opens with the same size
window as when it was previously opened. [#44535]

9. After installing or upgrading to MetaFrame XP, Feature Release 2/Service
Pack 2, some applications experienced a problem when launching a Web
browser. Symptoms of the problem were that a Web browser would not open,
that the browser opened a URL passed to it incorrectly, or certain
attachments that can be opened in a browser did not open. The problem
occurred because the following registry key was backed up and
changed to
the MetaFrame server FTA executable after Service Pack 2 was installed.
Also, some applications may be hard coded to look for popular Web browsers
such as Iexplore.exe or Netscape.exe:
HKEY_CLASSES_ROOT\http\shell\open\command
This hotfix introduces a registry flag that gives you the ability to turn
off the file type associations created by the MetaFrame server FTA and
restore them to their original values. To disable the file type
associations for server FTA, you need to create the following registry key
for SFTA:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\SFTA
Value Name: DisableServerFTA
Value Type: DWORD
Value: 1
If you use the registry value of 1, you cannot use "Enable content
redirection from server to client" for that server. [#44560]

10. Sometimes Microsoft Terminal Server experienced a fatal system error. This
occurred when some portion of the MetaFrame XP data store became corrupt
and a Citrix Dll received incorrect data. The Citrix Dll could not process
the incorrect data. The program has been modified so that even if the
MetaFrame data store becomes corrupt, the Microsoft Terminal Service will
remain running. [#258382]
This is a fix Incorporated In Citrix MetaFrame XP Feature Release 3 (FR3)/ Service Pack 3.