[THIN] KB: CTX104982 - Readme - Service Pack 4 for Metaframe XP 1.0
- From: "Jim Kenzig Kenzig.com" <jkenzig@xxxxxxxxx>
- To: thin@xxxxxxxxxxxxx
- Date: Tue, 21 Dec 2004 05:12:11 -0800 (PST)
CTX104982 - Readme - Service Pack 4 for Metaframe XP 1.0
This document was published at:
http://support.citrix.com/kb/entry.jspa?externalID=CTX104982
Document ID: CTX104982, Created on: Dec 20, 2004, Updated: Dec 20, 2004
Products: Citrix MetaFrame XP 1.0 for Microsoft Windows 2003, Citrix
MetaFrame XP 1.0 for Microsoft Windows 2000
Readme file name: MF_XP_FR3_SP4_en.htm
For: MetaFrame XP for Windows
Date: December, 2004
Language supported: English (US)
Readme Version 1.0
Welcome to Feature Release 3, Service Pack 4 for MetaFrame XP for Windows
2000 Server and Windows Server 2003. Service Pack 4 provides fixes for
known issues in MetaFrame XP Service Pack 3. This document includes the
following sections:
Prerequisites
Known Issues
Issues Resolved in Service Pack 4
Windows 2000 and 2003
Windows 2003
Installation Instructions
Uninstallation Instructions
Note: This service pack can be applied only to a Windows 2000 Server or
Windows Server 2003 with MetaFrame XP Version 1.0 with Feature Release 3
installed.
Prerequisites
Before installing Service Pack 4 for MetaFrame XP, ensure the following
components are installed:
? MetaFrame XP Feature Release 3/Service Pack 3
? Windows Installer 3.0, Microsoft knowledgebase article
http://support.microsoft.com/?kbid=884016
Known Issues
? Installation of this service pack does not update the pass-through
client, the ICA Web Clients, or the auto client update database.
o For ICA Web Client updates, see Citrix knowledgebase article
http://support.citrix.com/kb/entry.jspa?externalID=CTX104546
o To update the pass-through client, follow the installation instructions
for the latest version of the client
o To update the auto client update database, see the Client for 32-bit
Windows Administrator?s Guide, Citrix knowledgebase article
http://support.citrix.com/kb/entry.jspa?externalID=CTX103754
Caution! Several fixes in this service pack require you to edit the
registry. Using Registry Editor incorrectly can cause serious problems
that may necessitate reinstalling 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. Make sure you
back up the registry before you edit it.
? When upgrading from MetaFrame XP 1.0 Feature Release 1/Service Pack 1 to
MetaFrame XP Feature Release 2/Service Pack 2 to MetaFrame XP 1.0 Feature
Release 3/Service Pack 3 to MetaFrame XP 1.0 Service Pack 4 to MetaFrame
Presentation Server 3.0, the upgrade may fail. To resolve the issue,
change the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix
Name: ICAProductMinorVersion
Old Value
Data: Service Pack 4
New Value
Data: Service Pack 3
? Uninstalling Service Pack 4 using Citrix Installation Manager is not
supported.
? When uninstalling Service Pack 4, the Service Pack 3 media is required
to complete the uninstallation. The media can reside on either a network
share or the Feature Release 3/Service Pack 3 installation CD-ROM.
? When installing Service Pack 4, all fixes included in Feature Release
3/Service Pack 3 are uninstalled. If you subsequently uninstall Service
Pack 4, the Service Pack 3 fixes are not reinstated automatically. When
you uninstall Service Pack 4, a message appears telling you what fixes
were installed with Service Pack 3. In addition to the message, a log file
is generated in the information in your %temp% directory, which in most
cases is C:\Documents and Settings\User Name\Local Settings\temp
directory.
? If either Hotfix XE103W2K3039 or XE103W2K125 is installed on Feature
Release 3/Service Pack 3 servers, uninstall the hotfix before installing
Service Pack 4. There is an issue with these hotfixes whereby other
hotfixes may not uninstall properly during the installation of Service
Pack 4.
? If either Hotfix XE103W2K3043 or XE103W2K129 is installed, the problem
described in issue 87999 may occur when Service Pack 4 is installed. This
issue will be resolved in a post Service Pack 4 hotfix.
Issues Resolved in Service Pack 4
Windows 2000 and 2003
The following issues apply to both the Windows 2000 and Windows 2003
operating platforms.
1. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
Running an application whose associated small icon (that appears in the
task bar) frequently changed in a seamless session caused the session to
reject the icon changes. This occurred because GDI objects that were being
used were not being deleted.
This fix adds new logic to prevent the GDI handle leaks from occurring.
Applications that frequently change their small icons now work correctly
in a seamless session.
[#45336]
2. Malicious programmers could cause an access violation or execute their
own code by exploiting a buffer overrun. The original fix to this problem
caused an additional issue: a Java Client could not connect to the
MetaFrame server. This fix resolves the issue.
[#49076, #54892]
3. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
When a modal dialog box was created from an IME pad soon after the pad 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.
[#50843]
4. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
Using the Management Console for MetaFrame to configure use universal
driver only or use universal driver only if native driver is unavailable
to autocreate 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 on 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.
[#51176]
5. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
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.
[#51893]
6. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
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.
[#52158]
7. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
When using SQL as the database for the IMA Service, the IMA Service
sometimes experienced a fatal error because it could not handle memory
allocation failures in performing SQL database searches.
This fix ensures that memory allocation failures are handled when the IMA
Service performs SQL database searches.
[#52175]
8. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
Users could not run a custom application in an ICA session. While
initializing in the session, the application loaded a Citrix module. This
module was using a ?C? runtime library API but when this API was called,
the run-time library was not fully initialized. The application failed
with a 0x00000005 error and the following error message appeared:
?R6016 - not enough space for thread data.?
The module has been changed to use non-?C? runtime library APIs and the
custom application runs without a problem in an ICA session.
[#52273]
9. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
The IMA Service experienced a fatal error during startup. An entry in a
table could be deleted without being removed from the table first. This
corrupted the table and invalid memory was later accessed.
This fix ensures that the entry is removed from the table first before
freeing the entry. The IMA Service no longer experiences a fatal error
during startup.
[#52433]
10. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
A SQL query failed sometimes. In the SQL driver, a variable needed to be
reinitialized before the SQL query was made. Inside the query, the
variable was not ended correctly with the null character, thus the query
failed.
The variable is now reinitialized before the SQL query is made.
[#53482]
11. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
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 fix 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.
[#53537]
12. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
The IMA Service on data collectors experienced a fatal error if there were
multiple zones in a MetaFrame farm. The data collector expected zone names
to be case-sensitive and rejected messages from other zones if the source
zone name inside the message did not match what was stored in the data
collector.
This fix ensures that the data collectors no longer treat zone names as
case-sensitive.
Important: You need to install this fix on every server in the farm to
prevent the IMA Service on data collectors from experiencing a fatal
error.
[#53869]
13. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
The IMA Service could experience a fatal error while using Installation
Manager to install packages on a server when there were active sessions on
the server at the time of package installation. This occurred because the
program used an incorrect format string in the swprintf function.
This fix ensures that the correct format string is used for the swprintf
function and the IMA Service works properly.
[#54167]
14. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
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 a process is running. 16-bit Windows
applications now launch properly as published applications.
[#54663]
15. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
Trying to map a printer driver in the Management Console where the driver
name contained double-byte characters caused the operation to fail and the
driver was not mapped correctly. This was caused by an internal string
conversion that failed for driver names containing double-byte characters.
The string conversion was changed and now it correctly converts driver
names with double-byte characters. A printer driver with double-byte
characters in its name can be mapped correctly in the Management Console.
[#54875]
16. When using packages built with InstallShield Versions 6.2.xx and
6.3.xx, the packager did not record all the actions of the package
installation.
This problem occurred because the process filter recorded only the actions
of the install and child processes. In InstallShield Versions 6.2.xx and
6.3.xx, the installation created a service IKernel.exe and used that
service to install the actual files related to the package.
To resolve the problem, you need to add the value UseIKernel to the
following registry key.
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\IMS\2.0\Packager
Type: DWORD
Value: UseIKernel = 1
With the above value set at 1, all the actions of the package installation
are recorded.
[#55007]
17. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
The times in the Load Manager Scheduling rule sometimes used 12-hour
clocks when they should have used 24-hour clocks or the reverse. The
decision to use a 12- or 24-hour clock was based on the Management
Console's language rather than on Windows regional settings.
The Load Manager Scheduling rule now employs Java functions to read
Windows regional settings to determine which kind of clock to use.
Important: If you are using the German language version of the software,
you must employ the 24-hour clock.
[#55183]
18. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
A memory leak occurred when starting the shadow taskbar (Wshadow.exe) as a
published seamless application.
This fix corrects that behavior and the shadow taskbar no longer exhibits
a memory leak.
[#55781]
19. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
If a user was a member of many groups; for example, 100, and used desktop
credential pass-through, the XML Service returned an error message similar
to the following:
?Request too large. More than 4096 bytes.?
This occurred because the buffer to hold the request was a fixed size ? it
was too restrictive for users who were members of a large number of
groups.
The default maximum request size has been increased and a new registry key
has been added that allows you to increase the maximum request size. The
new registry key is:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\XML Service
A Value Name called MaxRequestSize of type DWORD controls the maximum
request size. If the error message still appears, create the new registry
value and increase it until the error message disappears.
[#56019]
20. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
The IMA Service on the data collectors randomly experienced fatal errors.
This also occurred occasionally when opening the Management Console on the
data collectors. This occurred because the IMA buffer append exception was
thrown but not caught.
This fix ensures that the append exception is caught and the information
is written to the event log to alert administrators that a new data
collector with sufficient memory needs to be elected. Citrix suggests that
the data collector not be overloaded and that applications be published on
servers other than the data collectors.
This fix ensures that the IMA Service on the data collectors no longer
experiences fatal errors.
[#56229]
21. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
The Hide application title bar property of published applications did not
work for Windows 2000 Japanese servers. The routine of the Hide
application title bar feature was trying to set the style changes for IME
windows, not the published application?s window.
With this fix, the common windows that don?t come from the published
application are intentionally skipped during the window enumeration in the
session and the Hide application title bar property of published
applications works for Windows 2000 Japanese servers.
[#56739]
22. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
When the MetaFrame XP farm was in MetaFrame 1.8 interoperability mode and
the published application was set to have High Color mode on the server,
the properties of that application on the client side incorrectly showed
256 colors. While negotiating the capabilities with the client, the
Program Neighborhood service set up the capability data structure
incorrectly.
This fix ensures that the capability data structure is built correctly by
the Program Neighborhood service. Now when the MetaFrame XP farm is in
MetaFrame 1.8 interoperability mode and the published application is set
to High Color mode on the server, the properties of that application on
the client side correctly show High Color.
[#56823]
23. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
Even if Force Reinstall was selected on an Installation Manager package
that was previously installed, the updated package was not installed.
This fix removes the package entry from the database (if Force Reinstall
is selected); this ensures the updated package is installed.
[#56824]
24. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
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.
[#56912]
25. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
Changing permission from [View Only] to [Full Administration] for Citrix
Administrators failed and an error message appeared. This occurred if the
feature release level was lower than Feature Release 2 and the enabled
Read-Write administrator was one.
If the enabled Read-Write administrator was one, the IMA Service rejected
the request that changed the privilege of an administrator user to Full
Administration from the Management Console where the feature release level
was lower than Feature Release 2.
This fix allows the Management Console where the feature release level is
lower than Feature Release 2 to change the privilege of the administrator
to Full Administration and the privilege of Citrix Administrators can be
changed from [View Only] to [Full Administration] on the Management
Console where the feature release level is lower than Feature Release 2.
[#56951]
26. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
If the Newer option was used in a CopyFile command in the WFS file of an
Installation Manager package and the target machine was in a time zone
east of Greenwich Mean Time (GMT); that is, GMT+1, GMT+2, and so on, the
file was not always replaced.
This fix ensures that the installer program now reads the date in the WFS
file as GMT time and does not convert it to local time.
[#57108]
27. Wsxica.dll caused memory access violations during initializing ICA
sessions in the context of termsrv.
[#57308]
28. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
Servers were trapping with error code 35 in Tdasync.sys. BugCheck was 35
{bdc2ac38, 0, 0, 0}. This occurred when using the ASYNC protocol on a poor
quality link.
With this fix, the server no longer traps with error code 35 when using
Tdasync.sys.
[#57910]
29. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
After changing the domain password for the Installation Manager Version
2.2 network account, event ID 1020 was sent to the event log every two
hours until the password was changed in the Management Console and a
package was successfully installed. If the issue was not resolved quickly,
the account sometimes locked because of too many failed logon attempts.
While idle, Installation Manager attempted a logon for its network account
every two hours whether or not the cached account information changed.
With this fix, Installation Manager attempts a logon for its network
account only when the cached account information changes. No events appear
in the event log.
[#58096]
30. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
The IMA Service on data collectors experienced a fatal error when memory
ran low. In the runtime subsystem, low memory and allocation failure were
not handled correctly.
This fix ensures that allocation failure is handled correctly.
[#58099]
31. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
On a MetaFrame server, Windows Explorer could not access a computer on a
network whose name began with client. From a console or an ICA session,
Windows Explorer displayed one of the following error messages:
?Incorrect Function.?
- or -
?The server service is not started.?
When processing a redirector query path request, the CDM driver did not
check for a delimiter character beyond the CDM UNC prefix length within
the path name. Therefore, any path name beginning with client was
automatically redirected to CDM regardless of what characters existed
beyond the prefix length.
This fix verifies the character beyond the CDM prefix is NULL or a
backslash ( \ ) before allowing the path name to be redirected.
[#58131]
32. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
Diacritic dead keys and the Eurokey (in Microsoft Word) did not work
properly on Java Clients configured with a Polish (Programmers) keyboard.
The Unicode mappings were not properly defined in the MetaFrame Polish
(Programmers) keyboard (.kbd) file.
The Polish (Programmers) keyboard file now contains the correct Unicode
mappings for the diacritic dead keys.
[#58270]
33. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
In the SSL Relay Configuration wizard, if a user deleted a port number
from the destination port list on the Target Server Properties page, the
delete button remained enabled even if no items were selected from the
list. After deleting any item from the list, the delete button state was
not being evaluated to determine if it needed to be disabled.
Now after deleting an item from the list, the delete button changes to
disabled if no items are selected.
[#58450]
34. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
While installing packages, one of the Installation Manager modules caused
an access violation when it failed to inform the Management Console about
the status of the package deployment. The module needed to periodically
inform the Management Console about the status of the package deployment.
When the module failed to do so, it wrote to a file. However, if the file
was not open when the error happened, the access violation occurred.
This fix ensures that the module does not write to a file if the file is
not open and the access violation no longer occurs.
[#59034]
35. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
When changing Broadcast Response settings in farm Properties, such as RAS
servers respond to ICA Client broadcast messages, the changed settings
frequently failed to be saved. If Access was used as the database,
settings were saved properly on the data collector but not on servers that
were not data collectors. If the database was SQL or Oracle, the problem
occurred on all servers.
This problem occurred because two requests from the Management Console
caused the ICA browser to experience a race condition due to lack of
synchronization in data store access routines.
This fix introduces a new critical section object to synchronize the
access to farm settings in the data store. Changed Broadcast Response
settings in the farm Properties are saved correctly.
[#59077]
36. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
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.
[#59358]
37. Note: This item requires that you have Version 7.100 or later of the
Win32 ICA Client installed.
A seamless session changed to a fixed window when the color depth
degraded. The server was configured to degrade color depth over resolution
to preserve the seamless session. The session color depth was being
degraded, but the seamless nature was lost. When an ICA Client connected
to a seamless application, the application changed to a non-seamless
window. The session degraded the color depth but still lost the seamless
appearance. This occurred because the client had no knowledge of the
server setting that stated whether to degrade resolution or color first,
so the client always degraded the resolution.
The server is now configured to degrade color depth over resolution to
preserve the seamless session. The session color is degraded but the
application remains seamless.
Limitation: For multiple monitor configurations, even if user notification
for degrading color/resolution is enabled on the server, users will not
receive notification if the color or resolution is degraded. Users will
still receive the notifications for the single monitor configurations.
[#59431]
38. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
When using an application to write to a floppy diskette from within a
session, the server experienced a fatal system error. This was caused by a
deadlock in the client driver mapping module.
A modification was made so that the deadlock no longer occurs. Users can
write to a floppy diskette from within a session without any adverse
effects.
[#59480]
39. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
The time choosers in Installation Manager were using 12-hour clocks when
they should have been using 24-hour clocks. This occurred in reverse also.
This occurred because the choice of which clock to use was based on the
Management Console's language rather than the Windows regional settings.
This fix provides functions to read the Windows regional settings to
determine which clock to use. The time choosers in Installation Manager
will use the correct clock.
[#59630]
40. An exception occurred when an SDK call was used to remove a privilege
for a custom administrator with no privileges. This was a result of a
missing check for administrator privilege count.
With this fix, the exception no longer occurs.
[#59720]
41. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
A problem occurred when a user entered a long root build location in the
Recording wizard of Packager. The Results page of the wizard could not
display the entire path name for the root build location. This occurred
because there was insufficient space in the root build text box.
The size of the build text box was increased and the Results page of the
wizard displays the entire path name for the root build location.
[#60041]
42. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
Servers were trapping with error code 50 in Cdm.sys. Bugcheck was 50,
{a8916fce, 0, 0, 1}.
One field in the file control block structure kept in Cdm.sys did not have
memory allocated for it. Subsequent reference to this field caused the
server to experience a fatal error.
Memory allocated for the field and the server no longer traps with error
code 50 in Cdm.sys with bugcheck 50, {a8916fce, 0, 0, 1}.
[#60110]
43. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
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. 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.
For the new value to take effect, you need to restart the IMA Service each
time you change the registry value.
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.
[#60162]
44. The server occasionally experienced a fatal system error with one of
the following bugcheck codes:
0xD1 in Termdd.sys
0xD1 in Tcpip.sys
0x1E in ntos kernel
This occurred because a synchronization error in Wdica.sys could free a
buffer twice.
This fix prevents Wdica.sys from freeing the buffer twice.
[#60238]
45. Incorrect help information for the Applications tab was displayed in
the Management Console for MetaFrame.
This fix ensures that the correct help tag is selected for the
Applications tab and the Management Console displays the correct
information.
[#60257]
46. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
The Content Redirection tab of the Management Console sometimes displayed
the incorrect file types for the selected application. The file types
associated with an application were not updated properly in the data
store.
With this fix, the Content Redirection tab of the Management Console
displays the correct file types associated with the selected application.
[#60366]
47. In the 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
[#60370]
48. Ticketing functions could permit access to user passwords.
[#60373]
49. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
The Management Console submenu shortcut ?n? in the Actions pull-down menu
did not work. Keyboard events were dropped before they could be
interpreted.
This fix resolves the issue and the submenu shortcut works properly.
[#60405]
50. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
Users could not remove a load evaluator from the server farm. The error
code received was 80110107.
The problem was due to database corruption associated with removing or
uninstalling a server from a farm. The load evaluator was still showing in
the database as being used by the server even if the server had already
been uninstalled or removed from the farm.
This fix checks to ascertain whether or not servers associated with a load
evaluator still exist in the server farm. If the servers do not exist in
the farm, the load evaluator is deleted.
[#60547]
51. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
Users could not distribute packages with Installation Manager. An error
message was sent to the application event log by the Gemini Installer.
Installation Manager created package IDs randomly before installing the
package. The package ID could be as long as 12 characters if the ID wais
written in decimal format. During installation, however, package IDs with
more than seven characters were considered invalid and the package was not
installed.
This fix ensures that Installation Manager recognizes all package IDs it
creates.[#60763]
52. By default, MetaFrame attempts to find the IME file name installed in
the system with the language ID requested by the client and activates an
alternative IME file name if one is found. With Terminal Services, the
user?s input locale is loaded if the requested IME file name is not found.
By request, an optional registry flag has been introduced to use the
Terminal Service IME file name handling instead of using
MetaFrame-specific processing.
MetaFrame stops its own IME processing. To use the Terminal Service IME
processing, set the value in the following registry key to 0x1:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix
Value Name: ClientDataOption
Type: REG_DWORD
Value: 0x1
With this registry flag set, the session uses Terminal Service?s IME
processing.
[#60837]
53. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
Users printing to a local printer named ?LPT1xxx? could not access that
printer from an ICA session. This occurred because the system was not
reading any digits beyond ?LPT1.?
This fix contains a modification that checks for ?LPT1:? instead of
?LPT1.?
With this fix, users can access a local printer named ?LTP1xxx? from an
ICA session.
[#61081]
54. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
Labels in the Printing Preferences dialog box were too close to the text
boxes and were difficult to read.
This fix adds white space between the labels and the text boxes, thereby
making the labels easier to read.
[#61131]
55. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
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 log off 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.
[#61232]
56. When an administrator set Notify User for Client Download mode in the
ICA Client Update Configuration utility, the Allow Background Download
option was ignored and users had to wait until the download completed.
With this fix, when Notify User is checked, a background download is
permitted.
[#61578]
57. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
If a user?s desktop was not 256 colors but the ICA session was using 256
colors, ReflectionX software running in the ICA session did not display
device-independent (.dvi) files correctly.
ReflectionX uses SRCPAINT to draw the .dvi files in 256 color mode.
SRCPAINT works differently from a paletted device, such as a 256 color
desktop, and a non-paletted device, such as a 16- or 24-bit color desktop.
ReflectionX is not intended to use SRCPAINT to draw the .dvi files in 16-
or 24-bit color mode. If the client desktop is using something other than
256 colors, the ICA Client runs SRCPAINT. This causes the .dvi file to
display incorrectly.
This fix adds a switch to a command-line utility. When the switch is
turned on, the client desktop is a non-paletted device and the ICA session
is a paletted device. SRCPAINT is performed in the ICA session?s video
buffer instead of on the client. The ICA Client copies the content in the
ICA session?s video buffer to the client device. The client avoids
performing SRCPAINT directly on the non-paletted device.
To turn on the switch, type the following at a command prompt:
twconfig /SrvSrcPaint:on
The switch is off by default.
Caution: Turning on the switch may degrade server performance.
This fix is supported only in Thinwire 2 mode.
Device-independent files now display correctly even if the color settings
on the client device and the server are different.
[#61598]
58. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
The XML Service used in NFuse Web configuration settings was requesting
credentials from remote XML servers that were failing to respond. Users
could not enumerate or connect to published applications.
This fix implements a ticket request time-out to prevent the XML Service
from experiencing a fatal error on failed connections. If the request
times out, the request fails and an Event Message is sent to notify the
administrator. The default time-out for connection attempts is set to five
minutes (300000 milliseconds).
To modify this time-out to a lower value, you need to add the following
registry value:
HKEY_LOCAL_MACHINE\SYSTEM\Services\CtxHttp
Name: SocketTimeout
Type: REG_DWORD
Data: Time-out number value in milliseconds
[#61737]
59. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
Feature release and service pack levels for a new server in a farm were
not displayed correctly in the server node of the Management Console
(detailed view). The Management Console caches information about feature
releases and service packs. This cache was not being updated when a server
was added to the farm.
After this fix is installed, press F5 to refresh server details. Feature
release and service pack levels will be displayed correctly.
[#61750]
60. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
In the Management Console, the Bandwidth Limit column on the Bandwidth tab
of the Printer Management node sorted numbers over 1000 incorrectly. This
occurred because the column was being sorted alphabetically.
This column is now sorted numerically with ?Unlimited? being greater than
any number.
[#61992]
61. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
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.
[#62041]
62. When a new printer or printer driver was installed on a MetaFrame
server, a substantial amount of traffic (in the order of 8 to 10MB per
second) occurred between the IMA Service and the data store the IMA
Service was using. This occurred because the IMA Service needed to update
the Management Console for MetaFrame XP with the information about the new
printer or printer driver, which caused the huge amount of network
traffic.
To resolve this problem, navigate to the following registry key and change
the value of fDisablePrinterWorkerThread to 1:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\IMAPrinter
Type: REG_DWORD
Value: fDisablePrinterWorkerThread = 1
After you make this change to the registry, restart the IMA Service for
the change to take effect.
Note: When the registry switch is set to 1, the IMA Service does not
automatically update printer or printer driver information to the
Management Console. You need to update this information manually. To do
this, right-click Printer Management in the left panel of the Management
Console and then click Update Printer and Driver.
[#62158]
63. While installing a package using Installation Manager, the last line
was duplicated in some of the text files installed on the target server.
An Installation Manager module failed to detect the end of the file while
processing a text file.
The Installation Manager module now detects the end of the file correctly
while processing a text file, avoiding the duplication of the last line of
the text files on the target server.
[#62286]
64. 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 fix, the function now checks to determine whether or not the
returned value is an error.
[#62319]
65. DSEdit allowed only one item at a time to be selected for deleting.
With this fix, DSEdit allows multiple items to be selected for deletion.
[#62368]
66. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
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.
[#62625]
67. The system was experiencing a fatal error after running sustained
connections through Citrix Secure Gateway. This occurred because an
invalid timer was used when processing thinwire stop watch commands.
The validity of the timer number is now checked when processing thinwire
stop watch commands and the system no longer experiences a fatal error.
[#62629]
68. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
When shifting the priority of a large number of policies (by deleting a
policy near the top, or moving one from near the bottom to the top), CPU
usage on the Management Console went to 100% for quite a long time. A
time-out error message appeared even though the action completed
successfully. This occurred because the policy update process changed the
priorities one at a time through individual update events from the IMA
Service.
This fix improves the performance of the individual update events and
increases the event time-out value.
[#62633]
69. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
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.
This fix checks the return status of the Win32 API call. The program does
not allocate the memory buffer if the Win32 API returns a failure message
and the IMA Service works correctly.
[#62757]
70. The ICA toolbar disappeared after setting up Windows 2000 Server with
Microsoft Service Pack 3. The ICA toolbar reads the default height and
width values from the registry. After installing Service Pack 3, these
values were sometimes zero.
This fix resets the values to the default if the registry value reads
zero.
[#62913]
71. In the Management Console, when a user expanded the Servers node,
right-clicked a server name, and clicked Properties > SNMP, the user could
not select the Use farm settings check box. This was caused by mishandling
of the check box properties.
With this fix, the check box works properly.
[#62960]
72. 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.
[#63001]
73. When a conference was started, the following error message appeared:
?CITRIX CONFERENCE ROOM failed to start. The Citrix server is unable to
process your request to start this published application at this time. If
the problem persists, contact your administrator.?
This error message appeared for 10-15 seconds and then disappeared. The
conference did start successfully. The problem was caused by a race
condition.
[#63055]
74. A ticketing call could trap Termsrv.
[#63120]
75. The Citrix MetaFrame Conferencing Manager and Citrix Conference Room
published application failed to publish in the server farm while
installing Conferencing Manager 3.0 using Active Directory or Installation
Manager.
The Citrix MetaFrame Conferencing Manager and Citrix Conference Room
published application could not be removed from the server farm while
uninstalling Conferencing Manager 3.0 using Active Directory or
Installation Manager.The System account was not recognized as a valid
MetaFrame administrator; therefore, publishing and unpublishing the
Conferencing Manager and Conference Room failed while installing or
uninstalling the Conferencing Manager. This fix resolves the problem. To
enable this fix, you need to install this fix on MetaFrame XP, Feature
Release 3 before deploying Conferencing Manager using Active Directory or
Installation Manager.
[#63122]
76. If the input locale for a remote session was IME 2002, published
applications did not always open with the window title bar hidden when
Hide application title bar was checked. The windows for IME 2002 were
considered the application windows and their title bars were hidden
instead of those of the published applications.
With this fix, published applications are launched without a title bar
when Hide application title bar is checked.
[#63253]
77. The HOMEDRIVE and HOMEPATH environment variables were not available
when the logon script ran if they were configured in the Active Directory
group policy object.
The problem occurred because Winlogon.exe does not set the environment
variables if a third-party Gina dll is configured and that dll does not
implement the proper export function. This behavior occurs with any
third-party Gina dll that does not contain the export function. A new
export function was added to Ctxgina.dll that forwards the request to the
Microsoft Gina.dll correctly.
[#63523]
78. 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.
[#63595]
79. If a published application was a program that created a new process
and then terminated itself, the published application appeared in the
Management Console. However, in a seamless session, if 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
are considered as published applications.
For this fix to work properly, you need to perform the following steps:
A. If the command line of the published application is [ApplicationPath],
go to the following registry key and make changes as necessary:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI\StartInJobObject
Key Value: Application Path
Type: DWORD
Value: 0
B. For example, if the command line specified for the published
application is c:\notepad.cmd, go to the following registry key and make
changes as necessary:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI\StartInJobObject
Key Value: c:\notepad.cmd
Type: DWORD
Value: 0
For those applications whose command line is specified in the
StartInJobObject key, the published application does not disappear from
the Management Console until all of the processes created by the process
are terminated.
[#63894]
80. Printing with the Version 7.0 client slowed significantly. The Version
7.0 client uses flow control protocol for printing. The server was using
the incorrect window size for virtual channels that request flow control.
It adjusted the window size to the maximum window size for virtual
channels that wanted to use flow control.
With this fix and the Version 8.0 client, printing is faster on clients
that request flow control.
[#63903]
81. 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 fix
introduces a new per-window exception flag (TYPE_TWI_NO_SMALLICON_
FROMWINCLASS 0X200) that can be set to direct the seamless engine so it
does 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: TYPE_TWI_NO_SMALLICON_FROMWINCLASS 0X200
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI
Name: Type
Type: REG_DWORD
Data: 200 (hex)
[#63960]
82. All Microsoft Office applications failed to enumerate the Client
Network drives under My Network Places. Cdmprov.dll returned ?Client?
instead of ?\\Client? as a network resource name. However, applications
failed to obtain the resource information because they expected network
resource names to begin with the double backslash ( \\ ).
Applying this fix returns ?\\Client? when the Client Network is opened.
[#64062]
83. 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.
[#64189]
84. Users could not retrieve values from an array of application extension
properties using VBScript with MFCOM. This occurred because MFCOM returns
an array of BSTR that VBScript cannot access. The solution is to return an
array of VARIANT.
If you are using DCOM, you need to update the Mfreg.exe file as follows:
A. Run mfreg /u on the client device.
B. Replace the existing Mfreg.exe file.
C. Run mfreg servername to re-register, where servername is the name of
the MetaFrame server where this fix is installed.
You can now retrieve values from an array of application extension
properties using VBScript with MFCOM.
[#64257]
85. When using Installation Manager from the Management Console to
uninstall Conferencing Manager, the following two error messages appeared:
?Error deleting application.?
?Failed to delete the published application. Delete the application
manually from within the Management Console for MetaFrame XP.?
The error messages appear twice on the server from which you are
uninstalling Conferencing Manager. Users cannot run an ICA session on that
server until the error messages are cleared by clicking OK.
The error occurred because the uninstaller did not have sufficient
permissions to remove the Conferencing Manager and CRoom published
applications from the server farm.
This fix ensures that uninstallation is successful and the server is not
blocked by the error messages.
[#64478]
86. Launching Novell?s GroupWise Version 6.0 with local text echo enabled
caused the application to experience a fatal error when writing a new
email. This problem was caused by the function that handles sending font
information to the ICA Client.
This behavior is corrected; launching GroupWise Version 6.0 with local
text echo enabled no longer causes a fatal error when writing a new email.
[#64580]
87. When a large number of sessions (greater than 100) were logged on to
the MetaFrame server and the Web Console Session page was used to view the
sessions, the following error message appeared:
?The page cannot be found.?
If sorting was enabled when the page was displayed, the session
information did not update. The sort algorithm used was recursive,
resulting in a stack overflow associated with the Web Console session. The
information used for sorting was obtained from HTTP session variables that
were not updated when sorting was enabled.
Now when sorting is enabled, the data being viewed is fresh. If more than
100 sessions are logged on to the MetaFrame server and the Web Console is
used to view the session information, the error message no longer appears.
[#64584]
88. Version 6.3 of a Siebel application running in an ICA session did not
display the client?s time zone. Certain dynamically loaded dlls in the
Siebel application require specific configuration to display time
according to the client time zone in an ICA session. This fix provides the
specific configuration required to display the client?s time zone.
To activate the fix, add the following key to the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\CtxHook\AppInit_DLLs\siebel application
Add the following two values to this key:
Name: Flag
Type: REG_DWORD
Data: Flag=0000000e
Name: SpecialDllSearch
Type: REG_STRING
Data: SpecialDllSearch=sscfbas.dll sssbl.dll;
Add the following key to the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\CtxHook\AppInit_DLLs\siebel
application\siebel.exe
The Siebel application running in an ICA session correctly displays the
client?s time zone.
[#64722]
89. In some circumstances, Cpmmon.dll tried to reference a NULL pointer.
This caused the spooler service to experience a fatal error.
With this fix, Cpmmon.dll no longer attempts to reference a NULL pointer
and the spooler service works as expected.
[#64973]
90. When published seamlessly, text-based telnet applications flickered
after upgrading to or installing Citrix MetaFrame 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.
[#65105]
91. After installing MetaFrame XP Feature Release 3, applications failed
to run in an ICA session. This problem occurred only when Microsoft Hotfix
Q329115 was installed on the MetaFrame server and specific applications
were run in an ICA session. This failure was due to an access violation
that was raised while the Windows multimedia subsystem was loading the ICA
media driver.
This behavior is corrected with this fix.
[#65107]
92. When upgrading MetaFrame XP to Service Pack 2 or Service Pack 3,
autocreated client printers with pending print jobs could not be deleted
at session logoff even with the following registry values set:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\ClientPrinterProperties
REG_DWORD: fPurgeAnyWay=1
REG_DWORD: fNotInheritKeepPrintedJobs=1
Service Packs 2 and 3 added a Feature Release 2 license check before
deleting autocreated client printers with pending print jobs at session
logoff. If the license was not present, autocreated client printers with
pending print jobs were not being deleted.
Now the Feature Release 2 license check is removed before deleting
autocreated client printers. With the registry values set as above,
autocreated client printers with pending print jobs are deleted at session
logoff.
[#65110]
93. When installing MetaFrame English Feature Release 3 on a Windows 2000
English system in a non-English locale, errors occurred when attempting to
install performance counters. Three sets of counters were involved: ICA,
IMA, and MetaFrame XP. The Application Programming Interface (API) used to
determine the language of the Windows installation was returning incorrect
information.
Microsoft recommended that a different API be used. With this new API, the
performance counters operate properly.
[#65371]
94. When a session was reset because of an ICA connection time-out or was
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 a winstation
query.
With this fix, the client autocreated printer properties are saved in the
correct registry key.
[#65428]
95. Outlook 2000 experienced a fatal error when printing rich text
documents (.rtf) using XPrint with SpeedScreen latency reduction enabled.
This occurred as a result of a deadlock between XPrint and SpeedScreen
latency reduction.
This update resolves the problem by checking for a deadlock and
pre-empting the thread so that Outlook 2000 does not experience the error
when printing .rtf documents.
[#65674]
96. Creating a distributed file system (DFS) share caused the Installation
Manager Packager to experience an error when recording an application
installation. For monitoring file system events while installing a
package, a system file hooks to the machine drives. The problem occurred
because MetaFrame was not hooking to drives on which DFS shares were
present.
With this fix, the Packager can record an application installation on
drives on which a DFS share is present.
[#65703]
97. 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:
This service pack must be installed on every server to avoid having
connections stuck in the ConnQ state.
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.
Each time the registry value is changed, you must restart the Program
Neighborhood service for the change to take effect.
You can refresh the application set from any MetaFrame server, even those
servers that do not have any published applications.
[#65747]
98. Important! For this fix to work correctly, you need to have Version
7.100 or later of the Win32 ICA Client.
The mouse pointer disappeared in an ICA session when PrintScreen was
pressed. There was a problem with the x and y coordinates on the display
where the driver positioned the mouse pointer.
This fix corrects this behavior.
[#65815]
99. Note: This item requires that you have the Version 7.1.1532 or later
of the Java Client installed.
A terminal server client access license was being consumed when connecting
to a Windows 2000 Server with a Java Client that was running on a Windows
2000 or Windows XP desktop. This occurred because the Java Client did not
support client-based terminal server licensing.
Support is added to allow the client to send the operating system platform
information to the server. The Java Client no longer consumes a terminal
server client access license.
[#66009]
100. Users on a MetaFrame server with MetaFrame XP Feature Release 3
installed could not shadow sessions on a server with MetaFrame XP 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 now correctly reads the ICA port number from a server with
MetaFrame XP Feature Release 2 installed.
[#66021]
101. 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 and
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.
[#66092]
102. The auto client reconnect feature did not always work for Novell NDS
users. The program did not capture user credentials correctly.
This fix enables NDS users to use the auto client reconnect feature.
[#66137]
103. In the Management Console, if a subholder?s parent folder had the
same name as the farm, the subfolder could not be deleted. The Management
Console treated any parent folder whose name was the same as the farm as
the farm node and offered no choice to delete the subfolders.
With this fix, only the node whose type is FARM is treated as the farm
node. Even if a folder has the same name as the farm, the subfolders can
be deleted
[#66353]
104. 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 fix 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.
[#66490]
105. Using the Installation Manager and complex installation packages, the
package would install but the application would always be listed as
disabled. The problem dealt with a user-modified installation package
using environment variables to control the installation path. When the
correct combination of variables was used, the package would not install
properly but would report success.
Uninstall any defective packages from the servers, either before or after
applying the service pack, then reinstall the packages. The packages will
be enabled and functional.
[#66579]
106. 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.
[#66583]
107. Under some circumstances, the processing of client print jobs within
one session were unnecessarily delayed by the processing of print jobs
from another session. This occurred because the synchronization mechanism
that was being used was unnecessary.
This fix eliminates the use of the synchronization mechanism.
[#66606]
108. In an operation running 24x7, license warning error messages caused a
flurry of Help desk calls and emails. Management was also alerted. Users
wanted to disable regular notification or have 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=1
With the value set to 1, only administrators receive the license warning
error messages.
[#66608]
109. No Shell32.dll icons appeared under the following scenario:
A. In the Management Console, go to the published application Properties
page.
B. Under Program Neighborhood Settings, change the icon to point to
c:\winnt\system32\SHELL32.dll.
This occurred because one of the icons in Shell32.dll had ?non-standard?
dimensions that did not match the new icon extraction code criteria,
thereby preventing all icons from appearing.
With this fix, any icons that do not meet the icon extraction code
criteria are skipped while standard icons are allowed to pass.
[#66832]
110. If universal printer drivers were specified with the compatibility
list option Only allow drivers from this list in the Management Console,
client printers could not be autocreated with universal print drivers. The
Management Console sent the incorrect driver names to the IMA Service.
This fix ensures that the correct driver names are sent to the IMA
Service.
Note: After you apply this fix, you must remove any universal printer
drivers from Only allow drivers from this list in the Management Console
and then add them to the list again.
[#66839]
111. Administrators were permitted to access client drives. This was by
design.
This behavior is modified so that administrators do not have permission to
access client drives.
[#66856]
112. A Java application experienced a fatal error when running as a
published or 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 is corrected.
[#67014]
113. One of the commands specified in the ADF installation package script
lets the installation package add environment variables to the target
server. This command was using only three parameters when, in fact, it
required four. Therefore, when trying to install a package containing this
command, the installation failed.
The command now utilizes all four parameters and installation proceeds
normally.
[#67034]
114. Explorer.exe trapped intermittently when drive mapping was enabled
and a user opened Explorer.exe within a session. The problem occurred more
frequently on a multi-processor system. This occurred because there was no
synchronization of threads to a shared list that contained the device
mappings.
A synchronization lock was added to the device mapping list. Explorer.exe
no longer traps.
[#67072]
115. 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.
[#67296]
116. 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 fix corrects that race condition.
[#68279]
117. 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 local host cache (LHC)
instead of the data collector.
[#68510]
118. Diacritic dead keys did not work on Linux Clients configured with a
Brazilian ABNT keyboard layout. The keyboard layout file did not contain
the correct code mappings for accented characters.
The keyboard layout file for a Brazilian ABNT keyboard is corrected and
the accented character key codes map correctly.
[#68668]
119. With use universal driver only if native driver is unavailable
checked and Automatically install native drivers for autocreated client
and network printers cleared in the Management Console, client printers
were sometimes created with a universal driver even if the native driver
was available. This occurred because an incorrect criteria was being used
to determine whether or not the native driver was present.
With this fix, the correct criteria is checked and the native driver is
used, if it is available.
[#69185]
120. 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.
[#69369]
121. When using Installation Manager from the Management Console to
install package groups, the installation did not proceed in the given
sequence. This occurred under the following scenario:
A. There are two package groups.
B. Each package group includes multiple packages.
C. The system needs to be restarted after each package group is installed.
D. Both package groups are scheduled to install Now. When scheduling each
job, the Delay reboot until end of job check box is clear.
Instead of installing all packages of the package group scheduled first
before installing all packages of the package group scheduled second, the
packages were installed in the incorrect sequence. The IMA Service
assigned an incorrect starting time for installation jobs that were
scheduled to be installed Now.
This fix ensures that the IMA Service assigns a correct starting time to
installation jobs that are scheduled to be installed Now.
[#69449]
122. 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
finished its task, causing some printers to be left in the session.
With this fix, 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.
[#69638]
123. When sorting by user name on the Citrix Web Console, the session
information was not updated. The information used for sorting was obtained
from HTTP session variables that were not updated when sorting was
enabled.
This fix ensures the session variables used for sorting are updated when
sorting is enabled.
[#69707]
124. When using the Management Console installed on a MetaFrame XP Feature
Release 3/Windows 2000 Server that was connecting to a MetaFrame XP 1.0,
Service Pack 2/Terminal Services server, the following error message
appeared:
?The server you are connecting to does not have Service Pack 2 installed.
Until you install Service Pack 2, features associated with Service Pack 2
are not available when you connect to this server.?
The Management Console could not determine what level of service pack was
installed on the Terminal Services server.
This fix ensures that the erroneous error message does not appear.
[#69745]
125. The following keys did not always work within a session using
non-Windows clients:
<, > (Finnish keyboard layout)
<, > (Norwegian keyboard layout)
<, >, \ (Belgian French keyboard layout)
The Unicode conversion table was using an Alt+Numpad key sequence even
though the characters could be typed with a single keystroke.
The conversion table entries are changed so that the characters can be
typed with a single keystroke instead of using an Alt+Numpad key sequence.
[#70746]
126. Servers in a farm intermittently experienced a fatal error on
Wdica.sys with stop error 0xC2. This occurred because a thread in
Wdica.sys was attempting to free a variable that had already been freed.
This fix synchronizes access to the variables so the fatal error no longer
occurs.
[#71243]
127. Note: For this fix to work, you must install Hotfix XE102W2K081 or
replacement on your MetaFrame XP Version 1.0 Feature Release 2 server(s).
An administrator on a Feature Release 3 server could not enumerate users
on a Feature Release 2 server from the shadow taskbar. An empty list was
returned.
With this fix, the administrator is able to enumerate the users on a
Feature Release 2 server when using the shadow taskbar on a Feature
Release 3 server.
[#71364]
128. When an ICA Client requested the MetaFrame server for an update of
Caps Lock, Num Lock, and Scroll Lock, the Kana_Lock flag was turned off.
The MetaFrame server regarded the flag as a request to turn off Kana_Lock
and changed the state every time the request came from the client.
This fix resolves the problem; the MetaFrame server retains the current
Kana_Lock setting and does not turn it off unexpectedly.
[#71495]
129. If a MetaFrame XP Feature Release 3 server on a French platform was
used in interoperability mode, the ICA browser service could not be
started. One resource string for the French platform was incorrect.
This fix corrects the resource string. Users on a French platform
operating in interoperability mode can start the ICA browser service with
no problems.
[#71496]
130. Sometimes a published application was launched more than once in the
same session in the following scenario:
? The published application was configured in the Management Console with
Allow only one instance of the application for each user
? 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 fix
corrects the problem and only one instance of the published application is
launched.
[#71801]
131. When trying to save a Microsoft Excel workbook to a client drive,
users received the following message.
?The file filename.xls may have been changed by another user since you
last saved it. In that case, what do you want to do??
This occurred because the Client Drive Mapping feature returned the
LastWriteTime of the file without synchronizing with the ICA Client.
This fix corrects the issue.
[#72187]
132. 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.
[#72688]
133. After successfully installing a package with Installation Manager,
users could not log on with either ICA or RDP. A manual restart of the
server worked around the issue. Installation Manager incorrectly set the
internal Windows state to System is in process of being shut down. This
state did not permit any new connections to the server until the system
was restarted.
With this fix, Installation Manager no longer sets the system state to
System is in process of being shut down. New connections are accepted with
no problem.
Note: In some cases, it may be necessary to restart the system after
application of this fix. Otherwise, you need to restart only the IMA
Service.
[#72794]
134. When installing a package using Installation Manager on a server
connecting to a replicated SQL data store, the package did not install and
remained in a pending state. The Installation Manager subsystem on the
target server attempted to read the server group from the data store,
where it had not yet been updated. The resolution is to read from the
local host cache first and then from the data store. The local host cache
is updated at the same time as the request for the installation job
arrives at the target server, so the local host cache always has the
correct record for the server group.
Now when installing a package using Installation Manager on a server that
is connecting to a replicated SQL data store, the package installs
correctly.
[#72877]
135. If Automatic install of native drivers was disabled, no events were
generated in the event log when printers could not be autocreated. With
this fix, events are generated if printers cannot be autocreated.
[#72922]
136. When trying to initialize objects using their MetaFrameID, the
following error message appeared:
?HRESULT of E_INVALIDARG?
This was caused by an improper conversion of a 32-bit variable to a 64-bit
variable.
This fix resolves the issue.
[#73044]
137. If the Remove my computer icon on the desktop policy setting was
enabled, an ICA connection to a MetaFrame server generated a Dr Watson
error for the Cmstart.exe process. Cmstart.exe was incorrectly making a
function call on a NULL interface pointer.
A validation check was added to prevent calling a function on a NULL
interface pointer and Cmstart.exe no longer causes a Dr Watson error at
logon..
[#73254]
138. The following keys did not always work within a session using
non-Windows clients:
<, >, \ (Danish keyboard layout)
The Unicode conversion table was using an Alt+Numpad key sequence even
though the characters could be typed with a single keystroke.
The conversion table entries are changed so that the characters can be
typed with a single keystroke instead of using an Alt+Numpad key sequence.
[#73285]
139. If Connect Client Printers at Logon was not checked, users either
were completely unable to map client printers or could not see any of the
available UPD printers when connecting to a printer. A misplaced
initialization of the Metafile drivers caused the Metafile drivers to be
unavailable.
This fix enables the Metafile drivers and clients can map any client
printer.
[#73621, #73769]
140. If two clients shared the same print driver but the name of the
driver differed in case (lowercase versus uppercase), the Management
Console assumed two printers were involved. This caused problems with
printer autocreation.
This fix ensures that driver comparisons operate correctly.
[#73722]
141. Occasionally the IMA Service experienced a fatal error when an
administrator tried to add a MetaFrame administrator using the Management
Console for MetaFrame XP using the following steps:
. Click the Add Administrator icon in the Management Console.
. Select the Show Users checkbox.
. Double-click a domain.
. Double-click a group.
. Click Add.
Sometimes an unsigned integer was decremented even though its value was
already zero. This unsigned integer served as an index to a memory block.
This caused any access to the memory block using the index to be out of
boundary and memory access violation occurred.
This fix ensures that the unsigned integer is not decremented when it is
already zero. The IMA Service no longer experiences a fatal error.
[#74268]
142. If the print spooler service stopped during a print job during an ICA
session, logging on to the MetaFrame server with RDP and attempting to
restart the spooler service sometimes resulted in a fatal system error.
Certain operations in Client Drive Mapping could take a very long time and
were subject to interruption by a user. If the interruption occurred, the
operations did not clean up the operating system kernel data structures
properly, causing the fatal system error.
This fix ensures that the long term operations in Client Drive Mapping can
be interrupted or canceled by a user but that proper cleanup of the
operating system kernel data structures will still occur without causing a
fatal error.
[#74290]
143. A memory leak occurred when MFCOM was accessed to enumerate servers
in a farm. MFCOM was using an incorrect function to release internal
memory allocated for server enumeration.
This fix ensures that MFCOM uses the correct function to release internal
memory allocated for server enumeration and the memory leak no longer
occurs.
[#74312]
144. 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.
[#74934]
145. Cdm.sys was causing the server to trap with bug check code 0xC4 when
the driver verifier was enabled. This occurred because the driver was
trying to free memory twice.
This fix ensures that appropriate checks are made before freeing memory.
[#75224]
146. The Web Interface, including the logon page before credentials were
entered, responded very slowly and eventually became inaccessible. This
problem occurred when there were a large number of published applications
(600 - 1000) and during heavy user traffic. Users could not enumerate
applications due to a bottleneck in the IMA application cache caused by a
high number of enumerations per minute (200 - 300 per Web server) and a
high number of published applications (600 -1000). Up to 20 threads could
be blocked while trying to read the IMA application cache.
The IMA application cache serial lock is replaced with a reader/writer
lock. This allows multiple reader threads to access the cache without
being blocked, resulting in improved performance of enumeration of large
numbers of published applications.
[#75454]
147. Client USB smart card devices were causing the server to experience a
fatal system error. When the connection was reset, a race condition was
not handled properly, causing the problem.
The race condition is now handled properly and the server no longer
experiences a fatal system error.
[#75473]
148. On a Windows 2000 Server or a Windows Server 2003 with Citrix
MetaFrame XP, Feature Release 3 installed, with a Danish keyboard
configuration, the server experienced a fatal system error. This was
caused by an incorrect data entry for the Diaeresis (U-00A8) and Acute
accent (U-00B4).
This fix resolves the issue.
[#75797]
149. When an application running in seamless mode became unresponsive,
users sometimes could not switch to other applications that were running
in seamless mode also. Clicking the taskbar icon or using the Alt-Tab
sequence did not work. The server seamless engine was using an API that
did not return if the target application was unresponsive.
This fix provides additional routines that call only those applications
that are responding. Users can switch to other applications even if one is
unresponsive.
[#76070]
150. If an Installation Manager package is scheduled/rescheduled on the
31st of the month to be installed on a date in the following month, the
installer scheduled the package to be installed one month later. The
calendar object was incorrect when selecting the installation date for a
package if the date when the installation was scheduled was the 31st of
the month.
This fix ensures that the installation date is correct no matter what the
current date is when scheduling occurs.
[#76147]
151. The ICA Client distribution wizard software installed on a MetaFrame
XP Feature Release 3 or below server experienced a fatal error if supplied
with the ICA Client setup initialization file of MetaFrame Presentation
Server 3.0. This occurred because insufficient memory was allocated for a
buffer to hold the information about the clients in the client setup
initialization file.
This fix ensures there is sufficient buffer space to hold all the required
information and the ICA Client Distribution wizard no longer experiences a
fatal error.
[#76507]
152. When users ran the drive remap utility, Driveremap.exe, in unattended
mode and then restarted the server, the drive was remapped as expected,
but the report file secedit.INTEG.RAW was inadvertently placed under Start
> Programs. Every time users logged on to the server thereafter, an error
message appeared stating that the report file could not be opened because
it had not associated an application with it.
This fix corrects the issue and the report file is removed.
[#76592]
153. 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 fix resolves the problem.
[#76593]
154. Users were experiencing various problems such as initializaion
failures, critical exceptions in NTDLL, abnormal termination of
applications, and no sound over ICA connections.
This fix resolves the various issues.
[#77002]
155. A user was employing a Linux Client from a UNIX workstation with a
Brazilian ABNT2 keyboard layout. When users attempted to log on to a
MetaFrame XP, Feature Release 3 server, the keyboard did not work in the
ICA session. In Windows, the ID for a Brazilian ABNT2 keyboard layout is
00010416. MetaFrame did not have a comparable file.
A keyboard layout file was created to accommodate a Brazilian ABNT2
keyboard and the keyboard works as expected.
[#77103]
156. MetaFrame XP was bypassing any application limits set in the
Management Console for pass-through connections. A global variable was not
being properly set in pass-through connections.
The global variable is now set correctly and MetaFrame adheres to any
application limits set in the Management Console for pass-through
connections.
[#77372]
157. The cent sign (¢) and the broken bar (the key adjacent to the left
shift key on a Dutch keyboard) did not always work on non-Windows clients
configured with a Dutch keyboard layout. This occurred because the
diacritic key Unicode mappings were not properly defined in the Dutch
keyboard (.kbd) file.
The keyboard mapping has been corrected and users no longer have a problem
using the cent sign and broken bar symbols on Dutch keyboards.
[#77702]
158. Icons for applications on a network share were not being displayed.
This fix resolves the issue.
[#78094]
159. Changing passwords through the Web Interface changed the Novell
password but not the Windows password. Now when the Web Interface requests
a password change from the XML Service, both the Novell and Windows
passwords are changed.
Important: If the XML Service is running in non-port sharing mode, you
must restart the XML Service after you install this fix.
[#78650]
160. If MetaFrame XP Feature Release 3 servers were installed with a fix
that included fix reference number 66606, some Java and SGI Clients could
not print to client autocreated printers. Installation of Feature Release
3 caused some clients to have incompatible protocols so that the servers
could not write to the clients for printing.
This fix ensures that the server?s protocol is compatible with the
client?s protocol and printing to client autocreated printers works
correctly.
[#78668]
161. Servers were trapping in Cdm.sys with the following STOP error
message:.
STOP 0x000000C2 BAD_POOL_CALLER (0x00000040, 0x00000000,
0x80000000,0x00000000)
This occurred because Cdm.sys was calling a memory free function with a
NULL pointer.
This fix alters that behavior; Cdm.sys no longer calls a memory free
function with a NULL pointer.
[#78747]
162. The Euro symbol did not always work in Microsoft Word on non-Windows
clients configured with a Norwegian keyboard layout. This occurred because
the diacritic key Unicode mappings were not properly defined in the
Norwegian keyboard (.kbd) file.
The keyboard mapping is corrected and users no longer have a problem using
the Euro symbol on Norwegian keyboards.
[#79182]
163. Internet Explorer experienced a fatal error when SpeedScreen Browser
Acceleration was enabled and a JPEG image of a certain size was loaded.
This occurred because an error caused the checktag to be written into an
image buffer.
This fix ensures that the checktag and the offset are handled correctly
and Internet Explorer loads JPEG images properly.
[#79220]
164. Some printers were not automatically autocreated in an ICA session
and an Event ID 1107 entry was recorded in the event log. This issue
tended to occur when several users attempted to connect to the same server
at the same time and if the printer driver was not installed on the
server.
With this fix, printer autocreation occurs correctly.
[#79268]
165. Icons for applications published through MFCOM looked fuzzy when
compared with the icons for the same applications when published through
the Management Console for MetaFrame XP. Icon generation in the IMA
Service was changed but the corresponding change was not made in MFCOM.
This fix ensures that icons for applications published through MFCOM look
similar to the icons for the same applications when published through the
Management Console.
[#79317]
166. If session sharing was disabled, client-to-server redirection failed
because applications with command lines that contained spaces in the paths
were not being launched.
This fix ensures that client-to-server redirection works even if session
sharing is disabled.
[#79331]
167. Reconnecting to a disconnected session did not work when applications
were limited to one instance per user. This problem occurred mainly when
session sharing was used. Due to session sharing, if a user was connected
to application A on server A and then tried to connect to application B
(hosted only on server B), the request to launch the application was sent
to server A. The IMA Service on server A checked to see if there were
disconnected sessions and also what limits were set on the application.
Because there was a disconnected session on server B and the limit was set
to one instance per user, the request. was rejected.
This fix ensures that the IMA Service on server A first checks whether or
not the application is hosted on that server before checking for
disconnected sessions or limits. So, if the IMA Service returns an error
message to the client that the application is not hosted on server A, the
client can make a connection to 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.
[#79433]
168. Note: You must install Microsoft Hotfix Q816134 before applying this
fix.
Servers slowed down randomly and eventually experienced a fatal system
error. This occurred most frequently during session reconnections.
This fix, along with the Microsoft hotfix, resolves the problem.
[#80186]
169. The server-side wallpaper appeared occasionally for a short time when
a seamless window was closed. There was a slight delay between the time
the window was closed and the seamless engine notified the client that the
window was closed. During that time, the client-side engine tried to
update the window that was already closed, resulting in the brief
appearance of the server-side wallpaper.
This fix ensures that the seamless engine immediately detects that the
window is closed and the server-side wallpaper no longer appears.
[#80221]
170. ICA sessions experienced fatal errors when users tried to change
their passwords. This 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.
[#80466]
171. The Euro symbol and the backslash key ( \ ) did not always work in
Notepad on non-Windows clients configured with a Belgian keyboard layout.
This occurred because the diacritic key Unicode mappings were not properly
defined in the Belgian keyboard (.kbd) file.
The keyboard mapping has been corrected and users no longer have a problem
using the Euro symbol or the backslash key on Belgian keyboards.
[#80524]
172. The caret symbol ( ^ ) did not always work in Notepad on non-Windows
clients configured with a Belgian French keyboard layout. This occurred
because the diacritic key Unicode mappings were not properly defined in
the Belgian French keyboard (.kbd) file.
The keyboard mapping has been corrected and users no longer have a problem
using the caret symbol ( ^ ) on Belgian French keyboards.
[#80525]
173. A number of keys did not work on Windows CE and non-Windows devices
configured with a Croatian keyboard layout. This occurred because the
Unicode mappings were not properly defined in the Croatian keyboard (.kbd)
file.
The keyboard mapping has been corrected and users no longer have a problem
with dead keys on Croatians keyboards.
[#80526]
174. When using smart cards, users were sometimes unable to reconnect to
disconnected sessions. This issue was caused by certain Cryptographic
Service Providers (CSPs) permitting server smart card commands to be sent
to the client before the reconnection sequence was complete.
This fix ensures that no commands are sent to the client before the
reconnection sequence is complete.
[#80574]
175. Various diacritic dead keys did not work on HP Warbird CE devices
configured with a Czech keyboard layout. This occurred because the
diacritic key Unicode mappings were not properly defined in the Czech
keyboard (.kbd) file.
The keyboard mapping has been corrected and users no longer have a problem
using the diacritic dead keys on Czech keyboards.
[#80867]
176. The pipe symbol ( | ) did not always work on non-Windows clients
configured with a Finnish keyboard layout. This occurred because the
diacritic key Unicode mappings were not properly defined in the Finnish
keyboard (.kbd) file.
The keyboard mapping has been corrected and users no longer have a problem
using the pipe symbol ( | ) on Finnish keyboards.
[#80868]
177. The caret symbol ( ^ ) did not always work on non-Windows clients
configured with a French keyboard layout. This occurred because the
diacritic key Unicode mappings were not properly defined in the French
keyboard (.kbd) file.
The keyboard mapping has been corrected and users no longer have a problem
using the caret symbol ( ^ ) on French keyboards.
[#80878]
178. Listener values could not be obtained or set correctly through the
MFCOM interface if the farm was in interoperability mode. This ocurred
because MFCOM was not using the correct set of functions to get and set
listener values in interoperability mode.
This fix modifies the implementation of those functions.
[#81033]
179. The Load Manager IP Address Range rule did not work consistently.
When changing the IP Address Range rule through the Management Console,
the data store and local host cache were updated and the IP rule worked
correctly. However, when the next Directory Change Notification Poll Event
occurred, the IP Address Range Record was deleted from the local host
cache and the new IP range rule no longer worked. The IMA Service had to
be restarted for the rule to work again.
This fix prevents the directory change notification event from deleting
the IP address range record from the local host cache.
[#81464]
180. Users could not schedule package deployments for any Sunday that
coincided with the first day of the month for regions where Monday is
considered the first day of the week; for example, France.
This fix ensures that the program logic properly handles deployments
scheduled for any day of the week regardless of which day is considered
the beginning of the week.
Note: After you install this fix, restart the Management Console for
MetaFrame.
[#82295]
181. When users connected to a published tool called Microsoft Imaging
Software and chose the pen or highlighter mode, the mouse pointer
disappeared from the document area of the screen. This occurred because
the ICA video driver was not supporting 32-bit maps for the ICA Client.
This fix ensures that when users connect to a published tool called
Microsoft Imaging Software and choose the pen or highlighter mode, the
correct mouse pointer is displayed in the document area of the screen.
[#83045]
182. A number of diacritic dead keys did not work on Windows CE and
non-Windows devices configured with a Czech keyboard. This occurred
because the Unicode keyboard mappings were not properly defined in the
Czech keyboard (.kbd) file.
The keyboard mapping has been corrected and users no longer have a problem
using a Czech keyboard.
[#83444]
183. Several keys did not work on devices configured with an Estonian
keyboard. This occurred because the Unicode keyboard mappings were not
properly defined in the Estonian keyboard (.kbd) file.
The keyboard mapping has been corrected and users no longer have a problem
using an Estonian keyboard.
[#83445]
184. Unicode characters in the range of 7000 to 10,000 did not work on
devices configured on a Latin American keyboard . This occurred because
the Unicode keyboard mappings for that range of keys were not properly
defined in the Latin American keyboard (.kbd) file.
The keyboard mapping has been corrected and users no longer have a problem
using a Latin American keyboard.
[#83447]
185. A number of keys did not work with a Slovak keyboard layout within an
ICA session. This occurred because the Unicode mappings were not properly
defined in the Slovak keyboard (.kbd) file.
The keyboard mapping has been corrected and users no longer have a problem
using a Slovak keyboard in an ICA session.
[#83448]
186. 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 fix 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.
[#83453]
187. Servers experienced a fatal system error with a smart card. This
occurred because the smart card logic was not handling the client/server
interaction properly, especially when the client did not respond before
the server timed out the client request.
This fix ensures that the servers no longer experience a fatal error with
a smart card.
[#83525]
188. The display speed of the combo list box became very slow if the list
box expanded beyond the area of the background window. The seamless
routine that checked to determine whether or not the target window was a
top-level window ignored the window, causing a delay in the display of the
window.
A new API is now used to determine whether or not the target window is a
top-level window. The combo list box appears as quickly as other types of
windows in a seamless session.
[#83550]
189. When the following registry entry was set, Sehook20.dll was still
loaded in the session:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\Wfshell\TWI
Type: REG_DWORD
Data: SeamlessFlags=0x4
In certain situations, the registry entry was ignored, causing
Sehook20.dll to be loaded despite the registry setting. This fix ensures
that the registry entry is used to determine whether or not to load
Sehook20.dll in the session.
[#83555]
190. The MFCOM SDK IMetaFrameWinApp::Validate function could not handle
modified applications.
With this fix, the MFCOM SDK function does not report failure when a
modified application is passed if the application is valid.
[#84231]
191. With replicated SQL databases, the printer mapping changes are not
properly propagated to the server on the subscriber database IMA data
store. This was a result of latency in the underlying database
replication.
This fix resolves the problem by populating the Local Host Cache (LHC)
with the printer mapping data and reading the printer mapping data
directly from the LHC, not the data store.
[#84528]
192. The AltGr key plus the key next to the left Shift key and the AltGr
key plus the third key to the left of the right Shift key did not work in
Windows CE or non-Windows clients configured with a Canadian French
keyboard layout. This occurred because the Unicode keyboard mappings were
not properly defined in the Canadian French keyboard (.kbd) file.
The keyboard mapping has been corrected and users no longer have a problem
using a Canadian French keyboard.
[#84624]
193. A number of keys did not work in Microsoft Word or Notepad on Windows
CE or non-Windows clients configured with a Czech keyboard layout. This
occurred because the Unicode keyboard mappings were not properly defined
in the Czech keyboard (.kbd) file.
The keyboard mapping has been corrected and users no longer have a problem
using a Czech keyboard.
[#84630]
194. The Euro key with the AltGr key did not work in Windows CE or
non-Windows clients configured with a Greek keyboard layout. This occurred
because the Unicode keyboard mappings were not properly defined in the
Greek keyboard (.kbd) file.
The keyboard mapping has been corrected and users no longer have a problem
using a Greek keyboard.
[#84631]
195. A number of keys did not work in Microsoft Word or Notepad on Windows
CE or non-Windows clients configured with a Hungarian keyboard layout.
This occurred because the Unicode keyboard mappings were not properly
defined in the Hungarian keyboard (.kbd) file.
The keyboard mapping has been corrected and users no longer have a problem
using a Hungarian keyboard.
[#84632]
196. A number of keys did not work in Microsoft Word or Notepad on Windows
CE or non-Windows clients configured with a Polish keyboard layout. This
occurred because the Unicode keyboard mappings were not properly defined
in the Polish keyboard (.kbd) file.
The keyboard mapping has been corrected and users no longer have a problem
using a Polish keyboard.
[#84633]
197. The Cyrillic letter Io did not work in Microsoft Word or Notepad on
Windows CE or non-Windows clients configured with a Russian keyboard
layout. This occurred because the Unicode keyboard mappings were not
properly defined in the Russian keyboard (.kbd) file.
The keyboard mapping has been corrected and users no longer have a problem
using a Russian keyboard.
[#84634]
198. A number of keys did not work in Microsoft Word or Notepad on Windows
CE or non-Windows clients configured with a Slovenian keyboard layout.
This occurred because the Unicode keyboard mappings were not properly
defined in the Slovenian keyboard (.kbd) file.
The keyboard mapping has been corrected and users no longer have a problem
using a Slovenian keyboard.
[#84636]
199. The Euro key did not work in Microsoft Word or Notepad on Windows CE
or non-Windows clients configured with a Spanish keyboard layout. This
occurred because the Unicode keyboard mappings were not properly defined
in the Spanish keyboard (.kbd) file.
The keyboard mapping has been corrected and users no longer have a problem
using a Spanish keyboard.
[#84639]
200. A number of keys did not work in Microsoft Word or Notepad on Windows
CE or non-Windows clients configured with a Turkish F keyboard layout.
This occurred because the Unicode keyboard mappings were not properly
defined in the Turkish F keyboard (.kbd) file.
The keyboard mapping has been corrected and users no longer have a problem
using a Turkish F keyboard.
[#84640]
201. A number of keys did not work in Microsoft Word or Notepad on Windows
CE or non-Windows clients configured with a Turkish Q keyboard layout.
This occurred because the Unicode keyboard mappings were not properly
defined in the Turkish Q keyboard (.kbd) file.
The keyboard mapping has been corrected and users no longer have a problem
using a Turkish Q keyboard.
[#84641]
202. The system experienced a fatal system error because of a
synchronization error in Wdica.sys.
This fix resolves the synchronization issue and the system functions
normally.
[#84651]
203. Keyboard input did not appear in the speed screen latency reduction
temporary text cache on the client if Australian English was set as the
default locale in an ICA session. The corresponding keyboard layout dll
failed to load.
This fix ensures that keyboard input appears in the speed screen latency
reduction temporary text cache on the client when Australian English is
set as the default locale in an ICA session.
[#84653]
204. Users occasionally experienced disconnected sessions when
transferring large amounts of data over low-bandwidth modem connections.
This fix prevents the session from disconnecting.
[#84837]
205. A number of keys did not work on Windows CE or non-Windows clients
configured with a Slovak keyboard layout. This occurred because the
Unicode mappings were not properly defined in the Slovak keyboard (.kbd)
file.
The keyboard mapping has been corrected and users no longer have a problem
using a Slovak keyboard.
[#84838]
206. 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 to the Program Neighborhood virtual channel is the same as the
one obtained from the logged on user token. The problem occurred because
the NDS user name and context were not being checked.
This fix ensures that NDS credentials are verified.
[#84862]
207. Applying the fix for another issue caused the Local Host Cache (LHC)
to grow abnormally large and it exposed another major problem. For various
reasons, every Windows 2000 native printer driver is installed on every
server in the farm. After applying the fix for the first issue, the Local
Host Cache needed to be recreated on every server in the farm to reduce
the LHC to a more manageable size. The problem with recreating the LHC was
that the procedure took hours per server to complete.
The resolution is to do the synchronization for all the printer drivers in
the data store just once.
After applying this fix, there is significant improvement in the LHC
synchronization time.
[#85052]
208. This is a request for a feature change enhancement involving the
following three scenarios:
. If Create browser listener on UDP network was not checked in the
Management Console, typing qfarm.exe /tcp at a command prompt did not
display the server nor did the server and its IP address appear in the
command qfarm.exe.
. If Create browser listener on IPX network was not checked in the
Management Console, typing qfarm.exe /ipx at a command prompt did not
display the server nor did the server and its IP address appear in the
command qfarm.exe.
. If Create browser listener on NetBIOS network was not checked in the
Management Console, typing qfarm.exe /netbios at a command prompt did not
display the server nor did the server and its IP address appear in the
command qfarm.exe.
This enhancement ensures that the behavior described in the three
scenarios no longer occurs.
[#85071]
209. When users attempted to log on using a smart card, the following
error message appeared:
?The system could not log you on. The requested key container does not
exist on the smart card.?
Some Cryptographic Service Providers (CSPs) saved the name used during the
logon sequence for later use. The session prefix was added only during the
logon sequence and became invalid at a later point.
To ensure the session number is not used as a prefix for the smart card
reader name, make the following change to the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\SmartCard
Data: ScUniqueReaderName=0
With this registry change, the prefix is not added to the smart card
reader name during the logon sequence and the CSP uses the proper name to
successfully access the smart card reader.
[#85648]
210. This fix addresses a custom application?s performance when run
seamlessly. Some applications appeared to be slower to respond when
performing actions such as moving, resizing, or closing windows. This fix
introduces two new registry settings that allow administrators to
configure an explicit time interval for the seamless engine mechanism to
monitor when changes take place in the seamless applications.
Create the following two registry keys:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI
Key: WorkerWaitInterval
Type: REG_DWORD
Value: Number of milliseconds allowed (Values are between 5 ? 500; the
default is 50.)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI
Key: WorkerFullCheckInterval
Type: REG_DWORD
Value: Number of milliseconds allowed (Values are between 50 ? 5000; the
default is 500.)
For both values, a larger size slows responsiveness but improves
scalability; a smaller size increases responsiveness but decreases
scalability slightly. The level of scalability depends on several factors,
such as hardware sizing, types of applications, network performance, and
number of users.
[#85657]
211. Server-to-client content redirection was not functioning properly
with URLs in Microsoft Outlook 2003 published on servers running MetaFrame
XP with Feature Release 3. When the URL was clicked, the link opened in an
instance of Internet Explorer published on the server rather than the
instance installed on the local client device. This was caused by an
incorrect registry key setting.
This fix corrects the issue.
[#85707]
212. A smart card application was requesting status continually or invalid
smart card status was being received. The reader state information
maintained by the Citrix Device Management component was incorrectly
updated. In addition the smart card state data included some
non-documented third-party flags that were being compared.
This fix ensures the reader state information is properly maintained by
the Citrix Device Management component. The smart card application no
longer continually requests status nor is invalid smart card status being
transmitted.
[#85780]
213. If an administrator changed some of a server?s settings under ICA
Browser in MetaFrame XP Settings on the Management Console and later
executed dsmaint recreatelhc on that server, the changed setting was not
retained. After executing dsmaint recreatelhc, the changed settings were
overwritten with default values in error.
This fix ensures that changed settings on a server are retained after
executing dsmaint recreatelhc on that server.
[#86011]
214. The IMA Service sometimes experienced a fatal error when an
administrator viewed, added, or deleted users on the node of a published
application from the Management Console. This occurred because one
function of the IMA Service was not checking the error code correctly.
This fix ensures that the function of the IMA Service correctly checks the
error code.
[#86433]
215. Some custom applications that did not display properly when running
on Windows XP/2000 with the Windows XP Theme enabled sometimes saw the
same behavior when running as a seamless application on MetaFrame XP
Feature Release 3 on Windows 2003 that does not have the Windows XP Theme
enabled. For example, the title bar of the application is larger in
height.
Starting with MetaFrame XP Feature Release 3 for Windows 2000/2003, the
server seamless engine has extended support for certain window style
properties of the workstation where the seamless application is running;
for example, the styles generated by Windows XP Themes.
This fix introduces a new seamless global registry flag that, when set,
instructs the server-side seamless engine not to read certain client
workstation window style information.
Set the following server-side registry key to instruct the server seamless
engine not to synchronize with the client?s window style that pertains to
those representative of the Windows XP Theme:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI
Name: SeamlessFlags
Type: REG_DWORD
Value: 0x4000
Custom applications that do not display properly when running on Windows
XP/2000 with the Windows XP Theme enabled can be run in a seamless session
from a workstation that has the Windows XP Theme enabled and be displayed
using the Windows Classic style.
[#87052]
216. An unresponsive server (IMA, XML, or Termsrv) could cause a farm
outage. This occurred when the unresponsive server was still capable of
sending load level updates to the data collector. Becasue the server was
not accepting connections, it remained as the least loaded server in the
farm and all new connection attempts were routed to it.
When a least loaded server was unresponsive, the data collector continued
to resolve connections to the server. The data collector sent all new
connection attempts and/or ticket requests to that server even though that
server would not respond to these requests.
If the server does not respond to a ticket request (times out), the data
collector is notified to update the server?s load to maximum. This
prevents any new ticket request to that server. The server stops its IMA
Service.
This fix prevents the unresponsive least loaded server from causing a farm
outage.
[#87613]
217. The content-redirection for Windows File Type Associations sometimes
became corrupted when a user modified a published application?s
command-line attribute.
This fix ensures that the Management Console for MetaFrame will not reset
the File Type Association settings whenever a user changes the published
application?s command-line attribute. Therefore, the command-line
attribute of the published application can be changed without corrupting
the File Type Associations.
[#87751]
218. Applications sometimes stopped running if they were configured to use
Word Wrap when Local Text Echo was enabled. The problem resulted from a
buffer overrun.
This fix resolves the problem by ensuring the buffer sizes and
applications no longer stop running if they are configured to use Word
Wrap when Local Text Echo is enabled.
[#87756]
219. If users attempted to access a Web site through Start > Run with a
URL that was longer than 256 characters (in some cases longer than 202
characters), the correct Web page appeared but Wfshell experienced a fatal
error. This problem occurred because of a buffer overrun in handling the
URL.
With this fix, when a URL longer than the allowed character limit is
pasted into Start > Run, Internet Explorer is launched and Wfshell remains
running without experiencing a fatal error.
[#87825]
220. Iexplore.exe sometimes became unresponsive when displaying images in
an ICA session if SpeedScreen browser acceleration was turned on. A
SpeedScreen acceleration routine did not compute the number of image scan
lines sufficiently to store the image check tag correctly, causing a
buffer overrun and leading to an application fault.
This fix ensures that the number of image scan lines is sufficient to
store the image check tag.
[#87843]
221. This is an enhancement to add the ability to configure which of the
server-to-client content redirection file types are allowed to be
redirected. By default, server-to-client content redirection redirects all
or none of the file types (http, https, rtsp, rtspu, pnm, mms).
A new registry key is specified to allow certain file types to be excluded
from content redirection. If HKEY_LOCAL_MACHINE
\SOFTWARE\Citrix\SFTA\DisableServerFTA is set, the multistring registry
value HKEY_LOCAL_MACHINE\SOFTWARE \Citrix\SFTA\NoRedirectClasses specifies
which file types are excluded from redirection. If the file type is not in
the list, it is redirected.
To implement this enhancement, make the following value changes to the
registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\SFTA
Name: DisableServerFTA
Type: REG_DWORD
Value: 1
Name: NoRedirectClasses
Type: REG_MULTI_SZ
Value: Specify any combination of the following values:
http,https,rtsp,rtspu,pnm,mms (these values are comma-delimited with no
space between)
With these registry changes, administrators can configure which file types
to exclude when using server-to-client redirection.
[#88380]
222. Saving a file to a client drive failed if the value of the seconds
portion of the time stamp equaled 59 because the Client Drive Mapping
feature rounded up the time stamp but failed to propagate the change.
This fix corrects the issue.
[#88799]
223. If the DisableError registry value was turned to ON and client
printer autocreation failed with the native printer driver but succeeded
with UPD, Event ID 1106 was logged in the event log. This occurred because
the registry value was not checked.
To avoid this problem, check the registry value before logging off. The
Event ID 1106 message is not logged.
[#89250]
224. The qfarm.exe utility failed to return data after a large number of
servers in a farm were restarted. This was caused by a number of read-only
objects preventing the utility from returning data.
This fix corrects the issue.
[#88608]
225. Some of the Japanese IME 2003 functions were not available in
published applications because the routine to enable IME was not being
executed.
This fix includes the routine to ensure that IME 2003 functions as
expected in published applications.
[#89686]
226. After a user created a custom ICA connection and connected to the
server desktop, no client printers were autocreated in the Printers
folder. The port monitor enumerated all existing ports on the system
before creating the port for the autocreated printer. It did not properly
catch the error condition and incorrectly reported that the port to be
autocreated already existed
Note: After applying this fix, you must restart the spooler service.
[#90244]
227. Every time a user who autocreated printers connected to a server,
printed, and then logged off, the handle count on the spooler service
increased. In addition, after the print spooler service ran for some time
on a server to which many users were connecting with autocreated printers,
many ports not belonging to any active printers were visible under
Printers > File > Server Properties > Ports. This occurred because
autocreated printer ports were not deleted when users logged off or if
there was a problem opening the printers.
This fix corrects the issue.
[#90456]
228. Instance limits for published applications were occasionally enforced
incorrectly when users connected to several published applications at the
same time. Therefore, when users connected to a second published
application, an error message may have appeared stating the instance limit
for the application had been reached when, in fact, it had not.
This fix corrects the issue.
[#91714]
229. Session sharing failed in mixed Windows/NDS deployments if users
employed the same password for both accounts but the application being
launched was available only to Windows domain users.
This fix corrects the issue.
[#92572]
230. A popup window of a custom application running in seamless mode
prompted the display of a dialog box as if Windows Explorer was being
launched, when, in fact, it was not.
This fix corrects the issue.
[#92839]
231. Note: This line item applies only to the Japanese version of Feature
Release 3/Service Pack 4.
By default, the IMA Service uses UTF8 to communicate with an Oracle
database. For Japanese double-byte characters, the variable NLS_LANG is
set to JA16SJIS (Shift+JIS) and the IMA Service cannot communicate with
the Oracle database.
To resolve this issue, add the following to DSMAINT.exe:
DSMAINT MIGRATE /SRCDSN:dsh:1 /SRCUSER:user1 /SRCPWD:pwd1 /DSTDSN:dsn:2
/DSTUSER:user2 /DSTPDW:pwd2 /RECREATEINDEX
DSMAINT RECREATEINDEX /DSN:dsn /USER;user /PWD:pwd
[#86413]
232. After a server was running for an extended period of time, the IMA
Service became exceptionally large, exhausting system resources. This was
caused by a memory leak in the IMA Service.
This fix resolves the issue.
[#88583]
233. Various Japanese IME 2003 functions were not available in published
applications. The routine to enable IME was not being enabled.
This fix ensures that Japanese IME 2003 functions are enabled in published
applications.
[#89686]
234. Note: This item pertains to Windows 2000 Server only.
When attempting to publish RDP clients that support SmartCard, users could
not use the published RDP client with a SmartCard. This occurred because
of a misunderstanding of API functionality.
With this fix, RDP detects SmartCard support properly.
[#90698]
235. Users were losing cut and paste functionality.
This fix ensures that cut and paste works correctly.
[#90826]
236. When users locked their workstations using the hotkey combination
Ctrl+F1, clicked the mouse outside the window, and then attempted to
return to the ?locked? window by clicking the mouse in the window, the
user name and password fields did not respond to the keyboard. When the
workstation is locked, the system switches from the user desktop to a
secure desktop. In this case, the foreground window was not set correctly.
Application of this fix resolves the issue.
[#93099]
237. If a user specified a domain name without a user name, the ICA
session did not use the specified domain; rather it used the default
domain configured on the server. Without a user name, the user credentials
were assumed to be invalid.
This fix ensures that the specified domain name is always used for session
logon.
[#94718]
238. Using Explorer, if users attempted to copy a file to the same folder
on a mapped drive in Windows Server 2003, the file copy failed and an
error message appeared. In Windows 2000, the file was copied with a ?Copy
of? prefix.
This fix resolves the issue.
[#96424]
239. When shadowing a seamless session, windows could not always be
located if they were minimized. The server seamless engine was updating a
flag that told the system to hide the minimized window.
That flag is now removed when synchronizing UI settings sent from the
client and the shadower can always locate minimized windows in a seamless
session.
[#97204]
240. Servers sometimes experienced a fatal error and stopped accepting new
connections after they were running for some time if users enabled the no
remote drives policy. This occurred because of a memory leak in the paged
pool.
This fix resolves the issue.
[#97536]
241. When trying to launch a connection using SmartCard authentication,
the following error message appeared:
?Error in Connection:
Error 1031: Virtual Driver Error?
SmartCard authentication now works correctly.
[98511]
242. Running iexplore -e in a seamless session caused a warning message to
appear. The message stated that the Windows desktop was starting and would
obscure the current desktop.
This fix checks the window class of the starting application to ensure it
is not a Windows Explorer desktop. The error message no longer appears
when running iexplore -e in a seamless session.
[#99087]
243. The IMA Service could not receive queries and writes from the data
store and the data store did not return any error messages. This sometimes
caused an entire farm to become unresponsive. This occurred because the
IMA query or write never timed out even if the SQL server failed to
respond. This fix sets an attribute that allows the query to time-out if
the SQL server fails to respond in a reasonable amount of time.
To enable this fix, navigate to the following registry key and change the
data from zero (0) to a higher value in decimal seconds:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\IMA
Name: DB_CONNECTION_TIMEOUT
Type: REG_DWORD
Data: Enter a number higher than zero in decimal seconds - adjust the
number as needed
With this fix, the data store query or write do not time-out and the IMA
Service performs as expected.
[#99277]
244. Seamless windows were not maximized when users double-clicked the
titlebar.
This fix resolves the issue.
[#87308]
245. The 'Í' (AltGr+T) and 'í' (AltGr+J) keys did not work as expected on
an HP Windows CE device on a Hungarian keyboard layout. A previous fix for
this problem did not take into account that there are two ways to produce
these keys.
This fix ensures that both methods of producing these keys is available.
[#98267]
246. Users accessing Distributed File System (DFS)-based file shares did
not get redirected to other replicas if the active DSF share became
inaccessible.
This fix corrects the issue.
[#91067]
247. Fixes a problem on some machines where a performance counter string
was not properly NULL terminated in the registry. This led to problems
like the following summary file entry:
"METRIC","Network Interface","Bytes Total/sec",
"WAN [PPP_SLIP] Interfaceä@"£(^","2002-12-09 21:32:19"
[From Hotfix RME103W2K001, RME103W2K3001]
248. Adds support for using SMTP servers to send email alerts, which is
available from Hotfix RME102W007 and later. You can configure this
functionality from the MAPI interface.
[From Hotfix RME103W2K001, RME103W2K3001]
249. Fixes an issue that occurred if users upgraded from Feature Release 2
to Feature Release 3 after installing Hotfix RME102W011 or RME102W012. The
summary database could not apply the schema correctly, causing the
database to become corrupted.
[From Hotfix RME103W2K001, RME103W2K3001]
250. Fixes an issue that occurred when users updated the summary database.
If the summary files included NULL characters at the end of the file, the
update failed.
[From Hotfix RME103W2K001, RME103W2K3001]
251. Fixes an issue where, after users restarted a server, an event type
2002 message appeared in the event log. This time-out message was
generated when Resource Manager attempted to query the performance
counters before the server was ready. This issue delayed startup of the
Resource Manager service. If this problem occurs again after you install
this hotfix, manually increase the time-out period by changing the
following registry value until the issue is resolved:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PerfDisk\Performance\Open
TimeoutThe time-out period is specified in milliseconds.
[From Hotfix RME103W2K001, RME103W2K3001]
252. Fixes an issue that occurred on some servers where an entry was not
made in the SDB_EVENTLOG table after restarting the server.
[From Hotfix RME103W2K001, RME103W2K3001]
253. Fixes an issue that occurred with applications with product dates set
before the year 1753. This issue caused the following error message to
appear in the event log:
"Communication with the Resource Manager local database failed with ODBC
Error 22008. ODBC Error String is [Microsoft][ODBC Microsoft Access
Driver]Datetime field overflow (null)."
The product date of these applications is changed to 1 Jan 1753 00:00:00.
The local database is fixed.
[From Hotfix RME103W2K001, RME103W2K3001]
254. Improved the performance of summary reports when using a large SQL
server or Oracle database.
[From Hotfix RME103W2K001, RME103W2K3001]
255. Fixes the following issues that occurred when generating summary
reports:
? If a report took over 10 minutes to generate, a time-out message
appeared (c0160b56) and the report was not generated. After you install
this hotfix, the time-out period is increased to 48 hours.
? If you cancelled a report while generating it, the dialog box closed but
the IMA service continued running and prevented you from generating
further reports.
After you install this fix, click Cancel to close the dialog box and stop
the IMA service from continuing to generate the report.
[From Hotfix RME103W2K001, RME103W2K3001]
256. Summary database fixed.
[From Hotfix RME103W2K002, RME103W2K3002]
257. This fix addresses issues with importing summary data into a summary
database on some non-English systems.
This is an example of an error message, caused by this issue when using a
Microsoft SQL Server summary database: '[Microsoft][ODBC SQL Server
Driver][SQL Server]Procedure
'AddProcess' expects parameter '@dSessionStart', which was not supplied.
Microsoft OLE DB Provider for ODBC Drivers System - 37000 System - Failed
to import summary file "C:\Program Files\Citrix\
Citrix Resource manager\SummaryFiles\1C1F6A12CD1259A" from host
"HOSTNAME"' Note: If the error message still appears after you install
this fix, there may be corrupt summary files on your server. To resolve
this issue, delete all files in the following folder:\Citrix Resource
manager\SummaryFiles
[From Hotfix RME103W2K003, RME103W2K3003]
258. This fix addresses the issue where active percentage could exceed
100% in the database reports. This hotfix does not alter existing
incorrect data in the database but fixes all new data entries in the
database.
[From Hotfix RME103W2K004, RME103W2K3004]
259. This fix addresses an issue where the IMA service could become
unresponsive due to non-standard metric data returned by the operating
system.
[From Hotfix RME103W2K005, RME103W2K3005]
260. This fix addresses an issue where duplicate user names could be
present in the Resource Manager summary database.
[From Hotfix RME103W2K006, RME103W2K3006]
261. This fix corrects the issue where a generated report was too big to
be displayed within the Management Console even though the report was not
to large to be displayed.
[From Hotfix RME103W2K007, RME103W2K3007]
262. This fix addresses the issue where after applying Hotfixes
RME103W2K001 through RME103W2K007, connecting with the Management Console
from a Feature Release 2 machine to a Feature Release 3 one and attempting
to generate a billing report from the summary database resulted in a
compatibility error between the database and Resource Manager.
[From Hotfix RME103W2K008, RME103W2K3008]
263. This fix addresses the issue where the Management Console needed to
be present for hotfixes to install.
[From Hotfix RME103W2K009, RME103W2K3009]
264. This fix addresses the issue where the Oracle database was taken
offline; for example, for back ups, and was still offline when the summary
database purge job activateed. When the purge job was activated, it failed
immediately due to the inability to contact the Oracle Listener.
The following appeared in the summary log:
9 August 2004 00:44:55 - System - Summary database purge for unbilled
sessions and processes starts.
9 August 2004 00:44:55 - System - Summary database purge of unbilled
sessions and processes failed with DB error 0x80004005. The error message
was ?[Oracle] [ODBC] [Ora] ORA-12514:TNS:listener could not resolve
SERVICE_NAME given in connect descriptor.?
9 August 2004 00:44:56 - System - Summary database purge for billed
sessions and processes starts.
The job was then rescheduled to execute immediately, resulting in many
excessive attempts per second.
[From Hotfix RME103W2K010, RME103W2K3010]
265. This fix addresses an issue where duplicate user names could be
present in the Resource Manager summary database. This fix ensures all new
user names are inserted in uppercase.
[From Hotfix RME103W2K011, RME103W2K3011]
Windows 2003
The following issues apply to only the Windows 2003 operating system.
1. Note: This line item applies only to the English version of Feature
Release 3/Service Pack 4.
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.
[#62617]
2. A feature release license for MetaFrame XP was not present and client
printers could not be autocreated. Terminal services in Windows 2003 was
changed so that the printer virtual channel needed to be created in the
system context. Otherwise, the MetaFrame server could not issue a printer
autocreation command through the printer virtual channel.
This fix ensures that client printers can be autocreated even if a feature
release license is not present.
[#63343]
3. Printing failed in an ICA session if the client printer was configured
through the Internet Printing Protocol. This occurred because the server
did not send the correct printer name to the client.
This fix permits the server to send the correct printer name to the
client.
[#67813]
4. If users had both local printers and network printers on their client
devices and the default printer was a network printer, ICA sessions
incorrectly set the default printer to one of the local printers because
the incorrect printer name was sent to the printer command.
This fix resolves the problem.
[#72459]
5. The IMA Service and the MFCOM interface were experiencing a memory
leak. The RPC runtime for Windows 2003 allocates memory for the output
parameter. Because this parameter is defined by the IDL as allocate
(dont_free), the RPC runtime did not free the memory it used to allocate
the pointer when the RPC call was finished.
By changing the attribute from allocate (dont_free) to allocate
(all_nodes), the RPC runtime is forced to delete the data it allocated for
the pointer but not the data that is pointed to by the pointer. The IMA
Service no longer experiences a memory leak.
[#81743]
6. The ICA browser could not be started when running MetaFrame XP Feature
Release 3 on a French Windows 2003 platform and switching into
interoperability mode. This occurred because one resource string in the
French Windows 2003 platform was incorrect.
This fix ensures that the French resource string is correct.
[#82723]
7. The Kana lock state of Japanese IME turned off unexpectedly when focus
was on an ICA session connecting to a MetaFrame/Windows Server 2003.
On Windows Server 2003, the Terminal Service checks the keyboard attribute
before notifying the keyboard drivers of the KANA_LOCK status change. Even
though the client had a Japanese keyboard, MetaFrame was not receiving the
KANA_LOCK flag because the client continued to tell Terminal Services to
recognize the attached keyboard as an English 101 keyboard.
With this fix, even when the client has a Japanese keyboard, the Kana lock
state is preserved.
[#82739]
8. Users could not print using the Novell iprint (Internet) client. In
addition, users could not print using any Internet printer with names that
contained http://, https://, or ipp://. A print job initiated in a session
for one of these printers spooled to the server?s print queue but never
reached the client?s local print queue.
Windows 2003 does not allow printer names to contain backslashes. During
printer creation on the server, backslashes ( \ ) are stored as forward
slashes
( / ). When autocreated printers are initialized, the forward slashes are
converted to backslashes. This process changed the names of pirnters that
contained http://, https://, or ipp://.
This fix preserves Internet printer substrings that are of the form
http://, https://, and ipp://. Printer jobs queued to Internet-based
printers now print with no problem.
[#83548]
9. Users were not always able to switch between seamless application
windows after reconnecting to a session. This happened when the global
system time-out value that sets the amount of time following user input
during which the system does not allow applications to force themselves
into the foreground was not successfully set to 0. Applications could not
set the time-out value unless they owned the foreground window.
This fix corrects the issue.
[#86405]
10. After reconnecting to disconnected seamless sessions, the foreground
window logic sometimes became invalid in Windows 2003 Server environments.
This fix ensures that after reconnecting, users can successfully get any
seamless window into the foreground.
[#86485]
11. Because of changes in Microsoft?s IDL compiler (MIPL) in Visual
Studio.Net, IMA RPC communications exposed an error in the Microsoft RPC
runtime that created a memory leak in the IMA Service.
This fix changes the behavior of Microsoft ?s IDL compiler in Visual
Studio.Net to revert to generating mixed mode stubs for the IMA RPC
functions and the memory leak in the IMA Service no longer occurs.
[#86641]
12. If users had several seamless windows open in a session that supports
the Windows XP Themes and Shaped Windows feature and they resized,
maximized, and restored the windows multiple times, occasionally the
seamless windows were not fully redrawn or even disappeared completely
from the screen. The support of ?shaped? windows requires that extra
information be delivered from the server to the client. Occasionally, this
information arrived at the client in the incorrect order, causing the
windows on the client to be drawn incorrectly.
This fix ensures that the extra information required for rendering
?shaped? windows arrives in a proper sequence so that the windows are
correctly redrawn on the client.
[#86943]
13. If a new connection was started upon a failure to reconnect to a
disconnected seamless connection, the original disconnected seamless
window was not always properly displayed.
This fix corrects the issue.
[#87317]
14. Seamless application windows did not display correctly after session
reconnection if an application running in the session was unresponsive.
This fix corrects the issue.
[#90739]
15. The following autocreated printers failed to print in client sessions
on servers running Windows Server 2003:
Epson LQ-570 ESC/P 2
Epson LQ-870 ESC/P 2
Epson LQ-1170 ESC/P 2
Epson SQ-870 ESC/P 2
Epson SQ-1170 ESC/P 2
HP Business Inkjet 2230/2280
HP DesignJet 750C (E/A0) Color
HP LaserJet 5/5M - PS
HP LaserJet 5/5M - Standard
Epson Stylus COLOR 800 ESC/P 2
Epson Stylus COLOR 850 ESC/P 2
This occurred because the incorrect printer name was sent to the client.
This fix corrects the issue.
[#91223]
16. Client printing failed for applications published on computers running
Windows Server 2003 if those applications were accessed through a
pass-through client published on computers running Windows 2000 Server.
This occurred because the incorrect client printer name was passed from
the server to the client.
This fix introduces a registry setting that enables printing from
applications published on computers running Windows Server 2003 when
accessed from pass-though sessions on computers running Windows 2000
Server. To enable this functionality, set the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Cdm\Parameters
Name: PassThroughW2kOnly
Type: REG_DWORD
Data: 1
[#92149]
Installation Instructions
Note: This service pack is packaged with Microsoft Windows Installer. You
can deploy this package to a group of servers using Microsoft Active
Directory Group Policy Object or using Citrix Installation Manager. For
more information, see the MetaFrame Presentation Server Administrator?s
Guide or the Citrix Installation Manager Administrator?s Guide.
1. Download the service pack from the Hotfixes and Service Packs page of
the Citrix Web site at http://www.citrix.com.
2. Copy the service pack 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.
Using Add/Remove Programs in Control Panel
1. Ensure no CDs or floppy diskettes are in the server.
2. From Add/Remove Programs in Control Panel, select Add New Programs.
3. Select CD or Floppy.
4. Enter the path to the service pack or use the Browse button to select
the service pack.
5. Follow the the Install wizard to complete the installation.
Using the Command-Line with Msiexec
1. At a command prompt, type the following command to install the service
pack:
msiexec /update C:\mfxpsp4.msp
2. Follow the Install wizard to complete the installation.
Note: You can perform the installation silently by using the /qn switch:
msiexec /update C:\mfxpsp4.msp /qn
Using Active Directory
Note: Redeployment of a patched administrative image is not supported.
However, you can use the following method of deployment using Active
Directory:
1. Install the Windows 2000 or 2003 Resource Kit.
2. At a command prompt, type the following commands to create an
Install.bat file:
cusrmgr -dgg GroupName -m \\DomainController -u Domain\%COMPUTERNAME%$
msiexec /p \...\mfxpsp4.msp /qn
3. Launch the Microsoft Management Console (MMC) and add the Active
Directory Users and Computers snap-in.
4. From the View menu, select Users, Groups and Computers as containers,
and Advanced Features.
5. Remove all users, computers, group policies, and sub-Organization Units
(OU) from the OU. Right-click the OU and select New > Group. Create a new
group called YourName_Group.
6. Right-click YourName_Group, select Properties, and then the Security
tab. Add YourName_Group and grant yourself Read, Write, and Add/Remove
self as member permissions.
7. From the Members tab, add the desired servers to the group and click
OK.
8. Right-click the OU and select Properties > Group Policy.
9. Remove a new Group Policy Object; select Properties and then Security.
10. Add YourName_Group and grant yourself Read, Write, and Apply Group
Policy permissions.
11. Remove Apply Group Policy permission from all other users on the list
and click OK.
12. Click Edit and select GPO_Name > Computer Configuration > Windows
Settings > Scripts (Startup/Shutdown) > Startup.
13. Add the Install.bat file as a startup script. Wait several minutes and
restart the computer.
Using Citrix Installation Manager
Note: While installation of Service Pack 4 is supported using Citrix
Installation Manager, uninstallation is not. You need to employ a
different method of uninstallation, such as through Add/Remove Programs or
from the command line.
1. Place the service pack on a network share.
2. Open the Citrix Management Console.
3. Select Installation Manager > Packages.
4. Right-click Packages and select Add Package.
Note: If this is the first time you are using Installation Manager, you
may be prompted to specify a network account. Specify a user who has
access to the network share where the service pack resides.
5. Enter the path for the service pack or select it using the Browse
function. The service pack is listed under Packages.
6. Right-click the service pack and select Install Package.
7. Specify the servers where you want to deploy the service pack.
8. Specify the remaining options and click Finish.
Uninstallation Instructions
Using Add/Remove Programs from Control Panel
1. From Add/Remove Programs in Control Panel, select MetaFrame XP, Service
Pack 4.
2. Click Change/Remove.
3. Follow the Install wizard to complete the installation.
Using the Command Line with Msiexec
1. From a command prompt, obtain the Patch and Product codes for the
service pack and base MetaFrame XP product using the cpatch command:
cpatch /r
******************Product Information******************
ProductName = Citrix MetaFrame XP Server for Windows with Feature Release
3
ProductCode = {05095D7E-4BA8-405F-A751-5C5C18BF5045}
ProductLanguage = 1033
ProductVersion = 1.3.0
cpatch /i C:\mfxpsp4.msp
******************Hotfix Information******************
HotfixName = MFXPServicePack4
HotfixLocalPackage = C:\WINNT\Installer\23a7e5.msp
PatchCode = {FD875D10-3027-4D3C-953A-999745109989}
2. Use the Patch and Product codes with msiexec to uninstall the patch as
follows:
msiexec /uninstall {PatchCode} /package {ProductCode}
Note: You can perform the installation silently by using the /qn switch:
msiexec /uninstall {PatchCode} /package {ProductCode} /qn
Using Active Directory
Note: Redeployment of a patched administrative image is not supported.
However, you can follow the uninstallation method below using Active
Directory.
1. At a command prompt, type the following commands to create an
Uninstall.bat file:
cusrmgr -dgg GroupName -m \\DomainController -u Domain\%COMPUTERNAME%$
msiexec /uninstall \...\mfxpsp4.msp /i \\...\mfxp001.msi /qn
2. Launch the Microsoft Management Console (MMC) and add the Active
Directory Users and Computers snap-in.
3. From the View menu, select Users, Groups and Computers as containers,
and Advanced Features.
4. Remove all users, computers, group policies, and sub-Organization Units
(OU) from the OU.
5. Right-click the OU and select New > Group. Create a new group called
YourName_Group. Right-click YourName_Group, select Properties, and then
Security. Add YourName-Group and grant yourself Read, Write, and
Add/Remove self as member permissions.
6. From the Members tab, add the desired servers to the group and click
OK.
7. Right-click the OU and select Properties > Group Policy.
8. Remove a new Group Policy Object; click Properties, and then Security.
9. Add YourName_Group and grant yourself Read, Write, and Apply Group
Policy permissions.
10. Remove Apply Group Policy permission from all other users in the list
and click OK.
11. From the Edit button, select GPO_Name > Computer Configuration >
Windows Settings > Scripts (Startup/Shutdown) > Startup.
12. Add the Uninstall.bat file as a startup script; wait several minutes
and restart the computer.
Using the Command-Line with CPatch
1. From a command prompt, type the following to uninstall the service
pack:
cpatch /u C:\mfxpsp4.msp
2. Follow the Uninstall wizard to complete the uninstallation.
********************************************************
This Weeks Sponsor SeamlessPlanet.com Domain Names
Register your .com domain name for as low as $7.85
One of the lowest prices on the web! Part of The Kenzig Group.
http://www.seamlessplanet.com
**********************************************************
Useful Thin Client Computing Links are available at:
http://thin.net/links.cfm
ThinWiki community - Awesome SBC Search Capabilities!
http://www.thinwiki.com
***********************************************************
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: CTX104982 - Readme - Service Pack 4 for Metaframe XP 1.0
