[THIN] KB: CTX104136 - Hotfix XE103W2K117 - For MetaFrame XP 1.0 for Windows 2000 Server - English
- From: "Jim Kenzig http://thin.net" <jimkenz@xxxxxxxxxxxxxx>
- To: thin@xxxxxxxxxxxxx
- Date: Wed, 26 May 2004 08:14:28 -0400
CTX104136 - Hotfix XE103W2K117 - For MetaFrame XP 1.0 for Windows 2000
Server - English
This document was published at:
http://support.citrix.com/kb/entry.jspa?externalID=CTX104136
Document ID: CTX104136, Created on: May 21, 2004, Updated: May 21, 2004
Products: Citrix MetaFrame XP 1.0 for Microsoft Windows 2000
Attachment: XE103W2K117.msi (343.5 K)
Hotfix readme name: XE103W2K117.HTM
Hotfix package name: XE103W2K117.MSI
For: MetaFrame XP 1.0 with Service Pack 3 for Windows 2000
Replaces: XE103W2K005, XE103W2K021, XE103W2K031, XE103W2K087
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 Acrobat Reader
4 or above. You can download Acrobat Reader for free from the Adobe Web site
at http://www.adobe.com/.
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.
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.
If users updated their passwords during Citrix Program Neighborhood
Application Set Refresh, the session went into an infinite wait state. This
occurred if users typed their user name and/or domain name in a different
case (lower or upper) that did not match the operating system's saved
case. The function of Program Neighborhood that compares these credentials
was case-sensitive.
The compare function was changed to case-insensitive and the session no
longer goes into a wait state when users change their credentials.
[From Hotfix XE103W2K005][#59358]
2.
Connections became indefinitely stuck in the Connection Query (ConnQ) state
if users did not enter user credentials while refreshing application sets
through the Program Neighborhood Client. A partial connection in this state
consumes one of the server's idle ICA sessions.
When ConnQ sessions begin to collect on a server, the Program Neighborhood
service eventually stops responding. If the server that collects ConnQ
sessions also has the lowest load, users cannot communicate with
applications and the entire server farm can become inaccessible.
You can solve this problem by creating a time-out for connections stuck in a
ConnQ state. This time-out is equal to a Cancel command from the Program
Neighborhood authentication window.
Follow the steps below to create a time-out for connections in a ConnQ
state.
A.
Open the Registry Editor and navigate to the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix
B.
From the Edit menu, select Add Value and enter the following:
Value Name: PNAuthenticationTimeout
Data Type: REG_DWORD
Data: <number of minutes>
Notes: The time-out value affects users who refresh application sets.
Because users have to enter their credentials in the Program Neighborhood
dialog box, setting the time-out value too short (such as one minute) may
not be convenient for certain users if their credentials are difficult to
enter.
You need to restart the IMA Service each time you change the registry value
for the new value to take effect.
The Program Neighborhood application set refresh can be done on any
MetaFrame server, even those servers that do not have published
applications. If this fix is not deployed on specific MetaFrame servers in a
farm, those servers might still have sessions stuck in the ConnQ state even
if this fix is deployed on other servers in the farm.
[From Hotfix XE103W2K005][#60162]
3.
Connections became indefinitely stuck in the Connection Query (ConnQ) state
if users did not enter their user credentials while refreshing an
application set through the Program Neighborhood Client. This occurred when
MetaFrame XP was running in interoperability mode.
To eliminate this behavior, perform the following steps:
A.
Open the Registry Editor and navigate to the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix
B.
From the Edit menu, select Add Value and enter the following:
Value Name: PNAuthenticationTimeout
Data Type: REG_DWORD
Data: number of minutes
Notes:
A.
This hotfix must be installed on every server to avoid having connections
stuck in the ConnQ state.
B.
If users cannot enter their credentials within the time-out interval, the
connection is lost and users must refresh the application set again. Ensure
you do not set the time-out interval for too short a period of time.
C.
Each time the registry value is changed, you must restart the Program
Neighborhood service for the change to take effect.
D.
You can refresh the application set from any MetaFrame server, even those
that do not have any published applications.
[From Hotfix XE103W2K021][#65747]
4.
The IMA Service trapped intermittently. The Program Neighborhood subsystem
corrupted the heap when terminal service connection licenses were depleted.
A buffer allocated for asynchronous read was deleted before the asynchronous
read operation was canceled. This caused a write on a released memory that
corrupted the heap.
This fix cancels the asynchronous operation before deleting the buffer.
[From Hotfix XE103W2K031][#64189]
5.
ICA sessions experienced fatal errors when users tried to change their
passwords. This problem occurred when User must change password at next
logon was selected, the users were part of Active Directory, and they tried
to log on to an application set using the Program Neighborhood client with a
blank domain name.
This fix resolves the problem.
[From Hotfix XE103W2K087][#80466]
6.
Sessions became unresponsive when users who belonged to an NDS domain tried
to change their passwords. The problem occurred when the user options in NDS
were set to User must change password at next logon and the users tried to
log on to an application set through Program Neighborhood using their NDS
credentials.
Program Neighborhood launches a session so that users can change their
passwords. While creating this session, the code verifies if the domain name
sent the Program Neighborhood virtual channel is the same as the one
obtained from the logged on user token. The problem occurred because we were
not checking the NDS user name and context.
This fix ensures that NDS credentials will be verified.
[From Hotfix XE103W2K117][#84862]
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 XE103W2K117.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
MfPnSs.dll
143,768
04/27/2004
02:16p
Pnsvc.exe
90,384
04/27/2004
02:16p
********************************************************
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] KB: CTX104136 - Hotfix XE103W2K117 - For MetaFrame XP 1.0 for Windows 2000 Server - English
