Readme file name: MF_XP_FR3_SP4_en.htm
For: MetaFrame XP for Windows
Date: May, 2005
Language supported: English (US)
Readme Version 1.3
This service pack replaces the following hotfixes for Windows 2000 Server:
XE103W2K001, XE103W2K002, XE103W2K003, XE103W2K005, XE103W2K006, XE103W2K007, XE103W2K008, XE103W2K009, XE103W2K010, XE103W2K011, XE103W2K013, XE103W2K015, XE103W2K016, XE103W2K019, XE103W2K020, XE103W2K021, XE103W2K022, XE103W2K023, XE103W2K024, XE103W2K025, XE103W2K026, XE103W2K027, XE103W2K028, XE103W2K029, XE103W2K030 XE103W2K031, XE103W2K032, XE103W2K033, XE103W2K034, XE103W2K035, XE103W2K036, XE103W2K037, XE103W2K038, XE103W2K039, XE103W2K040, XE103W2K041, XE103W2K042, XE103W2K043, XE103W2K044, XE103W2K045, XE103W2K046, XE103W2K047, XE103W2K048, XE103W2K050, XE103W2K054, XE103W2K055, XE103W2K056, XE103W2K057, XE103W2K058, XE103W2K060, XE103W2K061, XE103W2K063, XE103W2K064, XE103W2K065, XE103W2K066, XE103W2K067, XE103W2K068, XE103W2K069, XE103W2K070, XE103W2K071, XE103W2K072, XE103W2K073, XE103W2K078, XE103W2K080, XE103W2K081, XE103W2K082, XE103W2K084, XE103W2K085, XE103W2K086, XE103W2K087, XE103W2K088, XE103W2K089, XE103W2K090, XE103W2K091, XE103W2K092, XE103W2K093, XE103W2K094, XE103W2K095, XE103W2K096, XE103W2K097, XE103W2K098, XE103W2K099, XE103W2K100, XE103W2K101, XE103W2K102, XE103W2K103, XE103W2K104, XE103W2K105, XE103W2K106, XE103W2K107, XE103W2K108, XE103W2K109, XE103W2K110, XE103W2K111, XE103W2K112, XE103W2K113, XE103W2K114, XE103W2K115, XE103W2K116, XE103W2K117, XE103W2K118, XE103W2K119, XE103W2K120, XE103W2K121, XE103W2K122, XE103W2K123, XE103W2K124, XE103W2K125*, XE103W2K126, XE103W2K127, XE103W2K128, XE103W2K129**, XE103W2K130
This service pack replaces the following hotfixes for Windows Server 2003:
XE103W2K3002, XE103W2K3003, XE103W2K3004, XE103W2K3005, XE103W2K3006, XE103W2K3007, XE103W2K3008, XE103W2K3009, XE103W2K3010, XE103W2K3011, XE103W2K3012, XE103W2K3013, XE103W2K3014, XE103W2K3015, XE103W2K3018, XE103W2K3020, XE103W2K3022, XE103W2K3023, XE103W2K3024, XE103W2K3026, XE103W2K3028, XE103W2K3029, XE103W2K3030 XE103W2K3031 XE103W2K3032 XE103W2K3034 XE103W2K3035 XE103W2K3036 XE103W2K3037 XE103W2K3038, XE103W2K3039* XE103W2K3043**
*See Known Issues for information regarding Hotfixes XE103W2K125 and XE103W2K3039.
** See Known Issues for information regarding Hotfixes XE103W2K129 and XE103W2K3043.
Important: After installing this service pack, the Citrix Management Console no longer displays a list of Microsoft hotfixes installed on servers in the farm. To view a list of Microsoft hotfixes installed on a server, see Add/Remove Programs in the Control Panel.
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:
Issues Resolved in Service Pack 4
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.
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
• 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 CTX104546 – Updating ICA Web Clients for Deployment through Web Interface
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 CTX103754 – Client for 32-bit Windows Administrator's Guide - Version 8.x
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
• The Citrix Web Console fails to install after Service Pack 4 is applied. 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
Important: After the Citrix Web Console is installed, make sure you return the registry entry to the original value.
• 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.
• When downgrading from the English and Japanese versions of Service Pack 4 to Service Pack 3, if the upgrade path to Service Pack 4 was either of the following, errors occurred and the IMA Service failed to start:
MetaFrame XP 1.0 > Service Pack 3 > Service Pack 4
MetaFrame XP 1.0 > Feature Release 1 > Service Pack 3 > Service Pack 4
You can ignore the errors and proceed with logon. After logon, the downgrade process completes, resolving the errors and the IMA Service can be manually restarted by executing the following command at a command prompt:
net start imaservice
• When attempting to upgrade to the English version of Service Pack 4 from MetaFrame XP Feature Release 3, the following error message may appear if you are using a transform to change the CLIENT_UPGRADE property to No:
"The installer has encountered an unexpected error installing this package. This may indicate a problem with this package."
The error number is 2869. You can resolve this error by changing the CLIENT_UPGRADE property to Yes.
• The Citrix Web Console and Citrix Management Console Service Pack 4 patches contain an issue where CPatch.exe is deleted upon uninstallation. This occurs when there are multiple patches on one machine. This issue was found in the English version of Service Pack 4; however, it will not be fixed in any language.
• Installing the English and Japanese versions of Service Pack 4 using the command-line restart suppression /norestart or reboot=reallysuppress msiexec does not work. Following installation of Service Pack 4, restart is always forced.
• After Service Pack 4 is uninstalled and the server is restarted, an error message appears stating that Regappex.dll and Brapi.dll cannot be found. In addition, the IMA Service fails to start. When users (administrators) log on, they are prompted for the original Feature Release 3/Service Pack 3 media and the installer requests a restart of the server. If the user clicks Yes, the server continues to log on the user but the server does not restart. The IMA Service does not start until the administrator manually starts the service or restarts the server.
This issue is present only if MetaFrame XP 1.0 Feature Release 3/Service Pack 3 was upgraded from a previous version of the product including MetaFrame XP 1.0 or MetaFrame XP 1.0 with Feature Release 2.
• Note: The following issue affects only the English and German versions of Service Pack 4.
After installing Service Pack 4, certain Feature Release 3/Service Pack 3 hotfixes are not always removed from Add or Remove Programs in the Control Panel and from the registry. The dialog box providing the location of the Amazonhotfix.txt file did not appear and the file was not always created when uninstalling Service Pack 4 if the service pack was installed on a server containing Feature Release 3/Service Pack 3 hotfixes. Some universioned binaries were not being updated during the installation of Service Pack 4.
A hotfix to correct this issue will be released shortly.
Issues Resolved in Service Pack 4
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. The code 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. ICA sessions became unresponsive or failed entirely under heavy use. This was the result of a heavy lock contention.
Installation of this service pack reduces the lock contention and results in somewhat better performance under heavy load.
[#98670]
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 a
