CTX896772
MetaFrame XP 1.0 for Microsoft Windows 2000
MetaFrame XP 1.0 for Microsoft Windows 2000
1970-01-01
1970-01-01

Hotfix XE102W029
Filename: XE102W029.MSI
For: MetaFrame XP 1.0 for Windows 2000
Replaces: XE102W019, XE102W023, XE102W026
Date: September 18, 2002
Language Supported: English

Description

This hotfix can be applied only to a Windows 2000 Server with MetaFrame XP Version 1.0 with Feature Release 2/ Service Pack 2 installed.

WARNING! Several items in this hotfix require you to edit 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.

Where to Find Documentation

This document describes the issue solved by hotfix XE102W029 and includes installation instructions. You can find more information in the MetaFrame XP Administrators Guide, located in the DOC directory on the MetaFrame XP CD. All product documentation is also available from the Citrix Web site at www.citrix.com.

The Administrators Guide is in an Adobe Portable Document format (PDF) file. To view, search, and print the documentation, you need Acrobat Reader 4 or above. You can download Acrobat Reader for free from the Adobe Web site at http://www.adobe.com.

Issues Resolved in this Hotfix

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

Installation of this hotfix resolves the issue.
[From Hotfix XE102W019][#250207]

2. 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]

3. 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]

4. 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]

5. 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_MACHINESYSTEMCurrentControlSetControl CitrixWfshellTWISeamlessFlags

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]

6. 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_MACHINESYSTEMCurrentControlSet ControlCitrixwfshellTWI

B. From the Edit menu, choose Add Key and add a key with the following information:

Key Name: OpusApp

Note that you do not need to enter a value in the Class text box.

C. Open the OpusApp key you just created.

D. From the Edit menu, choose Add Value and add a value with the following information:

Value Name: ClassName
Data Type: REG_SZ
String: OpusApp

E. From the Edit menu, choose Add Value again and add a value with the following information:

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

F. Navigate back to the TWI registry key:

HKEY_LOCAL_MACHINESYSTEMCurrentControlSet ControlCitrixwfshellTWI

G. From the Edit menu, choose Add Key and add a key with the following information:

Key Name: _WwM

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

H. Open the _WwM key you just created.

I. From the Edit menu, choose Add Value and add a value with the following information:

Value Name: ClassName
Data Type: REG_SZ
String: _WwM

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

J. Choose Add Value again and add a value with the following information:

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]

7. 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_MACHINESYSTEMCurrentControlSetControl CitrixwfshellTWI

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]

8. 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]

9. 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_USERSoftwareMicrosoftInternet 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]

10. Printing to an ICA Client devices 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 Microsofts 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_MACHINESYSTEMCurrentControlSetControl CitrixClientPrinterAutoCreate

Add the following value:

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.
[From Hotfix XE102W029][#258358]

11. 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]

12. If an ICA Client device has printers whose print drivers are not approved on the server, an error event is sent to the servers 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.
[From Hotfix XE102W029][#44092, #42983]

13. 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 servers ability to negotiate print capabilities with the client when reconnecting.
[From Hotfix XE102W029][#258138]

14. 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 users 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_MACHINESYSTEMCurrentControlSetControl CitrixClientPrinterProperties

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.

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]

15. 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_ROOThttpshellopencommand

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_MACHINESOFTWARECitrixSFTA
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.
[From Hotfix XE102W029][#44560]

16. 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]

Installation Instructions for Hotfix XE102W029

NOTE: This hotfix is packaged with Microsoft Windows Installer. You can deploy the hotfix package to a group of servers using Microsoft Active Directory Group Policy Object or using Citrix Installation Manager. For more information, see the Citrix server Administrators Guide or the Citrix Installation Manager Administrators Guide.

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

2. Copy XE102W029.MSI to an empty directory on the hard drive of the MetaFrame server.

3. Close all applications.

4. Run XE102W029.MSI.

5. When prompted, click Yes to shut down and restart the server.

Uninstallation Instructions for Hotfix XE102W029

To uninstall the hotfix:

1. From the Start menu, select Settings > Control Panel.

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

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

4. Follow the directions on-screen.

Files Updated

chgcdm.exe

74,000

 

09/26/2002

01:29p

ctxnotif.dll

94,480

 

09/26/2002

01:29p

hotfix.exe

57,616

 

08/20/2002

08:05p

seamls20.dll

37,136

 

09/26/2002

01:29p

ServerFTA.exe

20,752

 

09/26/2002

01:29p

wfshell.exe

78,096

 

09/26/2002

01:29p

wsxica.dll

151,960

 

09/26/2002

01:29p


特别说明


本文来源为Citrix.com所有,翻译后版权归翻译者所有.如需转载请注明出处.

文档版本


.

广告招租


最新留言


.

广告招租


.