[THIN] CTX104121 - Hotfix XE103W2K119 - For MetaFrame XP 1.0 for Windows 2000 Server
- From: "Jim Kenzig http://thin.net" <jimkenz@xxxxxxxxxxxxxx>
- To: thin@xxxxxxxxxxxxx
- Date: Wed, 26 May 2004 08:17:16 -0400
English
This document was published at:
http://support.citrix.com/kb/entry.jspa?externalID=CTX104121
Document ID: CTX104121, Created on: May 20, 2004, Updated: May 21, 2004
Products: Citrix MetaFrame XP 1.0 for Microsoft Windows 2000
Attachment: XE103W2K119.msi (505.0 K)
Hotfix readme name: XE103W2K119.HTM
Hotfix package name: XE103W2K119.MSI
For: MetaFrame XP 1.0 with Service Pack 3 for Windows 2000
Replaces: XE103W2K008, XE103W2K025, XE103W2K036, XE103W2K064, XE103W2K075
Date: May, 2004
Language supported: English (US)
Note: This hotfix can be applied only to a Windows 2000 Server with
MetaFrame XP Version 1.0 with Feature Release 3/Service Pack 3 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 Adobe Reader for free from the Adobe Web site at
http://www.adobe.com.
Issue(s) Resolved in this Hotfix
1.
Note: This line item was fixed in non-English versions of Feature Release 3
with Service Pack 3.
When the alternate address was set with an IP address and a port number, the
Citrix XML Service returned an I/O error.
The IP address and the port number are stored as a single string in the
registry. The code that separates these two failed.
The fix inserts a terminating character in the string to separate the IP
address and the port number. The alternate address with an IP address and a
port number are returned to the ICA Client.
[From Hotfix XE103W2K008][#51893]
2.
The IMA Service continually experienced a fatal error.This occurred because
the program did not check the return status of one Win32 API and allocated a
zero length buffer when the Win32 API returned an error message. Because the
system did not allocate memory space for a zero length
buffer and returned a random memory pointer instead, subsequent freeing of
the buffer caused the fatal error.
A modification has been introduced that will check the return status of the
Win32 API call. The program does not allcoate the memory buffer if the Win32
API returns a failure message and the IMA Service works correctly.
[From Hotfix XE103W2K008][#62757]
3.
When a user with a UPN name longer than 20 characters established an ICA
session through NFuse and an administrator attempted to view the session
infomation for that user, the following error message appeared:
?Session information is not available for this session. User information
will be refreshed. Error Code 520.?
This occurred because the UPN name was being incorrectly saved in the
MetaFrame data collector.
This fix ensures that the UPN name is correctly stored in the data
collector.
[From Hotfix XE103W2K008][#63001]
4.
Caution! This fix requires 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.
In the Citrix Management Console, even when use of a published application
was limited to one, simultaneous logons could cause more than one instance
of the published application to be launched.
To resolve this behavior, navigate to the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\IMA
Add the following DWORD value:
AppInstanceLimitDoubleCheck = 1
[From Hotfix XE103W2K008][#60370]
5.
The IMA Service failed to start because of license group corruption in the
data store.
Note: This fix prevents corruption in the data store but it does not correct
any corruption that may already exist. You need to check for corruptions
present in the data store and correct them using the appropriate tools.
[From Hotfix XE103W2K025][#66583]
6.
Users on a MetaFrame server with Citrix Feature Release 3 installed could
not shadow sessions on a MetaFrame server with Feature Release 2 installed.
A problem was found in the way the IMA Service in Feature Release 3 queried
the Feature Release 2 server for its ICA port number, which is needed to
make the shadowing connection.
The IMA Service in Feature Release 3 now correctly reads the ICA port number
from a server with Feature Release 2 installed.
[From Hotfix XE103W2K036][#66021]
7.
There was excessive data store polling from the data collector in an Oracle
farm. The data collector constantly searched the data store for records with
a matching host ID.
The data store polling is now performed by the LHC instead of the data
collector.
[From Hotfix XE103W2K064][#68510]
8.
WAN/LAN traffic increased when running servers in mixed mode. In mixed
mode, winstation events trigger a large number of license- and
server-related database queries.
This function is now performed by the LHC.
[From Hotfix XE103W2K064][#74934]
9.
Limit Concurrent Logon Sessions did not work as expected. With seamless
session sharing invoked, if a user exceeded a number of applications, an
error message appeared.
This occurred because session sharing was not counting multiple applications
as one connection.
This hotfix resolves the problem.
[From Hotfix XE103W2K064][#76593]
10.
Reconnecting to a disconnected session did not work when applications were
limited to one instance per user. For example, there was an active session
to application A (hosted only on server A) and a disconnected session to
application B (hosted only on server B). If a user tried to connect to
application B, the request to launch the application as sent to server A
because of session sharing. The IMA Service on server A checked for
disconnected sessions and application limits. Even though the session on
server B was disconnected, the request was rejected because there was a
session on server B and the application limit was set to one instance per
user.
This hotfix ensures that the IMA Service on server A will first check if the
application is hosted on that server or not. If the IMA Service returns a
message to the client that the application is not hosted on server A, the
client will contact server B and connect to the disconnected session.
Reconnecting to a disconnected session now works as expected when
appl.ications are limited to one instance per user.
[From Hotfix XE103W2K075][#79433]
11.
Important: For this fix to work, you must install Citrix Hotfix XE103W2K037
or its equivalent in conjunction with this hotfix..
When Novell Directory Services (NDS) users reconnected to a farm from a
disconnected session, they were not always reconnected to a disconnected
session. This occurred because the IMA Service did not save the disconnected
session state without first converting credentials to uppercase, causing
subsequent queries to be case-sensitive. For example, if a user logged on as
mike, disconnected, and later logged back on as Mike, the search for a
disconnected session failed, causing a new session to be created.
This hotfix ensures that the fully qualified domain credentials are
converted to uppercase prior to saving the session record after a
disconnect. When a query for a disconnected session is made, the fully
qualified domain credentials are converted to uppercase. This avoids
case-sensitivity for user credentials for NDS users. The change also adds
the NDS tree to the search string when a user logs on.
NDS users can now reconnect to the disconnected session in the farm.
[From Hotfix XE103W2K119][#83453]
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 /I XE103W2K119.MSI /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
Hotfix.exe
74,000
04/28/2003
01:55p
MfSrvSs.dll
393,624
05/10/2004
03:22p
ImaLicSs.dll
246,168
05/04/2004
03:48p
********************************************************
This Week's Sponsor - Tarantella Secure Global Desktop
Tarantella Secure Global Desktop Terminal Server Edition
Free Terminal Service Edition software with 2 years maintenance.
http://www.tarantella.com/ttba
**********************************************************
Useful Thin Client Computing Links are available at:
http://thin.net/links.cfm
***********************************************************
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
http://thin.net/citrixlist.cfm
Other related posts:
- » [THIN] CTX104121 - Hotfix XE103W2K119 - For MetaFrame XP 1.0 for Windows 2000 Server
