1. Users who had shadowing rights to specific users could view all users when
using the shadowing taskbar. With the installation of this hotfix, users
can view only those users for whom they have shadowing rights. [#45401]

2. Under certain circumstances, autocreated client printers were not deleted
when a user logged off from an ICA session. The logoff process could not
access the ICA Client name to determine which autocreated printers to
delete. With this hotfix, autocreated client printers are deleted when a
user logs off. [#52394]

3. Using the Program Neighborhood Client, when a user tried to refresh an
application set but did not enter user credentials at the prompt, the IMA
Service could not be stopped. The thread that reads the user credentials
from the client did not exit until either the user entered the user
credentials or discontinued refreshing the application set. With the
application of this hotfix, the IMA Service can be stopped even if the user
does not enter user credentials while refreshing the application set.
[#236618]

4. If the default printer on an ICA Client was a network printer, it was not
always set as the default printer in the ICA session if the user connected
to a Feature Release 2 server. The ICA session did not set the default
printer if the default printer on the client was a network printer and the
server already had a connection to that printer. With this fix, even if the
Feature Release 2 server already has a connection to the network printer,
the network printer is set as the default printer in the ICA session as
long as it is the default printer on the client device. [#51686]

5. In an ICA session, autocreated printers were always set to "Start printing
after last page is spooled" instead of "Start printing immediately" or
"Print directly to the printer." Users could change this setting during the
ICA session but the next time they logged on, the printers were again set
to "Start printing after last page is spooled." With this hotfix, even if
users in an ICA session change the settings for autocreated client
printers, the change is preserved in the users' profiles. Printer settings
will reflect the change at the next logon. [#46108]

6. When using the Citrix Management Console to import a network print server
and autocreate the network printers, users found that the printer copy
count changed at random in their ICA sessions. The DEVMODE, which
determines the copy count field for printers, was not always correctly set
for autocreated network printers. This fix ensures that the DEVMODEs for
network printers are valid before setting them. The printer copy count for
autocreated printers no longer changes at random. [#45049]

7. Sessions in Connected and ConnectQuery states could not be reset through
the Management Console. The following error message appeared: "Failed to
reset session: User information will be refreshed. Error code: 523." Those
sessions could be reset through tools like Terminal Service Manager.
Sessions in the ConnectQuery state were shown to be using the RDP
protocol when no protocol should have been visible. A change was made to
correct this behavior. Sessions in the Connected and ConnectQuery states
can now be reset through the Management Console. [#46617]

8. If a seamless ICA session was disconnected, reconnecting to the session did
not restore the system tray icons created by seamless applications in that
session. This occurred because the system tray agent did not notify the ICA
Client of the need to recreate the tray icons when the session was
reconnected. This hotfix introduces a function that refreshes the tray
icons when reconnecting to a disconnected seamless ICA session. The system
trays are now restored when reconnecting to the seamless ICA session.
[#44697]

9. Novell Directory Services users sometimes could not reconnect to their
disconnected sessions. Instead new sessions were established. NDS user
names can be in different formats. When searching for disconnected sessions
for a given NDS user name, the MetaFrame XP server did not recognize those
sessions disconnected with the same user name but in a different user name
format. The MetaFrame XP server will now recognize disconnected sessions
with the same user name but in a different user name format. [#254396]

10. In the Management Console, the rules under Load Evaluators did not work.
The parameters for the rules were not cached in the local host cache so the
Load Evaluators did not know which IP ranges to allow or deny. The data is
now cached in the local host cache. After installing this hotfix, edit the
rules under Load Evaluators so the values are saved in the directory and
updated in the local host cache. The rules under Load Evaluators will now
work. [#257582]

11. When running 16-bit Windows applications, some legacy interprocess
communication mechanisms (such as shared memory) no longer worked
properly. The use of Job Objects to track child processes to control the
removal of applications launched from batch files caused 16-bit
applications to be started in separate NTVDMs. This resulted in their
inability to communicate using shared memory. 16-bit applications that are
sharing a session are now launched in the same NTVDM. [#51005]

Applications that use shared OLE components (such as COM objects exported
from Winword.exe) were not always removed from the Management Console
session list even though they terminated. The use of Job Objects to track
child processes to control the removal of applications launched from batch
files caused this problem. When a published application created a COM
object causing another process (such as Winword.exe) to start, the new
process was associated with the published application's Job Object. If a
second published application used the COM components provided by the
Winword.exe process, when the first application terminated, it remained in
the session list until the second application released the COM components
and Winword.exe terminated. Applications that use shared OLE components
will now be removed from the Management Console session list when they
terminate. [#49050]

Known Limitation: Published batch files can be removed from the Management
Console session list before all the applications launched by the batch file
terminate. This hotfix disables a code change made to resolve a problem in
an earlier hotfix. That fix caused all published applications to be

associated with a Job Object that tracked all the child processes of the
original application. The Management Console was able to track the
processes started by a published batch file and continue to display the
published application in the session list until all the child processes had
terminated. You can re-enable the use of Job Objects for a published
application after installing this hotfix by modifying the registry on each
server that publishes the application. Create the following registry key if
it is not already created:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI
\StartInJobObject
A. Open the Management Console.

B. Right-click the application for which you want to enable Job Objects.

C. Select Properties. From the Properties dialog box, click the
Application Location tab.

D. Highlight the contents of the Command Line edit box and copy the text
to the clipboard.

E. In the Registry Editor, create a new DWORD registry value under the
key you created above and paste the text into the name of the new
value.

F. Leave the data in the value blank.

12. The IMA Service experienced a Dr. Watson when starting. This was caused by
a memory pointer not being initialized before being used to get the
server's NetBIOS information. A modification was made to ensure that
all memory pointers are initialized before being used to get the server's
NetBIOS information. The IMA Service starts without experiencing a Dr.
Watson. [#51787]

13. Printing to a server printer in an ICA session caused printing activity on
a client printer under the following conditions:
* A printer was attached to a certain LPT port on the server
* A printer was attached to a certain LPT port on the client
* The client port had the same name as the server port in item 1
* A user was employing the ICA Win32 Client

This problem was a side effect of server LPT port mapping. By default, in
an ICA session the server LPT port was mapped to the corresponding client
LPT port. During printing to the server printer attached to the server LPT
port, the Microsoft spooler service opened the LPT port and then
immediately closed the LPT port for printing optimization. However, because
of printer port mapping, the open server LPT port was translated to open
the corresponding client LPT port. A modification allows the program to
recognize the following registry switch on the MetaFrame server:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\ClientSettings
Data Type: DWORD
Value Name: fDisableLPTMappingAtLogon
Data: 1

If this registry switch is on the MetaFrame XP server, the LPT port is not
mapped when a user logs on and no activity occurs on the client LPT port.
Limitations
A. This solution can be used only if all users are employing the ICA
Win32 Client.

B. Do not apply this solution if users in an ICA session will print from
legacy DOS applications.
[#258493]
This is a fix Incorporated In Citrix MetaFrame XP Feature Release 3 (FR3)/ Service Pack 3.