[THIN] Re: KB: CTX103692 - Hotfix XE103W2K089 -ForMetaFrame XP for Windows 2000 Server - English
- From: "Jay Moock" <jmoock@xxxxxxxxxxxxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Thu, 8 Apr 2004 17:10:42 -0400
It is my understanding that if 056 replaced any previous hotfixes then those
would also be listed on 089's list.
I don't have 056 so I can't say for sure, but I do have 041 and here's what
it replaced:
XE103W2K004, XE103W2K011, XE103W2K022, XE103W2K030, XE103W2K039
All of those are reflected in 089:
XE103W2K004, XE103W2K011, XE103W2K022, XE103W2K030, XE103W2K039,
XE103W2K041, XE103W2K049, XE103W2K053, XE103W2K056, XE103W2K062, XE103W2K079
Sure it may take a little work to figure out what you need, but the
information is definitely available. I suppose the reason that they don't
post a roll-up package is because that is what the SP's are for.
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On
Behalf Of Shonk, Joe - Perot
Sent: Thursday, April 08, 2004 4:58 PM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] Re: KB: CTX103692 - Hotfix XE103W2K089 -ForMetaFrame XP
for Windows 2000 Server - English
And how are we suppose to know that 016 didn't get rolled up in another
hotfix.
In order to find out what the CURRENT list of hotfixes you have to enumerate
and remediate ALL of hotfixes from the beginning. Sure 056 is include in
089, but what hotfixes did 056 replace? (if any)
Joe
-----Original Message-----
From: Jay Moock [mailto:jmoock@xxxxxxxxxxxxxxxxxxxxxx]
Sent: Thursday, April 08, 2004 12:26 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: KB: CTX103692 - Hotfix XE103W2K089 - ForMetaFrame XP
for Windows 2000 Server - English
They always say right at the top of the page which hotfixes they replace.
Clearly XE103W2K016 is not in the list so what are you complaining about?
------------
Hotfix readme name: XE103W2K089.HTM
Hotfix package name: XE103W2K089.MSI
For: MetaFrame XP 1.0 with Service Pack 3 for Windows 2000
Replaces:
XE103W2K004, XE103W2K011, XE103W2K022, XE103W2K030, XE103W2K039,
XE103W2K041, XE103W2K049, XE103W2K053, XE103W2K056, XE103W2K062, XE103W2K079
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On
Behalf Of Shonk, Joe - Perot
Sent: Thursday, April 08, 2004 12:49 PM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] Re: KB: CTX103692 - Hotfix XE103W2K089 - ForMetaFrame XP
for Windows 2000 Server - English
It does not appear to have the required XE103W2K016 printing patch.
I wish Citrix would manage their patches better. Either roll them all up
every so often or have a list of recommend hotfixes. You have to guess
which ones you need and which one are included/rolled up into another one.
Joe
-----Original Message-----
From: Steve Greenberg [mailto:steveg@xxxxxxxxxxxxxx]
Sent: Thursday, April 08, 2004 9:42 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: KB: CTX103692 - Hotfix XE103W2K089 - For MetaFrame
XP for Windows 2000 Server - English
Does anyone know if this a complete "roll up"?
Steve Greenberg
Thin Client Computing
34522 N. Scottsdale Rd. suite D8453
Scottsdale, AZ 85262
(602) 432-8649
(602) 296-0411 fax=20
steveg@xxxxxxxxxxxxxx
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On =
Behalf
Of Jim Kenzig http://thin.net
Sent: Thursday, April 08, 2004 4:12 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] KB: CTX103692 - Hotfix XE103W2K089 - For MetaFrame XP =
for
Windows 2000 Server - English=20
CTX103692 - Hotfix XE103W2K089 - For MetaFrame XP for Windows 2000 =
Server -
English
This document was published at:
http://support.citrix.com/kb/entry.jspa?externalID=3DCTX103692
Document ID: CTX103692, Created on: Mar 30, 2004, Updated: Mar 30, 2004
Products: Citrix MetaFrame XP 1.0 for Microsoft Windows 2000
Attachment: XE103W2K089.msi (548.0 K)
http://support.citrix.com/servlet/KbServlet/download/4032-102-10903/XE103=
W2K
089.msi
Hotfix readme name: XE103W2K089.HTM
Hotfix package name: XE103W2K089.MSI
For: MetaFrame XP 1.0 with Service Pack 3 for Windows 2000
Replaces:
XE103W2K004, XE103W2K011, XE103W2K022, XE103W2K030, XE103W2K039,
XE103W2K041, XE103W2K049, XE103W2K053, XE103W2K056, XE103W2K062, =
XE103W2K079
Date: March, 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/.
Issue(s) Resolved in this Hotfix
Caution! Several fixes 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.
Note: This line item was fixed in non-English versions of Feature =
Release 3
with Service Pack 3.
When a modal dialog box was created from an IME pad soon after it was
created in a seamless session, the Windows operating system client =
sometimes
stopped responding.
In seamless logic, the set owner of the IME pad window was intentionally =
set
to the foreground. When the accessibility hook was disabled, the =
seamless
engine could create a situation where its enumeration routine picked the
modal dialog box from the IME pad window as the parent of the IME pad
window. This created a situation where the seamless engine caused both
windows to see each other as the parent.
Now the foreground window, which is set as the parent, is not mistaken =
as
the child of the enumerated window. If it is the child, the engine will =
not
associate the window with the parent. The Windows operating system =
client
does not stop responding.
[From Hotfix XE102W2K004][#50843]
2.
Note: This line item was fixed in non-English versions of Feature =
Release 3
with Service Pack 3.
Using the Management Console for MetaFrame to configure "use universal
driver only" or "use universal driver only if native driver is =
unavailable"
to auto-create client printers, the scaling field sometimes did not =
display
properly when running Excel in an ICA session. This occurred under the
following scenario:
A.
Create a new Excel document.
B.
Type a from A1 to A37 in the Excel work sheet.
C.
Open Print Preview in Excel.
D.
Click Setup.
E.
Change the orientation from Portrait to Landscape.
F.
Change the scaling from Adjust to to Fit to.
G.
Close the Print Setup window.
H.
Click Setup again.
Note that the percentage in the Adjust to field sometimes appears to be
changed.
If Excel.exe was launched from the console and the scenario above was
repeated, the percentage of scaling in the Adjust to field did not =
change
when the server default printer was the HP LaserJet Series II printer.
The DEVMODE set for autocreated client printers may not have been valid.
This could cause the scaling fields to be interpreted incorrectly by the
print driver.
This fix ensures the DEVMODES for autocreated client printers are valid
before setting them. The scaling fields in Excel launched in an ICA =
session
display correctly.
[From Hotfix XE102W2K004][#51176]
3.
Note: This line item was fixed in non-English versions of Feature =
Release 3
with Service Pack 3.
The Connect Client Printers policy did not work consistently. The code =
was
looking at an incorrect return value and ignored the correct value.
The Connect Client Printers policy was changed so that it looks at the
correct value and the policy now works consistently.
[From Hotfix XE102W2K004][#52158]
4.
Note: This line item was fixed in non-English versions of Feature =
Release 3
with Service Pack 3.
16-bit Windows applications launched as published applications
intermittently failed to launch.
With some 16-bit applications, timing became an issue when determining =
if a
process was actually running because these applications run as "tasks" =
under
Ntvdm.exe.
The timing in the functionality that checks for these "tasks" under
Ntvdm.exe was modified to verify when is a process is running. 16-bit
Windows applications now launch properly as published applications.
[From Hotfix XE102W2K004][#54663]
5.
Note: This line item was fixed in non-English versions of Feature =
Release 3
with Service Pack 3.
Closing nested popup menus in a seamless session sometimes caused an
application to lose focus when the seamless session was displayed on a
Windows NT 4.0-based system.
Menus that are created as a regular window using the CreateWindow API =
did
not always adhere to top level window changes correctly.
A new seamless Exception Global Flag has been introduced that provides =
the
ability to prevent the creation of top level windows in a seamless =
session.
To set this flag, create the following registry value:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI
Key name: SeamlessFlags
Type: REG_DWORD
Value: 0x1000
Closing nested popup menus in a seamless session no longer causes an
application to lose focus.
[From Hotfix XE103W2K004][#56912]
6.
Note: This line item was fixed in non-English versions of Feature =
Release 3
with Service Pack 3.
When ATOK IME Version 16 is installed on a MetaFrame server and a user
attempts to use it in an ICA session, the session may not logoff even =
after
all the published application are closed.
ATOK Version 16 introduced new processes to host IME windows. Those
processes were left in the session and MetaFrame regarded them as user
processes.
With this fix, those processes are regarded as system processes. =
MetaFrame
logs off the session if only those system processes are present.
The ICA session is logged off if all the published applications in the
session are closed.
[From Hotfix XE103W2K004][#61232]
7.
Additional output trays on client printers were not being saved and
restored on subsequent logons. This affected certain Lexmark-developed
printer drivers among others.
This occurred because printer driver data registry keys greater than 2KB =
in
length were not being read and could not be saved or restored.
This fix ensures that printer driver data registry keys up to 16KB are =
saved
and restored.
Some device-specific properties that were reset with each logon; for
example, output expander setups, are saved and restored on subsequent
logons.
[From Hotfix XE103W2K004][#62041]
8.
When using the shadow taskbar, the server occasionally experienced a =
fatal
system error.
This occurred because wsxica was calling a function in TermService but =
it
was not checking whether or not the returned value was an error. This =
caused
an access violation error.
With this hotfix, the function now checks to determine if the returned =
value
is an error or not.
[From Hotfix XE103W2K004][#62319]
9.
Note: This line item was fixed in non-English versions of Feature =
Release 3
with Service Pack 3.
After exiting a published application in an ICA session, the session did =
not
close on a MetaFrame/Windows 2003 Server if the Windows Product =
Activation
process (Wpabaln.exe) was running. The ICA session was not closed if any
applications other than the system applications that were registered =
with
MetaFrame were running.
To resolve this problem, Wpabaln.exe was registered to the MetaFrame =
system
process list. The ICA session now closes even if the Windows Product
Activation process is running.
[From Hotfix XE103W2K004][#62617]
10.
Some client printer properties were not being saved and restored on
subsequent logons. This affected certain Lexmark-developed printer =
drivers
among others.
This occurred because printer driver data registry keys greater than 2KB =
in
length were not being read and could not be saved or restored.
This fix ensures that printer driver data registry keys up to 16KB are =
saved
and restored.
Some device-specific properties that were reset with each logon; for
example, output expander setups, are saved and restored on subsequent
logons.
[From Hotfix XE103W2K004][#62625]
11.
Changing a password when logging on to a seamless session launched two
instances of the same published application.
This problem occurred as a result of the functionality in the seamless
engine that determines whether or not applications are launched.
With this update, only one instance of an application is launched if a
password is changed during logon to a seamless session.
[From Hotfix XE103W2K004][#63595]
12.
When published seamlessly, text-based telnet application flickered =
after
upgrading to or installing Citrix' Feature Release 3.
This occurred because new logic introduced with Feature Release 3 caused =
the
client to treat certain windows of an application differently from the =
way
the server was treating them.
With this fix, the server sends the correct information to the client.
[From Hotfix XE103W2K004][#65105]
13.
When running an application in a seamless session, a problem sometimes
occurred when the application changed its large icon using WM_SETICON. =
The
operating system failed to change the associated small icon. This hotfix
introduces a new per-window exception flag
(TYPE_TWI_NO_SMALLICON_FROMWINCLASS 0X200) that can be set to direct the
seamless engine to not request the small icon associated with the =
specified
window class. The addition of a registry key specifies the window class =
name
Navigate to the following registry keys:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI
Name: ClassName
Type: REG_SZ
Data: <Name of the window class>
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI
Name: Type
Type: REG_DWORD
Data: 200 (hex)
[From Hotfix XE103W2K011][#63960]
14.
Outlook.exe's parameters were used by the client when launching
OutlookExpress as a published application if client-to-server content
redirection was enabled. This occurred because the default setting was =
to
use Outlook.exe's parameters for mailto requests.
This hotfix adds functionality to better handle mailto requests from the
client. Based on the mailer application to be launched, the appropriate
mailto parameters are selected from the registry to format the launch
string.
[From Hotfix XE103W2K022][#53537]
15.
When a session was reset because of an ICA connection time-out or =
logged
off from the Management Console, the client autocreated printer =
properties
were saved in the incorrect registry key. As a result, MetaFrame could =
not
get the current user security ID from the winstation query. With this
hotfix, the client autocreated printer properties are saved in the =
correct
registry key.
[From Hotfix XE103W2K030][#65428]
16.
If a starting program was specified under the Environment tab in User
Account Properties and if the ICA pass-through Client had pass through
authentication enabled, Ssonsvr.exe was running in the user's ICA =
session.
When the user exited the application (specified under the Environment =
tab in
User Account Properties), the ICA session could not be logged off; the
administrator had to manually stop the Ssonsvr.exe process. The thread =
that
caused the Ssonsvr.exe process to exit when the user logged off from the
application was not being started.
Now The thread that causes the Ssonsvr.exe process to exit is started =
when
the user logs off from the application.
[From Hotfix XE103W2K030][#66092]
17.
In an operation running 24x7, license warning error messages caused a
flurry of help desk calls and emails. Management was also alerted. User
wanted to disable regular notification or an option to control who saw =
the
error messages.
To avoid the error messages from being sent to everyone, you need to =
make
the following change to the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix
Type: DWORD
Value: AnnoyAdminsOnly=3D1
With the value set to 1, only administrators receive the license warning
error messages.
[From Hotfix XE103W2K030][#66608]
18.
A Java application experienced a fatal error when running as a =
published
application or the initial application. The size of the buffer for the
window class name was incorrect; the error occurred if the application
window exceeded 64 characters.
This behavior has been corrected.
[From Hotfix XE103W2K030][#67014]
19.
Windows 2000 Server with Service Pack 3 or Service Pack 4:
By selecting Logoff from the ICA Connection Center, a user was able to =
log
off another user's seamless, locked session without being prompted for a
password. The unauthenticated user also had access to the locked session
while the logoff script was running.
This behavior has been corrected.
[From Hotfix XE103W2K030][#67296]
20.
Logon names prefaced with a pound sign or hash mark (#) followed by a
decimal value equal to or greater than 49152 sometimes caused a memory =
leak.
For example, the logon name #99999 would cause the memory leak.
This hotfix corrects that behavior; user logon names prefaced with a =
pound
sign or hash mark (#) followed by a decimal value equal to or greater =
than
49152 can be used without causing a memory leak.
[From Hotfix XE103W2K039][#66490]
21.
Note: For this fix to work correctly, you need Version 7.100 or later =
of
the Win32 ICA Client.
Instant Messenger type programs commonly use the FlashWindow() API to =
flash
the taskbar button to alert users of incoming messages. Prior to this, =
this
functionality was not available when running a seamless session.
This fix adds support for this API when running a seamless session. The
taskbar button now flashes to alert users of incoming messages.
[From Hotfix XE103W2K041][#69369]
22.
In Windows Server 2000, client printers could not be autocreated =
without
installing a Citrix Feature Release 3 license.
Terminal services in Windows Server 2000 were changed so that the =
printer
virtual channel needed to be created in the system context. The =
MetaFrame
server would not issue a printer autocreation command through the =
printer
virtual channel.
This hotfix ensures that the printer virtual channel is created in the
system context and a Feature Release 3 license is no longer required.
[From Hotfix XE103W2K049][#63348]
23.
An ICA session sometimes failed to delete autocreated printers when a =
user
logged off from the session soon after logging on. The thread to delete
printers finished its task before the thread to create them finish its =
task,
causing some printers to be left in the session.
With this hotfix, the thread to delete printers waits for the thread to
create printers to finish its task All printers in the session are =
always
deleted correctly.
[From Hotfix XE103W2K049][#69638]
24.
When a user disconnected from a session, then later reconnected to it =
from
a different workstation that had a different printer, the new printer =
was
not autocreated and the session had the printer from the first =
connection.
A race condition was discovered where the previous client name was sent
instead of the new one. This hotfix corrects that race condition.
[From Hotfix XE103W2K053][#68279]
25.
Sometimes a published application was launched more than once in the =
same
session in the following scenario:
.
The published application was configured with Allow only one instance of =
the
application for each user in the Management Console
.
The user rapidly clicked the published application icon in the Program
Neighborhood Client
.
The published application was to run seamlessly
This occurred because the program was not enforcing an application =
instance
limit check while launching a published application. This hotfix =
corrects
the problem and only one instance of the published application is =
launched.
[From Hotfix XE103W2K053][#71801]
26.
An access violation occurred in Wsxica.dll. This occurred because
winstations were not being enumerated properly.
The winstations are now being enumerated properly and the access =
violation
no longer occurs.
[From Hotfix XE103W2K053]]#72688]
27.
If a published application was a program that created a new process and
then terminated itself, the published application appeared in the =
Management
Console for MetaFrame XP. However, in a seamless session the application =
was
launched through session sharing, the application appeared in the =
Management
Console but then disappeared.
By default, the thread that checks the process cares about only the =
first
instance of the launched process. The thread regarded the published
application as terminated when the first instance of the process was
terminated even if that process created a separate process.
This fix provides a way to configure those published applications to use =
the
JOB object so that additional processes created by the initial process =
********************************************************
This Week's Sponsor - RTO Software / TScale
What's keeping you from getting more from your terminal servers? Did you
know, in most cases, CPU Utilization IS NOT the single biggest
constraint to scaling up?! Get this free white paper to understand the
real constraints & how to overcome them. SAVE MONEY by scaling-up rather
than buying more servers.
http://www.rtosoft.com/Enter.asp?ID=147
**********************************************************
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:
