Hotfix XE102W065 - For MetaFrame XP 1.0 for Windows 2000 Server - English

Replaces:

XE102W006, XE102W008, XE102W010, XE102W011, XE102W019, XE102W023, XE102W024, XE102W026, XE102W029, XE102W036, XE102W053, XE102W064

1.

Users could not authenticate when using a Schlumberger smart card on the client and the Schlumberger smart card CSP and virtual channel on a server newly installed (not upgraded from MetaFrame Version 1.0 or Feature Release 1) with MetaFrame XP with Feature Release 2. After entering the PIN, the following error message appeared:

“Provider DLL failed to initialize correctly.”

The Schlumberger smart card CSP Dll file imports functionality from several Citrix DLL files located in the directory name\citrix\system32 directory, where directory name is the name of the directory where the Citrix DLL files were installed .

These files were moved to the %SystemRoot%\system32 directory and users can authenticate without error.

[From Hotfix XE102W006][#256661]

2.

Single Sign-On failed on a server newly installed (not upgraded from MetaFrame Version 1.0 or Feature Release 1) with MetaFrame XP with Feature Release 2 with the Pass-Through Client connecting to a published application.

A Citrix DLL was moved from the %directory name%\citrix\system32 directory, where directory name is the name of the directory where the Citrix DLL file was installed to the %SystemRoot%\system32 directory and Single Sign-On now works correctly.

[From Hotfix XE102W006][#257571]

3.

The browser could not enumerate application lists for older ICA Clients because they passed only one flag instead of two. This hotfix permits enumeration of the application list when only one flag is passed.

[From Hotfix XE102W008][#256897]

4.

When ICA listener names were changed from the default “ICA-tcp,” any attempt to shadow sessions from the shadow taskbar failed for all encryption levels except Basic.

MetaFrame XP looks for the default ICA listener name “ICA-tcp.” If this listener name is not found, the shadow taskbar defaults to Basic encryption.

With this hotfix, MetaFrame XP searches for ICA-tcp listeners of any name and determines the highest level of encryption in use by the listeners. The ICA file created to shadow a session is then set to the highest encryption level found.

[From Hotfix XE102W010][#249330]

5.

Events corresponding to event sources were showing up with no data in them. This problem occurred with the Citrix MetaFrame Management Pack for MOM development process. MOM is Microsoft Operations Manager 2000, which delivers enterprise-class operations management by providing comprehensive event management, proactive monitoring and alerting, reporting, and trend analysis. MOM health pack functionality relies on these events to be generated appropriately.

MetaFrame components were not registered correctly in the event log-related keys in the registry.

Installation of this hotfix causes an executable file to run that updates the registry entries for the MetaFrame components that were not registered properly. After installation of the hotfix, the event sources appear in the event log with the appropriate data.

[From Hotfix XE102W011][#254339]

6.

Sessions that were in a down state were not displayed as such in Citrix Management Console. Instead, the console displayed these sessions as disconnected or do not display any data at all. Other tools displayed the down sessions correctly.

This hotfix causes all the tools to display the sessions in a down state correctly.

[From Hotfix XE102W011][#254256]

7.

Upgrading from MetaFrame XP 1.0 to MetaFrame XP 1.0 with Feature Release 2 left two copies of the ImaRPCclient.dll on the server, with the older version the one being used. The Windows Management Instrumentation (WMI) events were not being generated by this DLL

This hotfix deletes the older DLL so that the newer one is used and events are generated correctly.

[From Hotfix XE102W011][#27149]

8.

Occasionally, if users attempted to log on immediately after logging off, they could not print to the default autocreated printer because another user’s printer was set as the default printer.

Installation of this hotfix resolves the issue.

[From Hotfix XE102W019][#250207]

9.

In an ICA session, if users clicked on a URL in an application such as Microsoft Outlook and a Web browser was already open, the session did not navigate to the new URL.

This occurred because a backup registry value used to establish DDE communication with the Web browser was set incorrectly.

With this hotfix, the registry value is set correctly and the URL will open correctly in a running Web browser.

[From Hotfix XE102W023][#257855]

10.

With MetaFrame XP Feature Release 2 and the Novell client installed on the same server, Single Sign-On did not work for the Pass-Through Client in an ICA session.

This problem had several causes:

A.

A known issue in Windows 2000 caused logon scripts not to run in certain situations.

B.

On a fresh installation of Feature Release 2, a Citrix DLL was not placed in the %SystemRoot%\system32 directory.

C.

Some third-party GINAs do not run logon scripts.

This hotfix moves the Citrix DLL to the %SystemRoot%\system32 directory and the logon script is triggered to run.

You need to perform the following workaround:

A.

Right-click My Network Places on the server console.

B.

Click Properties.

C.

From the Advanced pull-down menu, choose Advanced Settings.

D.

Click the Provider Order tab.

E.

Move NetWare Services below Citrix Single Sign-On.

F.

Click OK.

Single Sign-On will work correctly for the Pass-Through Client.

[From Hotfix XE102W024][#257573]

11.

Single Sign-On did not work if the primary Gina DLL was not the Citrix Gina DLL. User credentials were deleted when the Citrix Gina DLL was not the primary Gina DLL.

Some applications replace the primary Gina DLL with their own Gina DLL. When this occurred, the following registry key showed the custom Gina DLL instead of the Citrix Gina DLL:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\Current Version\Winlogon\GinaDll

With this hotfix, user credentials are not deleted even if the Citrix Gina DLL is not used. In addition, another DLL was moved to the %SystemRoot%\System32 directory and Single Sign-On now works properly.

[From Hotfix XE102W024][#258460]

12.

Ctxgina.dll would not load any third party Gina.dlls except for Nwgina.dll or MSGina.dll.

Functionality has been added so that other third party Gina.dlls can be loaded by Ctxgina.dll.

[From Hotfix XE102W024][#258354]

13.

When disconnecting from an ICA session on certain WBT devices, some modules remained active on the MetaFrame servers.

With this hotfix, the modules no longer remain as an active session on the MetaFrame servers.

[From Hotfix XE102W026][#249791]

14.

Users were unable to change window focus by toggling the window icons on the taskbar.

Installation of this hotfix resolves the issue.

[From Hotfix XE102W026][#253398]

15.

When setting the seamless flag to 0x01 in the following registry key, seamless session sharing was not being disabled as it should have been:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\Wfshell\TWI\SeamlessFlags

A path was not reading or using the registry flag to determine whether or not to share the session.

A modification to the path now disables session sharing as intended.

[From Hotfix XE102W026][#258522]

16.

Note: This hotfix item does not apply to the Japanese language version of MetaFrame XP 1.0 for Windows 2000.

When using Microsoft Word 2000, the AutoText ToolTip window occasionally disappeared for several seconds. Users sometimes noticed the AutoText ToolTip window blinking. This occurred when icon request messages were sent to both the Word 2000 document window and the ToolTip window. The solution is to exclude messages that request icon changes in these two windows.

To enable this feature, add the two registry entries detailed below.

A.

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

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI

B.

From the Edit menu, select Add Key and enter the following:

Key Name: OpusApp

C.

Open the OpusApp key you just created.

D.

From the Edit menu, select Add Value and enter the following:

Value Name: ClassName
Data Type: REG_SZ
String: OpusApp

E.

Select Add Value again and enter the following:

Value Name: Type
Data Type: REG_DWORD
Data: 00000100
Radix: Hex

F.

Navigate to the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI

G.

From the Edit menu, select Add Key and enter the following:

Key Name: _WwM

Note: This Key Name is case-sensitive. To type this Key Name, you must type an underscore, a W in uppercase, a w in lowercase, and an M in uppercase.

H.

Open the _WwM key you just created.

I.

From the Edit menu, select Add Value and enter the following:

Value Name: ClassName
Data Type: REG_SZ
String: _WwM

Note: This string is case-sensitive. To type this string, you must type an underscore, a W in uppercase, a w in lowercase, and an M in uppercase.

J.

Select Add Value again and enter the following:

Value Name: Type
Data Type: REG_DWORD
Data: 00000100
Radix: Hex

With this change, the AutoText ToolTip and the insertion-point cursor displayed in Microsoft Word 2000 no longer blink.

[From Hotfix XE102W026][#242516, 253407]

17.

When running seamlessly, some applications built using the Borland development environment, such as Delphi, sometimes allowed the parent window of a dialog box to go to the foreground, leaving no mechanism to return the dialog box to the foreground.

In a seamless session, the parent window can receive messages other than mouse-oriented ones, like a focus change request from the ICA Client. The parent window responds to the request and goes to the foreground.

This hotfix introduces a new seamless exception flag by which you can set the following registry value to have the ICA Client always send the mouse event messages to the server.

A.

Set the following registry value:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI

Value Name: SeamlessFlags
Value Type: REG_DWORD
Value: 0x400

B.

Install the Citrix ICA Client, Version 6.31 or later.

The parent window of a dialog box no longer moves to the foreground to cover the dialog box.

[From Hotfix XE102W026][#257632]

18.

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.

[From Hotfix XE102W029][#258382]

19.

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.

[From Hotfix XE102W029][#43971]

20.

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

Navigate to the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\ClientPrinterAutoCreate

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)

With this feature enabled, network printers are created as client printers in the ICA session.

[From Hotfix XE102W029][#258358]

21.

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.

[From Hotfix XE102W029][#43913]

22.

If an ICA Client device had printers whose print drivers were not approved on the server, an error event was sent to the server’s application event log. The following message appeared on 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.

[From Hotfix XE102W029][#44092, #42983]

23.

If a user in an ICA session had client printers created with the Universal Print 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 the Universal Print Driver. This negotiation did not take place.

This hotfix updates the server's ability to negotiate print capabilities with the client when reconnecting.

[From Hotfix XE102W029][#258138]

24.

A.

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.

[From Hotfix XE102W029][#258464]

B.

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.

[From Hotfix XE102W029][#258464]

25.

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

[From Hotfix XE102W029][#44560, #44539, #45000]

26.

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.

[From Hotfix XE102W029][#44535]

27.

Large MetaFrame XP Feature Release 2/Service Pack 2 server farms sometimes experienced data store contention problems when simultaneously adding or upgrading multiple servers to the farm. Similar problems sometimes occurred when using the
Mlicense.exe utility to add multiple licenses or when manually adding multiple licenses to these large farms.

When a new server was added to the farm and a dual CPU server was being used for the data store, the CPU usage on the data store server sometimes went to 100% for periods of time up to 30 minutes. Problems with installation integrity and Citrix Management Console connectivity were sometimes experienced during this time.

Because of the changes made in this hotfix, fewer read requests will be sent to the data store, resulting in improved data store/database performance. These changes will decrease installation and license addition times.

[From Hotfix XE102W036][#43961]

28.

When connecting to a published application through NFuse using credentials in a domain where the domain name contained an ampersand (&), the following error message appeared:

“The application encountered an error trying to connect to the MetaFrame server through NFuse. The ticketing feature is disabled on one or more MetaFrame servers. Please make sure the Citrix XML Service is running in the farm and that all are listening on the same port number.”

An ampersand is the escape character in XML and HTML. The Citrix XML parser attempted to parse the characters after the ampersand as an escape character sequence, which caused the error in the XML parser.

The ampersand in the domain name is now properly encoded in the XML request and the ticketing feature works as intended.

[From Hotfix XE102W053][#51707]

29.

If an ICA seamless session was disconnected, reconnecting to the session did not restore the system tray icon created by seamless applications in that session.

This occurred because the seamless 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 seamless sessions are reconnected. System tray icons are restored when reconnecting to an ICA seamless session.

[From Hotfix XE102W064][44697]

30.

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.

[From Hotfix XE102W064][#236618]

31.

In the Citrix Management Console, the IP Range Rule under Load Evaluators did not work. The parameters for the IP Range Rule 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 IP Range Rule under Load Evaluators so the values are saved in the data store and updated in the local host cache. The IP Range Rule under Load Evaluators will now work.

[From Hotfix XE102W064][#257582]

32.

On a MetaFrame XP Feature Release 2 server with Novell Directory Services (NDS) integration enabled, if the NDS tree name being passed from the ICA Win32 Client was longer than 15 characters, the SyncedDomainName feature failed and Pass-Through Authentication did not work. This occurred because not enough space was reserved in the memory buffer to store the contents.

The size of the memory buffer has been increased and the SyncedDomainName feature and Pass-Through Authentication work even if the tree name being passed from the ICA Win32 Client is longer than 15 characters.

[From Hotfix XE102W064][#47057]

33.

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 server did not recognize those sessions disconnected with the same user name but in a different user name format.

The MetaFrame server will now recognize disconnected sessions with the same user name but in a different user name format.

[From Hotfix XE102W064][#254396]

34.

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.
[From Hotfix XE102W064][#51005]

Applications that use shared OLE components (such as COM objects exported from Winword.exe) were not always removed from the Citrix 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 Citrix Management Console session list when they terminate.
[From Hotfix XE102W064][#49050]

Known Limitation

Published batch files can be removed from the Citrix 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 Citrix 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 Citrix 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.

[From Hotfix XE102W064]

35.

Sessions in Connected and ConnectQuery states could not be reset through the Citrix 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 Citrix Management Console.

[From Hotfix XE102W064][#46617]

36.

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.

[From Hotfix XE102W064][#51787]

37.

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.

[From Hotfix XE102W064][#45049]

38.

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.

[From Hotfix XE102W064][#51686]

39.

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.

This hotfix is effective with either one of the following scenarios:

•

The farm does not have a Feature Release 2 or above license

•

If the server has a Feature Release 2 license and Update printer properties at each logon is not checked under Autocreated Client Printers in the Citrix Management Console

[From Hotfix XE102W064][#46108]

40.

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.

[From Hotfix XE102W064][#45401]

41.

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 server, the LPT port is not mapped when a user logs on and no activity occurs on the client LPT port.

Limitations

•

This solution can be used only if all users are employing the ICA Win32 Client.

•

Do not apply this solution if users in an ICA session will print from legacy DOS applications.

[From Hotfix XE102W064][#258493]

42.

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.

[From Hotfix XE102W064][#52394]

43.

If a user was running a published application in a seamless session, disconnected from that session, and then started another application, the second application opened in a new seamless session. If the user then connected to the first application again, that application would run in the new seamless session instead of reconnecting to the disconnected session.

This occurred in the following three scenarios:

•

The winstation extension dll (Wsxica.dll) did not properly keep track of the initial program name in the disconnected session

•

By default, the functionality that enables sharing of a disconnected session with other applications was ON

•

The MetaFrame shell process (Wfshell) was not properly identifying whether or not the application was in a seamless session in the disconnect/connect sequences

This fix resolves the problem in the following manner:

•

The winstation extension dll (Wsxica.dll) properly keeps track of the initial program name in the disconnected session

•

By default, the functionality is now OFF

•

The MetaFrame shell process (Wfshell) properly identifies whether or not the application is in a seamless session

For the disconnected session to be shared with other applications, set the following registry value and restart the server:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix

Value Name: ReconnectWithNewApplication
Data Type: DWORD
Data: 0x00000001

This makes the disconnected session share the two applications.

[From Hotfix XE102W065][#50601]

44.

Performance of certain applications was considerably degraded in a seamless session, especially when moving or dragging windows.

This was caused by the server seamless engine forcing the session to enable “Full Window Drag” mode (referred to as “Show contents of window while dragging:) to send sufficient notification to the client (continuous display update information). This setting created significant performance overhead for certain applications.

A new seamless global flag, 0x800, has been introduced so that the seamless engine does not change “Full Window Drag”
mode when it is set.

Administrators can use the new seamless global flag to prevent “Full Window Drag” change. To do so, edit the following
registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI
Value Name: SeamlessFlags
Value Type: DWORD
Value: 0x800

With this change, degradation of performance in a seamless session no longer occurs.

[From Hotfix XE102W065][#52638]

45.

WARNING! This fix is valid only if you are not sharing the XML/NFuse port with IIS. Do not implement this registry change if you are sharing the XML port with IIS.

The XML Service could go into an endless loop, causing an NFuse Web 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 NFuse 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

[From Hotfix XE102W065][#61737]

1.

Download the hotfix package from the Hotfixes and Service Packs page of the Citrix Web site at http://www.citrix.com.

2.

Copy the hotfix package to an empty directory on the hard drive of the MetaFrame server.

3.

Close all applications.

4.

Run the executable.

5.

Shut down and restart the server.

1.

From the Start menu, select Setting > Control Panel.

2.

In Control Panel, double-click Add/Remove Programs.

3.

Highlight the hotfix you want to uninstall and click Add/Remove.

4.

Follow the directions on-screen.

brapi.dll

41,232

04/25/2003

01:31a

ccticket.dll

53,520

04/25/2003

01:31a

chgcdm.exe

74,000

04/25/2003

01:31a

ctxgina.dll

28,944

04/25/2003

01:31a

ctxnotif.dll

94,480

04/25/2003

01:31a

ctxrpc.dll

29,080

04/25/2003

01:31a

cutildll.dll

33,040

04/25/2003

01:31a

EventRegUpdate.exe

36,864

02/19/2003

04:48p

hotfix.exe

65,808

01/13/2003

07:48p

ImaLicSs.dll

246,168

04/25/2003

05:39p

ImaRpcClient.dll

28,944

03/03/2003

03:39p

LmsSS.dll

188,824

04/25/2003

05:39p

MfBrowserSs.dll

123,288

04/25/2003

05:39p

MFEvent.dll

24,848

04/25/2003

01:31a

MfPnSal.dll

49,424

04/25/2003

01:31a

MfPnSs.dll

139,672

04/25/2003

05:40p

MfSrvSs.dll

352,664

04/25/2003

05:40p

seamls20.dll

37,136

04/25/2003

01:31a

ServerFTA.exe

20,752

04/25/2003

01:31a

wfapi.dll

41,232

04/25/2003

01:31a

wfshell.exe

78,096

04/25/2003

01:31a

wshadow.exe

106,768

04/25/2003

01:31a

wsxica.dll

156,056

04/25/2003

01:31a