[THIN] KB: CTX106118 - Hotfix XE104W2K3010 - For MetaFrame XP 1.0 for Windows 2003 Server
- From: "Jim Kenzig Kenzig.com" <jkenzig@xxxxxxxxx>
- To: thin@xxxxxxxxxxxxx
- Date: Tue, 10 May 2005 19:46:43 -0700 (PDT)
CTX106118 - Hotfix XE104W2K3010 - For MetaFrame XP 1.0 for Windows 2003 Server
This document was published at:
http://support.citrix.com/kb/entry.jspa?externalID=CTX106118
Document ID: CTX106118, Created on: May 6, 2005, Updated: May 6, 2005
Products: Citrix MetaFrame XP 1.0 for Microsoft Windows 2003
Attachment: XE104W2K3010.msp (1.2 MB)
http://support.citrix.com/servlet/KbServlet/download/6299-102-12986/XE104W2K3010.msp
Hotfix readme name: XE104W2K3010.HTM
Hotfix package name: XE104W2K3010.MSP
For: MetaFrame XP 1.0 with Feature Release 3/Service Pack 4 for Windows 2003
Replaces: XE104W2K3001, XE104W2K3004, XE104W2K3005, XE104W2K3008
Date: May, 2005
Language supported: English (US)
Readme version: 1.0
Note: This hotfix can be applied only to a Windows Server 2003 with MetaFrame
XP Version 1.0 with Feature Release 3 and Service Pack 4 installed.
Where to Find Documentation
This document describes the issue(s) solved by this hotfix and includes
installation instructions. You can find more information about MetaFrame for
Windows in the Administrator's Guide. The Administrator's Guide is in the \DOCS
directory on the Citrix MetaFrame Server CD. All product documentation is also
available from the Citrix Web site at http://www.citrix.com/support.
The Administrator's Guide is in an Adobe Portable Document (PDF) format file.
To view, search, and print the documentation, you need Adobe Reader 4 or above.
You can download the Reader for free from the Adobe Web site at
http://www.adobe.com.
Issue(s) Resolved in this Hotfix
Caution! Several items in this hotfix may 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.
1. Due to an access violation, a custom MFCOM application was experiencing a
fatal error while attempting to obtain Citrix virtual channel policy
information. This occurred because the reference count of the wrong MFCOM
object was incremented, which resulted in the original MFCOM object being freed
while it was still in use.
This fix corrects the issue.
[From Hotfix XE104W2K3001][#90079]
2. In large farms, when replicating an updated version of a printer driver to a
server that was using a previous version of the same driver, the update failed
on the destination server even though the event viewer on the source server
reported the update as successful. This occurred because the two versions of
the specific driver had inconsistent printer monitor configuration information
in the registry.
This fix corrects the issue by forcing the installation of the print monitor on
the destination server. If the monitor is not already installed, installation
is performed; otherwise, the driver installation process simply skips this step
and continues as expected.
[From Hotfix XE104W2K3001][#92899]
3. The feature that allows you to limit application launches to one concurrent
instance per user did not work when a user connected using a UPN name. This
occurred because the Independent Management Architecture (IMA) service, when
comparing the user names associated with sessions that were already already
open, did not check against UPN names.
This fix corrects the issue.
[From Hotfix XE104W2K3001][#94371]
4. In farms with more than one server, smart card users could not reconnect to
disconnected sessions. This occurred because sessions of smart card users were
not associated with actual user or computer names, and therefore the server
hosting the disconnected session could not be identified. This fix corrects the
issue.
[From Hotfix XE104W2K3001][#101409]
5. If a server had more than one network interface card (NIC), but not all
cards were bound to ICA-TCP listeners, incoming ICA connections were attempted
on all NICs, including those not bound to ICA-TCP listeners. This occurred
because MetaFrame operated under the assumption that all NICs were bound to
ICA-TCP listeners.
This fix corrects the issue.
[From Hotfix XE104W2K3001][#104098]
6. On occasion, launching a published application from within a user session
failed. This occurred because of a code error.
This fix corrects the issue.
[From Hotfix XE104W2K3004][#103660]
7. If extended characters were used in elements of a seamless window, such as
window titles or the notification area (system tray), the characters may have
displayed incorrectly if the server's system code page was different from the
client's. This occurred because the extended characters were not translated
accurately between server and client.
This fix corrects the issue.
[From Hotfix XE104W2K3005][#94146]
8. After closing modal dialog boxes of certain published applications in
seamless mode, focus occasionally went to other windows on the client desktop
rather than to the application that launched the dialog, and you had to click
on the seamless application title bar to get focus back to the application.
Applications affected by this issue use a zero-sized window at coordinates
(0,0) to hold focus between the time the modal dialog closes and the time the
application window is reenabled. The seamless code recognizes this window as
invisible and, therefore, does not send seamless protocol messages to it.
Although this behavior was a designed, it was considered inconvenient by users,
and this fix corrects the issue.
[From Hotfix XE104W2K3005][#95001]
9. When attempting to launch an application published on Windows Server 2003
using NDS credentials, the following message appeared:
"You do not have access to logon to this session."
This occurred because NDS was not properly initialized, which caused user
authentication to fail.
This fix corrects the issue.
[From Hotfix XE104W2K3005][#98490]
10. A memory leak was caused by a custom Terminal Services API to enumerate
processes.
This fix corrects the issue.
|
[From Hotfix XE104W2K3005][#100466]
11. If run on computers running Windows Server 2003, the shadow taskbar may
have become unresponsive while enumerating servers. This occurred because of an
invalid memory address lookup.
This fix corrects the issue.
[From Hotfix XE104W2K3005][#103290]
12. If an application performed a specific action upon pressing the Escape key,
switching from a seamless window with a menu open to a desktop window caused
that action to be executed, even if the Escape was not pressed.
This fix corrects the issue.
[From Hotfix XE104W2K3005][#104173]
13. An access violation sometimes caused servers to experience a Terminal
Services related blue screen. This occurred if the state of an anonymous user
session became invalid during the logon or logoff process. The session state
was not verified before calling a Microsoft API.
This fix corrects the issue.
[From Hotfix XE104W2K3005][#108555]
14. Occasionally, the IMA Service experienced a fatal error while performing
load management tasks to select the least loaded server in a farm. The issue
occurred because insufficient space was allocated for a local string, which
caused a buffer overflow.
This fix corrects the issue.
[From Hotfix XE104W2K3008][#106078]
15. This is an enhancement allowing you to redirect specific URLs from server
to client, without redirecting other URLs.
A new registry key, HKEY_LOCAL_MACHINE \SOFTWARE\Citrix\SFTA\ValidSites, lets
you specify URLs to be redirected from server to client.
To implement this enhancement, make the following value changes to the registry
key using regedt32:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\SFTA
Name: ValidSites
Type: REG_MULTI_SZ
Data: Specify any combination of URLs
Note: The values must be line-delimited, for example:
www.my_URL.com
*.my_URL.com
The asterisk (*) is supported as a wildcard character.
[From Hotfix XE104W2K3010][#88382]
16. Users were sometimes unable to shadow other users and they were unable to
enumerate the necessary objects from the Shadow Taskbar (wshadow.exe). This fix
corrects the issue and also introduces the following functionality change:
By default, only local and Citrix administrators can enumerate the Applications
node. To enable other users to enumerate the node, you must create the
following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\IMA
Name: EnableAppEnumForUsers
Type: REG_DWORD
Data: 0 (Disable) or 1 (Enable)
You must restart the IMA service for the registry change to take effect.
[From Hotfix XE104W2K3010][#94764]
17. Users without Windows user profiles and users whose profile had been
modified, were unable to launch published applications.
This fix corrects the issue.
[From Hotfix XE104W2K3010][#101958]
18. ICA sessions failed to launch the associated media player for URLs starting
with mms:// and the multimedia files did not play back.
This fix corrects the issue.
[From Hotfix XE104W2K3010][#103537]
19. Smart card pass-through authentication failed after installing Service Pack
1 for Windows 2003. The issue occurred because of changes in the Windows logon
code introduced with Service Pack 1 to prevent race conditions during smart
card logons.
This fix corrects the issue.
[From Hotfix XE104W2K3010][#111392]
Installation Instructions
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 Administrator?s Guide or the Citrix Installation Manager
Administrator?s Guide.
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.
Note: To install this hotfix silently, use the /q option after the executable.
For example:
msiexec /P XE104W2K3010.MSP /q
Using the /q option without additional options automatically restarts the
server.
For additional information about msiexec, see the Microsoft Web site at
http://www.microsoft.com. Search on keyword msiexec.
Uninstallation Instructions
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 Remove.
4.
Follow the directions on-screen.
Files Updated
CPatch.exe
25,600
04/28/2005
04:42p
ctxgina.dll
23,040
05/02/2005
06:04p
ctxnotif.dll
188,416
05/02/2005
06:04p
ctxrpc.dll
20,616
05/02/2005
06:13p
iexplore.exe
36,864
05/02/2005
06:04p
ImaMfRpc_Client.dll
29,696
05/02/2005
06:04p
LmsSS.dll
200,840
05/02/2005
06:14p
mfappsal.dll
135,168
05/02/2005
06:04p
mfappss.dll
450,696
05/02/2005
06:14p
mfbrowsersal.dll
17,408
05/02/2005
06:04p
mfbrowserss.dll
131,208
05/02/2005
06:14p
mfcom.exe
221,184
05/02/2005
06:04p
mfcomsrv.dll
454,656
04/28/2005
04:42p
mfcontentsal.dll
25,600
05/02/2005
06:04p
MFContentSs.dll
86,152
05/02/2005
06:14p
mferror.dll
15,872
05/02/2005
06:04p
mfevent.dll
12,288
05/02/2005
06:04p
mfpnsal.dll
36,864
05/02/2005
06:04p
mfpnss.dll
143,496
05/02/2005
06:14p
mfprintsal.dll
69,632
05/02/2005
06:04p
mfprintss.dll
397,448
05/02/2005
06:15p
mfrpcss.dll
209,032
05/02/2005
06:15p
MFRules.dll
48,128
04/28/2005
04:42p
mfsrvsal.dll
172,032
05/02/2005
06:04p
mfsrvss.dll
442,504
05/02/2005
06:15p
mfstatus.dll
13,824
05/02/2005
06:05p
seamls20.dll
57,344
05/02/2005
06:05p
wfshell.exe
167,936
05/02/2005
06:05p
wshadow.exe
114,688
05/02/2005
06:05p
wsxica.dll
258,184
05/02/2005
06:17p
Copyright © 2005 Citrix Systems, Inc. All rights reserved.
Citrix, MetaFrame, and MetaFrame XP are registered trademarks of Citrix
Systems, Inc. in the United States and other countries.
All other trademarks and registered trademarks are the property of their
respective owne
Other related posts:
- » [THIN] KB: CTX106118 - Hotfix XE104W2K3010 - For MetaFrame XP 1.0 for Windows 2003 Server
