[THIN] KB: CTX105682 - MetaFrame Presentation Server 4.0 Fixed Issues EN
- From: "Jim Kenzig http://thethin.net" <jimkenz@xxxxxxxxxxxxxx>
- To: thin@xxxxxxxxxxxxx
- Date: Thu, 19 May 2005 18:44:14 -0700 (PDT)
CTX105682 - MetaFrame Presentation Server 4.0 Fixed Issues EN
This document was published at:
http://support.citrix.com/kb/entry.jspa?externalID=CTX105682
Document ID: CTX105682, Created on: May 11, 2005, Updated: May 17, 2005
Products: Citrix Presentation Server 4.0 for Microsoft Windows 2000, Citrix
Presentation Server 4.0 for Microsoft Windows 2003
Issues Fixed in this Release
Citrix Presentation Server for Windows
Current Product: Presentation Server 4.0; Presentation Server 3.0, Service Pack
2005.4
Previous Product Version: 3.0
Language: English (EN)
Fixed Issues List: 1.0
The following issues have been fixed since the previous release of this
product. For information about new features and system requirements, see the
product administration guides.
Caution! Several items in this list may require you to edit the registry. Using
Registry Editor incorrectly can cause serious problems that may require you to
reinstall your operating system. Citrix cannot guarantee that problems
resulting from the incorrect use of Registry Editor can be solved. Use Registry
Editor at your own risk.
Citrix Presentation Server 4.0 for Windows 2000 Server
Citrix Presentation Server 4.0 for Windows Server 2003
Conferencing Manager for Citrix Presentation Server
Citrix Presentation Server 4.0 for Windows 2000 Server
1. The MFCOM SDK function IMetaFrameWinApp::Validate reported a failure when a
modified published application was passed in as an argument even though the
application was valid. This occurred because the MFCOM SDK function could not
handle modified applications.
With this fix, the MFCOM SDK function IMetaFrameWinApp::Validate does not
report a failure when a modified published application is passed in as an
argument if the application is valid.
[From Hotfix MPSE300W2KR03][#84231]
2. By default, the IMA Service uses UTF8 to communicate with an Oracle
database. For Japanese double-byte characters, the variable NLS_LANG is set to
JA16SJIS (Shift+JIS) and the IMA Service cannot communicate with the Oracle
database.
If you have not migrated your data store, use the following command:
DSMAINT MIGRATE /SRCDSN:dsn1 /SRCUSER:user1 /SRCPWD:pwd1 /DSTDSN:dsn2
/DSTUSER:user2 /DSTPDW:pwd2 /RECREATEINDEX
If you have already migrated your data store, run the following command to
rectify the issue:
DSMAINT RECREATEINDEX /DSN:dsn /USER:user /PWD:pwd
[From Hotfix MPSE300W2KR03][#86413]
3. After a server was running for an extended period of time, the IMA Service
became exceptionally large, exhausting system resources. This was caused by a
memory leak in the IMA Service.
[From Hotfix MPSE300W2KR03][#88583]
4. Some Installation Manager packages could not be deleted from their package
group.
[From Hotfix MPSE300W2KR03][#90796]
5. Copying session content to the local device failed.
[From Hotfix MPSE300W2KR03][#90826]
6. Users accessing Distributed File System (DFS) based file shares did not get
redirected to other replicas if the active DFS share became inaccessible.
[From Hotfix MPSE300W2KR03][#91067]
7. Charts and graphs, and selected ranges of cells in Microsoft Excel
spreadsheets experienced excessive flickering if SpeedScreen Latency Reduction
and Local Text Echo were enabled.
[From Hotfix MPSE300W2KR03][#91818]
8. On occasion, ICA sessions did not assume a disconnected state when ICA
Keep-Alive was enabled. This occurred because ICA KeepAlive packets relied on
TCP retransmission time-outs rather than a client response to detect when a
client disconnected.
[From Hotfix MPSE300W2KR03][#92145]
9. In the Presentation Server Console, published applications that did not have
a 16x16 or 32x32 pixel icon showed the Citrix icon by default. This occurred
because the algorithm responsible for displaying the application icon only
recognized 16x16 and 32x32 pixel icons.
This fix corrects the issue so that application icons with different dimensions
are displayed properly.
[From Hotfix MPSE300W2KR03][#92320]
10. In large farms, when replicating an updated version of a printer driver to
a server that was using a previous version of the same driver, the update
failed on the destination server even though the event viewer on the source
server reported the update as successful. This occurred because the two
versions of the specific driver had inconsistent printer monitor configuration
information in the registry.
This fix corrects the issue by forcing the installation of the print monitor on
the destination server. If the monitor is not already installed, installation
is performed; otherwise, the driver installation process simply skips this step
and continues as expected.
[From Hotfix MPSE300W2KR03][#92899]
11. With SpeedScreen Multimedia Acceleration enabled, video files occasionally
stopped playing before all frames were rendered. The issue occurred because
with the default implementation of the underlying DirectShow technology,
servers stopped playing multimedia files when a timer expired. The timer was
calculated based on the multimedia file length. Due to network latency, a
client would start to render frames several seconds after the server started to
generate them. When the server stopped playing, several seconds worth of frames
remained to be rendered but did not.
This fix corrects the issue by modifying the default implementation of
DirectShow so that servers continue playback until the client finishes playing
all frames.
[From Hotfix MPSE300W2KR03][#92986]
12. If extended characters were used in elements of a seamless window, such as
window titles or the notification area (system tray), the characters may have
displayed incorrectly if the server's system code page was different from the
client's. This occurred because the extended characters were not translated
accurately between server and client.
[From Hotfix MPSE300W2KR03][#94146]
13. Enumerating users from the shadow taskbar failed for sessions with session
IDs greater than 255. This occurred because the session IDs were being
truncated to a single byte.
[From Hotfix MPSE300R02W2K001][#94401]
14. Connecting to servers over RDP caused excessive querying of the
SessionTimeZone registry key. This occurred because the code did not discern
between ICA and RDP sessions. For RDP sessions, the queries are unnecessary.
This fix introduces support for limiting the queries to ICA sessions so they do
not occur for RDP sessions. To limit the queries to ICA sessions, set the
following registry key::
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\CtxHook\AppInit_Dlls\Per Session Time Zone
Name: Flag
Type: REG_DWORD
Data: 00000014
[From Hotfix MPSE300W2KR03][#98019]
15. The 'Í' (AltGr+T) and 'í' (AltGr+J) keys did not work as expected on an HP
Windows CE device on a Hungarian keyboard layout. A previous fix for this
problem did not take into account that there are two ways to produce these
keys.
This fix ensures that both methods of producing these keys is available.
[From Hotfix MPSE300W2KR03][#98267]
16. On occasion, copying content from local applications and pasting them in
published applications failed on multiprocessor servers. This was caused by
exclusive access blocking for multithreading.
This fix corrects the issue by restricting exclusive access blocking while you
put data on the clipboard.
[From Hotfix MPSE300R02W2K003][#98286]
17. If Microsoft Outlook was limited to one instance per user and you closed
Outlook but kept an email attachment open, Outlook refused to open again as
long as the attachment was open. After closing the attachment, you could open
Outlook again. This occurred because application limits were not enforced
properly.
This fix corrects the issue. It also introduces a change in behavior so that
Management Console application limits are no longer tracked for applications
that exit immediately after spawning other applications, such as, for example,
write.exe.
[From Hotfix MPSE300W2KR03][#98468]
18. Using Installation Manager, modifying the command line properties of a
package failed for custom network administrators, and an error message appeared
instead. This occurred because the Installation Manager subsystem was using the
default network rather than the custom network administrator account.
[From Hotfix MPSE300W2KR03][#99106]
19. The IMA Service could not be stopped on a remote server that had
experienced a ticket request time-out. The issue occurred because of a
dependency of various services.
[From Hotfix MPSE300W2KR03][#100159]
20. A memory leak was caused by a custom Terminal Services API to enumerate
processes.
[From Hotfix MPSE300W2KR03][#100466]
21. In farms with more than one server, smart card users could not reconnect to
disconnected sessions. This occurred because sessions of smart card users were
not associated with actual user or computer names, and therefore the server
hosting the disconnected session could not be identified.
[From Hotfix MPSE300W2KR03][#101409]
22. The printer driver replication feature updated the driver file's creation,
modification, and access date/time stamps to the current date and time when the
file was received by each server on the distribution list.
This fix corrects the issue so that the original date/time stamps of the driver
file are preserved.
[From Hotfix MPSE300W2KR03][#102960]
23. On occasion, the IMA Service became unresponsive unexpectedly. The issue
was caused by a function with an invalid message handle.
[From Hotfix MPSE300W2KR03][#103129]
24. This fix introduces a code change to increase code efficiency in
replicating printer drivers.
[From Hotfix MPSE300W2KR03][#103189]
25. The CtxWinStationQueryClientAddressA and CtxWinStationQueryClientAddressW
APIs would fail unexpectedly and return an ERROR_INSUFFICIENT_BUFFER(0x7a)
error. The issue occurred because a wrong command code parameter passed to a
WinStation API within those CtxWinStation APIs caused the WinStation API to
detect that the corresponding output buffer was too small.
[From Hotfix MPSE300W2KR03][#103222]
26. If a server had more than one network interface card (NIC), but not all
cards were bound to ICA-TCP listeners, incoming ICA connections were attempted
on all NICs, including those not bound to ICA-TCP listeners. This occurred
because Presentation Server operated under the assumption that all NICs were
bound to ICA-TCP listeners.
[From Hotfix MPSE300W2KR03][#104098]
27. Occasionally, when converting from Windows NT 4.0-format (domain\user) user
names to UPN-format (user@xxxxxxxxxxxxxxxx) user names, the IMA Service
unexpectedly became unresponsive. The issue occurred because the reference
count for certain COM objects were incorrect and caused a DLL to be unloaded.
[From Hotfix MPSE300W2KR03][#104398]
28. Restarting the IMA Service sometimes produced an error message even though
the operation itself succeeded. The issue was caused by a dependency between
the IMA Service and other services.
This fix corrects the issue by removing the dependency.
[From Hotfix MPSE300W2KR03][#104452]
29. Under MFCOM SDK 3.0, calling SpeedScreen plus LoadData SaveData more than
once caused a 0x80010105 error. The issue was caused by an object reference
count that was incorrectly incremented.
[From Hotfix MPSE300W2KR03][#104521]
30. Disconnected sessions were displayed as active or not displayed at all in
the Presentation Server Console.
[From Hotfix MPSE300W2KR03][#104720]
31. If corrupt entries were in the policy table, enumeration failed. For
example, if there were two valid entries and one invalid one, the valid data
was ignored. When this occurred, users could not view, add, or modify any
policies. This was caused by corrupt data nodes in the policy table.
Now when enumerating the policy table, any invalid records are skipped and
users can continue to manipulate the policy table.
[From Hotfix MPSE300W2KR03][#104869]
32. When restarting computers running Windows Server 2003, error messages 9017
and 9018 appeared in the system event log, indicating that the license server
could not be found even if the license server was up and running. The issue was
caused by a dependency between the termservice service and other services.
[From Hotfix MPSE300W2KR03][#104890]
33. The Citrix IMA and XML Services were consuming a lot of server CPU time at
the expense of other tasks. This occurred primarily because of periodic updates
made to the data store resulting from changes in the domain trust information.
After the updates were made, the user management subsystem was notified of the
changes and updated its tables accordingly. In a large environment with a large
number of domains this could impact the CPU utilization of the IMA service when
trust changes occurred.
This fix corrects the issue by queuing notification requests and by updating
the tables more efficiently when multiple requests are received.
To queue notification requests, set the following registry keys:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\IMA\IMA_AAMS
Name: UpdateLatency
Type: REG_DWORD
Data: Range = 10 minutes (000927C0) to 120 minutes (6DDD00). Use of any larger
value may produce unexpected results.
Name: PollingInterval
Type: REG_DWORD
Data: Range = 6 hours (1499700) to 7 days (240C8400). Use of any larger value
may produce unexpected results.
Note: UpdateLatency controls how long the IMA service will queue requests
before updating its table of domain trust information for other servers in the
farm. PollingInterval controls how frequently the IMA service will query for
trust changes. The following example shows how to set the UpdateLatency and
PollingInterval to 10 minutes and 7 days, respectively:
Name: UpdateLatency
Type: REG_DWORD
Data: 000927C0
Name: PollingInterval
Type: REG_DWORD
Data: 240C8400
[From Hotfix MPSE300W2KR03][#106642]
34. Under MFCOM SDK 3.0, retrieving the server name after initialization of the
server object using the InitByServerID function did not work even if the server
was initialized with a valid ID object. The issue occurred because a member
variable of the server object was not being filled with the correct value in
the InitServerByID function.
[From Hotfix MPSE300W2KR03][#106798]
35. Servers on which SpeedScreen Browser Acceleration was enabled would
unexpectedly restart at periodic intervals with memory dumps indicating the
vdtw30.dll video driver to be at fault. The issue occurred due to improper
error handling when older clients, which do not support ThinWire2 mode, were
connected to the servers in ThinWire1 mode.
[From Hotfix MPSE300R02W2K002][#108173]
36. Shadowing did not work when shadow logging was enabled. This occurred
because of a code error.
This fix corrects the issue.
[From Hotfix MPSE300R02W2K001][#108658]
37. Under MFCOM SDK 3.0, calling SpeedScreen through the IMetaFrameWinFarm5
interface would sometimes cause an error. The issue was caused by an object
reference count that was incorrectly incremented.
[From Hotfix MPSE300W2KR03][#108915]
38. This feature enhancement adds support for running Microsoft Rights
Management Services (RMS) for Windows on computers running Presentation Server.
Previously, running the RMS client on such computers resulted in the display of
the following error message:
"Cannot verify user information at this time. Contact your administrator if
this problem continues".
The issue was caused by a DLL that was interfering with the RMS client.
To enable this enhancement, you must set the following registry key:
HKEY_LOCAL_MACHINE\Software\Citrix\CtxHook
Name: Flags
Type: REG_DWORD
Data: 0
[From Hotfix MPSE300W2KR03][#108993]
39. Servers may have experienced a KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e) blue
screen when clients utilized the ThinWire1 virtual channel by connecting at low
resolution and low color depth. For example, a client connecting at less than
800x600 pixels and 256 colors may have caused the exception. This occurred
because of an invalid handle.
[From Hotfix MPSE300R02W2K002][#110106]
40. The CHANGEFARM (chfarm) utility failed to join a new server to a farm when
using a fully qualified domain name (FQDN) or an IP address. Connections using
a NetBios name were successful and the server was able to join the new farm.
The issue occurred because a transport command did not support FQDNs or IP
addresses.
This fix adds support for FQDNs and IP addresses to the chfarm utility.
[From Hotfix MPSE300W2KR03][#110427]
41. When logging on to a session using non-smart card credentials and
subsequently inserting a smart card, the session may have become unresponsive.
This occurred because the Microsoft Smart Card Resource manager, resident on
the client device, blocks certain commands while a transaction is pending. If
the server was forwarding commands while such transactions were pending, the
commands would be blocked on the client and result in session unresponsiveness.
This fix corrects the issue in that server commands are now held on the server
until the related client side transaction has completed.
[From Hotfix MPSE300W2KR03][#110436]
42. Implementing a smart card removal policy to lock a client device caused all
ongoing ICA sessions from that device to be disconnected. This feature
enhancement introduces support for a registry entry that allows ongoing
sessions to remain connected while such policy is being implemented. To prevent
ongoing sessions from being disconnected while you implement a smart card
removal policy, set the following server-side registry key using regedt32.exe:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\SmartCard
Name: ScLockNoDisc
Type: REG_SZ
Data: 1
[From Hotfix MPSE300W2KR03][#111680]
43. After installing Hotfix Rollup Pack MPSE300W2KR02 and restarting the
server, ICA connections were refused and the following message may have
appeared:
"A problem with Terminal Services functionality has been corrected on the
server running Presentation Server. The correction involves changes to the
registry. Please reboot the server."
This happened if the RDP-TCP listener was deleted before you installed Hotfix
Rollup Pack MPSE300W2KR02.
This issue was corrected in Hotfix Rollup Pack MPSE300W2KR03.
[From Hotfix MPSE300W2KR03][#112020]
44. Smart Card applications run within an ICA session may have exhibited
different behavior than when run in an RDP session. This occurred, in part,
because additional time had been added to certain time-outs in an attempt to
minimize network traffic resulting from polling smart cards. Additionally,
error codes were different based on the session protocol.
This fix corrects the issue in that it applies time-outs as specified by smart
card vendors, and returns error codes that more accurately represent the smart
card state.
[From Hotfix MPSE300W2KR03][#112461]
45. When trying to save a Microsoft Excel workbook to a client drive, the
following message appeared:
"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.
[From Hotfix MPSE300W2K016][#72187]
46. When the following registry entry was set, Sehook20.dll was still loaded in
the session:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\Wfshell\TWI
Name: SeamlessFlags
Type: REG_DWORD
Data: 0x4
In certain situations the registry entry was ignored, causing Sehook20.dll to
be loaded despite the registry setting.
This fix ensures that the registry entry is used to determine whether or not to
load Sehook20.dll in the session.
[From Hotfix MPSE300W2K002][#83555]
47. The times shown in the Access Suite Console Historical Metric Graph were
incorrect for timezones other than GMT.
[From Hotfix MPSE300W2K009][#84788]
48. The Citrix Event Provider generated unnecessary disconnected session
alerts.
[From Hotfix MPSE300W2K009][#85174]
49. Server to client content redirection was not functioning properly with URLs
in Microsoft Outlook 2003 published on servers running MetaFrame XP V. 1.0 with
Feature Release 3. When you clicked the URL, the link opened in an instance of
Internet Explorer published on the server rather than the instance installed on
the client device. This was caused by an incorrect registry key setting.
[From Hotfix MPSE300W2KR02][#85707]
50. When reconnecting to a disconnected seamless session, users were unable to
maximize the application window by double-clicking its title bar. Although the
application window did get maximized temporarily, it reverted to its previous
size immediately thereafter.
[From Hotfix MPSE300W2KR02][#87308]
51. Reconnecting to a logged off session from the Web interface while the
Workspace Control feature was enabled may have launched multiple instances of
the same published applications. This was caused by a flaw in the duplicate
session algorithm of the Workspace Control feature.
[From Hotfix MPSE300W2KR02][#87318]
52. Applications were attempting to access a smart card reader attached to the
server instead of the one residing on the client. Depending on the way the CSP
vendor implemented smart card support, the previous mechanism used to hook the
smart card functions didn't always work.
To enable the new smart card hook, you must create or modify the following
registry entries:
1. Open the Registry Editor and navigate to the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\CtxHook\AppInit_Dlls\Smart Card Hook
2. From the Edit menu, select Add Value and enter the following:
Value Name: Flag
Data Type: REG_DWORD
Data: 80000000
3. From the Edit menu, select Add Value and enter the following:
Value Name: FilePathName
Data Type: REG_SZ
Data: scardhook.dll
This fix introduces a new mechanism that minimizes errors by placing the hook
in the DLL function of interest, not every piece of code making a reference to
the DLL function of interest. As a result, users will not see any indication
that an application is attempting to access a smart card reader attached to the
server. The application should be hooked consistently and routed to the smart
card reader attached to the client.
[From Hotfix MPSE300R01W2K004][#87999]
53. Saving a file to a client drive failed if the value of the seconds portion
of the time stamp equaled 59. This occurred because the Client Drive Mapping
feature rounded up the time stamp but failed to propagate the change.
[From Hotfix MPSE300W2K016][#88799]
54. An error occurred when you attempted to launch an application published on
a server running MetaFrame XP V. 1.0 with Feature Release 2 if the server was
located in a zone with a data collector running MetaFrame Presentation Server
3.0. This occurred because the data collector, running Version 3.0 of the
product, was directing an event to an event handler that handles Version 3.0
events only and generates an error when receiving an event from a server
running an earlier version of the product.
[From Hotfix MPSE300W2KR02][#89269]
55. When using the Server Default keyboard setting in Program Neighborhood, the
Input Method Editor (IME) user dictionary was created in an incorrect folder.
[From Hotfix MPSE300R01W2K007][#89688]
56. Due to an access violation, a custom MFCOM application was experiencing a
fatal error while attempting to obtain Citrix virtual channel policy
information. This occurred because the reference count of the wrong MFCOM
object was incremented, which resulted in the original MFCOM object being freed
while it was still in use.
[From Hotfix MPSE300W2KR02][#90079]
57. Each time a user with auto-created printers connected to a server, printed,
and then logged off, the handle count on the spooler service increased. Also,
after the print spooler service had been running for some time on a server to
which many users were connecting with auto-created printers, you could see many
ports not belonging to any active printers under Printers->File->Server
Properties->Ports. This occurred because the auto-created printer ports were
not deleted upon users' logoff or if there was a problem opening the printers.
[From Hotfix MPSE300W2KR02][#90456]
58. When a user tried to publish the latest RDP clients that support Smart
Card, they could not use the published RDP client with a Smart Card. This was
caused by an internal misunderstanding of API functionality.
With this fix, RDP detects Smart Card support properly.
[From Hotfix MPSE300R01W2K004][#90698]
59. Users were sometimes unable to access files or folders with long file names
on mapped client drives and received an error message instead. The issue was
caused by an incompatibility between long file and folder names and session IDs
longer than two characters.
This fix removes the incompatibility.
[From Hotfix MPSE300W2K016][#90860]
60. Requests by SDKs to obtain SpeedScreen Flash Acceleration returned
incorrect values. This occurred because the SDK requests did not call the IMA
Service to update the values.
[From Hotfix MPSE300W2KR02][#91022]
61. Custom programs or scripts calling the MFCOM SDK function
IMetaFrameApplication::WriteIconToFile got an exception.
[From Hotfix MPSE300W2KR02][#91025]
62. The following auto-created printers failed to print in client sessions on
servers running Windows Server 2003:
Epson LQ-570 ESC/P 2
Epson LQ-870 ESC/P 2
Epson LQ-1170 ESC/P 2
Epson SQ-870 ESC/P 2
Epson SQ-1170 ESC/P 2
HP Business Inkjet 2230/2280
HP DesignJet 750C (E/A0) Color
HP LaserJet 5/5M - PS
HP LaserJet 5/5M - Standard
Epson Stylus COLOR 800 ESC/P 2
Epson Stylus COLOR 850 ESC/P 2
This occurred because the wrong printer name was sent to the client.
[From Hotfix MPSE300W2KR02][#91223]
63. Occasionally, servers experienced a fatal error, displaying a blue screen.
This fix introduces a code change that corrects the issue.
[From Hotfix MPSE300R01W2K002][#91404]
64. When writing email in Lotus Notes over low latency connections with Local
Text Echo enabled, text prediction changed to an illegible font.
[From Hotfix MPSE300W2KR02][#91605]
65. In the Presentation Server Console, when you assigned a policy to a group
and then searched by user name for policies assigned to a particular member of
the group, the search result did not include the policy. The issue was caused
by a flaw in the way the IMA user management subsystem enumerates Active
Directory user groups.
[From Hotfix MPSE300W2KR02][#92024]
66. Session sharing failed in mixed Windows/NDS deployments if users were using
the same password for both accounts but the application being launched was only
available to Windows domain users.
[From Hotfix MPSE300W2KR02][#92572]
67. A popup window of a custom application running in seamless mode prompted
the display of a dialog as if Windows Explorer was being launched, when, in
fact, it was not.
[From Hotfix MPSE300W2KR02][#92839]
68. In the Client Update Configuration utility, limits on the number of
simultaneous client updates did not work properly. The limits worked properly
for clients connected with Administrator rights, but simultaneous updates to
clients connected with User rights may have exceed the limit you specified.
[From Hotfix MPSE300W2KR02][#92858]
69. When a client device was locked and you clicked outside the Unlock Computer
dialog box and then clicked inside the dialog box, the User name and Password
text boxes did not respond to keyboard input.
[From Hotfix MPSE300W2KR02][#93099]
70. When accessing a Web page that contained an AlphaImageLoader object in a
published instance of Internet Explorer in Program Neighborhood Version 7.1 or
later, Internet Explorer experienced a fatal error. This occurred because the
presence of the AlphaImageLoader object on the Web page loads a DLL associated
with SpeedScreen Browser Acceleration even if that feature is not enabled. The
fatal error occurred because the DLL's data structures were not initialized
unless SpeedScreen Browser Acceleration is enabled.
This fix modifies the DLL so that it works properly even if SpeedScreen Browser
Acceleration is not explicitly enabled.
[From Hotfix MPSE300W2KR02][#94109]
71. Summary database purge jobs failed if the Oracle database was offline due
to or following, for example, backups. This occurred because the Oracle
listener could not be contacted.
[From Hotfix MPSE300W2K020][#94651]
72. The IMA Service experienced a deadlock. This was caused by the server down
processor not releasing a lock.
[From Hotfix MPSE300W2K020][#96163]
73. Client drive mapping failed if you disabled the "System objects: Strengthen
default permission of internal system objects (e.g. Symbolic Links)" base
system object restriction.
Though disabling the restriction is not recommended, client drive mapping no
longer fails if you disable the restriction after applying this fix.
[From Hotfix MPSE300W2KR02][#96289]
74. Due to different screen resolutions, when shadowing a seamless session you
were unable to locate windows in the session window if you or the shadowee
minimized the session window.
[From Hotfix MPSE300W2KR02][#97204]
75. Occasionally, if one or more of the following policies were enabled,
servers became unresponsive and stopped accepting new connections after running
for several hours. The issue was caused by a memory leak.
? Client Devices>Resources>Drives>Connection>Connect Client Drives at Logon
? Client Devices>Resources>Drives>Connection>Do not Connect Client Drives at
Logon
? Client Devices>Resources>Drives>Mappings>Turn off Floppy disk drives
? Client Devices>Resources>Drives>Mappings>Turn off hard drives
? Client Devices>Resources>Drives>Mappings>Turn off CD-ROM drives
? Client Devices>Resources>Drives>Mappings>Turn off Remote drives
[From Hotfix MPSE300W2KR02][#97536]
76. In the Presentation Server Console, under Installation Manager, the
Schedule Time column on the Jobs tab displayed incorrect dates for packages
scheduled for deployment. The issue was caused by a code error.
[From Hotfix MPSE300R01W2K005][#97644]
77. Occasionally, when a non-Windows client was connecting to a server running
Presentation Server, the server would experience a fatal error. This issue was
caused by unsynchronized access to a global variable by multiple threads.
[From Hotfix MPSE300W2KR02][#97822]
78. When attempting to launch an application published on Windows Server 2003
using NDS credentials, the following message appeared:
"You do not have access to logon to this session."
This occurred because NDS was not properly initialized, which caused user
authentication to fail.
[From Hotfix MPSE300W2KR02][#98490]
79. When trying to establish a pass-through connection from a smart card
authenticated session, you may have received a 1031 virtual driver error.
Separately, smart card developers may have received a 258 or 0x102 error from
the ScardGetStatusChange API when calling with a 0 time-out within a
Presentation Server environment.
This fix introduces a code change to ensure that the proper error code is
returned. Smart card users no longer receive a 1031 virtual driver error when
trying to establish a pass-through connection from a smart card authenticated
session. Also, smart card developers receive a specific SCARD_E_TIMEOUT
(0x8010000A) error code from the ScardGetStatusChange API when calling with a 0
time-out within a Presentation Server environment.
[From Hotfix MPSE300W2KR02][#98511]
80. Occasionally, servers experienced a fatal error, displaying a blue screen.
[From Hotfix MPSE300R01W2K003][#98528]
81. Custom Administrators were unable to add/remove metrics or adjust metric
properties. Error code:c0160ad8 was displayed.
[From Hotfix MPSE300W2K020][#99003]
82. When querying an unresponsive SQL Server, the IMA service did not time out.
As a result, the Management Console was not populated properly and command line
tools such as qfarm and chfarm did not work until you restarted the server.
This fix introduces a new registry entry that allows you to configure an
explicit time-out interval for the IMA service.
Create the following registry entry:
HKEY_LOCAL_MACHINE\\Software\Citrix\IMA
Name: DB_CONNECTION_TIMEOUT
Type: REG_DWORD
Data: <time-out value, in seconds>
[From Hotfix MPSE300R01W2K001][#99277]
83. Users were unable to launch published applications if the Session
Reliability feature was enabled and an option other than All network adapters
with this protocol was configured for the ICA protocol in the Citrix Connection
Configuration utility.
This fix introduces support for session reliability even if you limit a
protocol to a particular network adapter.
To enable this functionality:
1. Open the file httpd.conf, located in the Program Files\Citrix\Xte\conf
folder, in a text editor.
2. Below the line #Citrix_End, add the following line:
CgpSpecifiedIcaLocalAddress <server IP address, for example, 10.8.6.192>
3. Save your changes.
4. Reboot the server.
If you have this functionality enabled, assign a static IP to the server or, if
you are using DHCP, create a script to automatically update the IP address of
CgpSpecifiedIcaLocalAddress in the httpd.conf file. If the IP address of
CgpSpecifiedIcaLocalAddress does not match the actual IP address of the server,
you receive an error stating that there is no route to the specified subnet
address.
[From Hotfix MPSE300W2KR02][#99885]
84. Installation Manager, after installing a package on a server, enabled
logons to that server even if you manually disabled them. This occurred because
Installation Manager, by design, disables logons to a server before installing
a package and then re-enables them when the installation is complete. However,
it ignored the status of the Enable logons to this server option of the
MetaFrame Settings server properties page of the Presentation Server Console
and enabled logons even if that option was disabled.
[From Hotfix MPSE300W2KR02][#100402]
85. Users without Windows user profiles and users whose profile had been
modified, were unable to launch published applications.
[From Hotfix MPSE300W2KR02][#101958]
86. Servers may have experienced a fatal error if you ran Microsoft's Driver
Verifier utility while users were logged on or logging on to the server using
smart cards. This occurred because of a lack of synchronization in the smart
card I/O control cancel handler.
[From Hotfix MPSE300W2KR02][#103495]
87. If the print spooler service stopped during a print job during an ICA
session, logging on to the computer running Presentation 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.
[From Hotfix MPSE300W2K001][#74290]
88. When playing back sound that was recorded inside of a client session, the
last two seconds of the recorded sound was repeated.
This fix resolves the problem.
[From Hotfix MPSE300W2K001][#86157]
89. When pausing the playback of sound inside a client session, it sometimes
took up to 10 seconds for the sound to stop playing in a low-latency network.
This was caused by buffering of audio data on the client resulting in pause
request responses being slow.
To enable the new Delayed Callback mode, you must create the following registry
entry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal
Server\WinStations\ICA-tcp\AudioConfig
Name: CallbackDelta
Type: REG_DWORD
Data: (Citrix recommends you start with a value of five or 10 milliseconds)
This fix ensures that the sound will not continue to play for 10 seconds when
pausing the playback of sound in a client session.
[From Hotfix MPSE300W2K001][#86166]
90. 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 will call only those applications
that are responding. Users can switch to other applications even if one is
unresponsive.
[From Hotfix MPSE300W2K002][#76070]
91. 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.
[From Hotfix MPSE300W2K002][#80221]
92. The display speed of the combo list box became very slow if the list box
expanded beyond the area of the background window. The seamless routine that
checked to determine whether or not the target window was a top-level window
ignored the window, causing a delay in the display of the window.
A new API is now used to determine whether or not the target window is a
top-level window. The combo list box appears as quickly as other types of
windows in a seamless session.
[From Hotfix MPSE300W2K002][#83550]
93. This fix addresses a custom application's performance when run seamlessly.
Some applications appeared to be slower to respond when performing actions such
as moving, resizing, or closing windows. This fix introduces two new registry
settings that allow administrators to configure an explicit time interval for
the seamless engine mechanism to monitor when changes take place in the
seamless applications.
Create the following registry keys:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI
Name: SeamlessFlags
Type: REG_DWORD
Data: 0x4
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI
Name: WorkerWaitInterval
Type: REG_DWORD
Data: <Number of milliseconds allowed> (Values are between 5 ? 500; the default
is 50.)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI
Name: WorkerFullCheckInterval
Type: REG_DWORD
Data: <Number of milliseconds allowed> (Values are between 50 ? 5000; the
default is 500.)
A higher value slows responsiveness but improves scalability; a smaller size
increases responsiveness but decreases scalability slightly. The level of
scalability depends on several factors, such as hardware sizing, types of
applications, network performance, and number of users.
[From Hotfix MPSE300W2K002][#85657]
94. Computers running Presentation Server could not reestablish a connection to
the license server if the IP address of the license server changed. This was
identified as a problem with a third-party SDK.
This fix ensures that computers running Presentation Server can reestablish a
connection to the license server even if the license server's IP address
changes. See Citrix Knowledge Base article CTX103795 for additional
information.
[From Hotfix MPSE300W2K004][#86151]
95. 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.
[From Hotfix MPSE300W2K005][#71243]
96. Users occasionally experienced disconnected sessions when transferring
large amounts of data over low-bandwidth modem connections.
This fix prevents the session from disconnecting.
[From Hotfix MPSE300W2K005][#84837]
97. If the following registry key was set with a non-zero value, servers
occasionally experienced a fatal error when users connected to a server farm:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\Wds\icawd
Name: ActiveLatencyPeriodInSeconds
Type: REG_DWORD
This was caused by an error in timing that resulted in the reuse of a buffer
that was already freed.
This fix ensures that the servers no longer experience a fatal error when
connecting to a server farm even if the registry key is set with a non-zero
value.
[From Hotfix MPSE300W2K005][#87252]
98. Starting with MetaFrame XP Feature Release 3, the server seamless engine
was enhanced to support the Windows XP Theme style. This new functionality was
enabled by default and could not be turned off.
With Windows XP Themes enabled, some custom published applications could not be
displayed or operated properly on Windows XP/2003 clients.
This fix introduces a new seamless global registry flag that, when set,
disables this new functionality as well as the use of client-side metrics. Set
the following server-side registry key to accomplish this:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI
Name: SeamlessFlags
Type: REG_DWORD
Data: 0x4000
Note that this setting forces all published applications to be displayed using
server-side metrics. If the local client-side metrics differ from the
server-side metrics, there will be an inconsistency in the window styles. In
addition, because ICA sessions will not be aware of any client-side metrics,
maximizing windows will ignore any Windows Always On Top toolbar settings.
[From Hotfix MPSE300W2K006][#87052]
99. Installing or uninstalling multiple computers running MetaFrame
Presentation Server 3.0 in large farms failed intermittently and left partial
data in the data store. A SQL transaction did not retry when it failed to get
the record locks it needed.
The retry count was increased across the board to improve robustness in large
farms. Installing or uninstalling multiple computers running MetaFrame
Presentation Server 3.0 in large farms no longer fails.
[From Hotfix MPSE300W2K007][#86168]
Note: The following related updates and hotfixes are also available:
? KB Article Number CTX104813 (pre-installation update): Installing or
uninstalling multiple computers running MetaFrame Presentation Server 3.0 in
large farms failed intermittently and left partial data in the data store. A
SQL transaction did not retry when it failed to get the record locks it needed.
The retry count was increased across the board to improve robustness in large
farms. Installing or uninstalling multiple computers running MetaFrame
Presentation Server 3.0 in large farms no longer fails.
? KB Article Number CTX104817 (optional). This optional utility provides a way
to perform validation checks on a server farm's data store. Results are
displayed on the console and written to the event log. The /Clean option
deletes inconsistent records.
100. If the Presentation Server Console was used to create a policy that had
the rule \Client Devices\Resources\Network Printers\Print Job Routing included
and had Send directly from server to printer enabled in the rule, relevant
print jobs were not being sent directly from the server to the printer. The
rule was not being enforced correctly.
This fix ensures that the rule is enforced correctly and print jobs are being
sent directly from the server to the printer.
[From Hotfix MPSE300W2K008][#84405]
101. The content-redirection for Windows File Type Associations was not reset
when a user modified a (copied) published application's command-line.
This fix ensures that the Presentation Server Console resets the File Type
Association settings whenever a user changes a (copied) published application's
command-line.
[From Hotfix MPSE300W2K010][#87751]
102. If an administrator changed some of a server's settings under ICA Browser
in MetaFrame Settings on the Presentation Server Console and later executed
dsmaint recreatelhc on that server, the changed setting was not retained. After
executing dsmaint recreatelhc, the changed settings were overwritten with
default values in error.
This fix ensures that changed settings on a server are retained after executing
dsmaint recreatelhc on that server.
[From Hotfix MPSE300W2K011][#86011]
103. In interoperability mode, listener values could not be obtained or set
correctly through the MFCOM interface. This occurred 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.
[From Hotfix MPSE300W2K012][#81033]
104. When a least loaded server was unresponsive, the data collector continued
to resolve connections to the server. The data collector sent all new
connection attempts and/or ticket requests to that server even though that
server could not respond to these requests. This sometimes caused the entire
server farm to become unresponsive.
If a server is not responding to a ticket request, the data collector is
notified to update the server's load to maximum. This prevents any new ticket
requests to that server. This prevents an unresponsive least loaded server from
causing a farm to become unresponsive.
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 to the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CtxHttp\SocketTimeout
Name: SocketTimeout
Type: REG_DWORD
Data: Time-out number value in milliseconds
[From Hotfix MPSE300W2KR01][#87613]
105. The ICA browser could not be started when running MetaFrame XP Feature
Release 3 on a French Windows 2003 platform and switching into interoperability
mode. This occurred because one resource string in the French Windows 2003
platform was incorrect.
This fix ensures that all localized resource strings are correct.
[From Hotfix MPSE300W2KR01][#82723]
106. When users connected to a published tool called Microsoft Imaging Software
and chose the pen or highlighter mode, the mouse pointer disappeared from the
document area of the screen. This occurred because the ICA video driver was not
supporting 32-bitmaps for the ICA Client.
This fix ensures that when users connect to a published tool called Microsoft
Imaging Software and choose the pen or highlighter mode, the correct mouse
pointer is displayed in the document area of the screen.
[From Hotfix MPSE300W2K013][#83045]
107. Iexplore.exe sometimes became unresponsive when displaying images in an
ICA session if SpeedScreen browser acceleration was turned on. A SpeedScreen
acceleration routine did not compute the number of image scan lines
sufficiently to store the image check tag correctly, causing a buffer overrun
and leading to an application fault.
This fix ensures that the number of image scan lines is sufficient to store the
image check tag.
[From Hotfix MPSE300W2K013][#87843]
108. When two processes attempted to access a remote smart card reader, all
activity going across the virtual channel stopped. After a time-out period, a
failure would occur on one of the processes and the other would continue. This
occurred because the Microsoft Smart Card Resource Manager blocks certain
commands. If a command was sent from the server while a command from another
process was still in process, activity would stop.
This fix ensures that no additional commands are sent to the client until the
command blocked by the Microsoft Smart Card Resource Manager is released.
Activity will not stop when two processes within a session attempt to access a
remote smart card reader.
[From Hotfix MPSE300W2K014][#83631]
109. A smart card application was requesting status continually or invalid
smart card status was being received. The reader state information maintained
by the Citrix Device Management component was incorrectly updated. In addition
the smart card state data included some non-documented third-party flags that
were being compared.
This fix ensures the reader state information is properly maintained by the
Citrix Device Management component. The smart card application no longer
continually requests status nor is invalid smart card status being transmitted.
[From Hotfix MPSE300W2K015][#85780]
110. A server sometimes experienced a fatal system error caused by Cdm.sys with
bug checkcode 50. This occurred because Cdm.sys occasionally accessed a buffer
out of boundary.
With this fix, Cdm.sys no longer accesses a buffer out of boundary.
[From Hotfix MPSE300W2KR01][#87762]
111. 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 permitted to be sent to the client before
the reconnection sequence has completed.
[From Hotfix MPSE300W2K016][#80574]
112. When logging on to a server using a smart card, users sometimes received
the message, "The system could not log you on. The requested key container does
not exist on the smart card." This issue was caused by a mechanism used to
track smart card based sessions that was incompatible with the way some CSPs
store logon information.
This fix uses a different tracking mechanism that is compatible with the way
those CSPs store logon information.
[From Hotfix MPSE300W2K016][#85648]
113. In client sessions, the playback quality of sound recorded in low-quality
mode over a wide area network (WAN) was poor.
This fix addresses the issue in such a way that the playback is of equal
quality on the client as on the server.
[From Hotfix MPSE300W2K016][#87095]
114. 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.
[From Hotfix MPSE300W2KR01][#72877]
115. 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.
This fix ensures that the installation date will be correct no matter what the
current date is when scheduling occurs.
[From Hotfix MPSE300W2KR01][#76147]
116. If Automatic install of native drivers was disabled, no events were
generated in the event log when printers could not be auto-created.
With this fix, events are generated if printers cannot be auto-created.
[From Hotfix MPSE300W2KR01][#72922]
117. Some printers were not automatically auto-created in an ICA session, and
an Event ID 1107 entry was added to 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 auto-creation should occur without incidents.
[From Hotfix MPSE300W2KR01][#79268]
118. Belgian French keyboard layout with non-Win32 ICA Clients: The following
key combination did not work as expected in several applications:
AltGr + '^' symbol (on the number 6 key)
The Unicode mappings were not properly defined in the Presentation Server
Belgian French keyboard (.kbd) file. This fix corrects the issue, and the key
combination works properly.
[From Hotfix MPSE300W2KR01][#80525]
119. Belgian Dutch keyboard layout with non-Win32 ICA Clients: The following
key combinations did not work as expected in several applications:
AltGr + '?' (euro symbol)
AltGr + '\' (backslash symbol)
The Unicode mappings were not properly defined in the Presentation Server
Belgian Dutch keyboard (.kbd) file. This fix corrects the issue, and the key
combinations work properly.
[From Hotfix MPSE300W2KR01][#80524]
120. Canadian French keyboard layout with non-Win32 ICA Clients: The following
key combinations did not work as expected in several applications:
AltGr + the key next to the left Shift key
AltGr + the third key to the left of the right Shift key
The Unicode mappings were not properly defined in the Presentation Server
Canadian French keyboard (.kbd) file. This fix corrects the issue, and the key
combinations work properly.
[From Hotfix MPSE300W2KR01][#84624]
121. Czech keyboard layout with non-Win32 ICA Clients: The following key
combination did not work as expected in several applications:
AltGr + various keys at the top of the keyboard ( '2' to '+').
The Unicode mappings were not properly defined in the Presentation Server Czech
keyboard (.kbd) file. This fix corrects the issue, and the key combinations
work properly.
[From Hotfix MPSE300W2KR01][#80867, 84630]
122. Dutch keyboard layout with non-Win32 ICA Clients: The following key
combinations did not work as expected in several applications:
AltGr + 'cent' symbol key
AltGr + 'broken bar' symbol key
The Unicode mappings were not properly defined in the Presentation Server Dutch
keyboard (.kbd) file. This fix corrects the issue, and the key combinations
work properly.
[From Hotfix MPSE300W2KR01][#77702]
123. English (Australia) keyboard layout: Keyboard input did not appear in the
SpeedScreen Latency Reduction bubble if English (Australia) was set as the
default locale in an ICA session.
The program failed to load the corresponding keyboard layout DLL if English
(Australia) was set as the default locale. This fix corrects the issue, and the
key combinations work properly.
[From Hotfix MPSE300W2KR01][#84653]
124. Finnish keyboard layout with non-Win32 ICA Clients: The following key
combination did not work as expected in several applications:
AltGr + '|' (pipe symbol, right of left Shift key)
The Unicode mappings were not properly defined in the Presentation Server
Finnish keyboard (.kbd) file. This fix corrects the issue, and the key
combination works properly.
[From Hotfix MPSE300W2KR01][#80868]
125. French keyboard layout with non-Win32 ICA Clients: The following key
combinations did not work as expected in several applications:
AltGr + 'ç/9' symbol key
The Unicode mappings were not properly defined in the Presentation Server
French keyboard (.kbd) file. This fix corrects the issue, and the key
combination works properly.
[From Hotfix MPSE300W2KR01][#80878]
126. Greek keyboard layout with non-Win32 ICA Clients: The following keys and
key combinations did not work as expected in several applications:
AltGr +'?' (euro symbol) and various other keys
Shift + 's' key
's' key did not work with Caps Lock on
Shift + 'h'' key
'h' key did not work with Caps Lock on
Shift + 'w' key
'[' with Caps Lock on turned off the Caps Lock indicator light. Subsequently,
Caps Lock On produced lowercase letters, Caps Lock Off produced uppercase
letters.
The Unicode mappings were not properly defined in the Presentation Server Greek
keyboard (.kbd) file. This fix corrects the issue, and the key combination
works properly.
[From Hotfix MPSE300W2KR01][#84631]
127. Hungarian keyboard layout with non-Win32 ICA Clients: The following keys
and key combinations did not work as expected in several applications:
AltGr + '^' symbol key
AltGr + '?' (euro symbol)
3rd key left of backspace key
'Í' key next to the left Shift key with Cap Locks on
The Unicode mappings were not properly defined in the Presentation Server
Hungarian keyboard (.kbd) file. This fix corrects the issue, and the key
combinations work properly.
[From Hotfix MPSE300W2KR01][#84632]
128. Norwegian keyboard layout with non-Win32 ICA Clients: The following key
combination did not work as expected in several applications:
AltGr +'?' (euro symbol)
The Unicode mappings were not properly defined in the Presentation Server
Norwegian keyboard (.kbd) file. This fix corrects the issue, and the key
combination works properly.
[From Hotfix MPSE300W2KR01][#79182]
129. Polish keyboard layout with non-Win32 ICA Clients: The following keys and
key combinations did not work as expected in several applications:
AltGr + '?' (euro symbol)
3rd key left of backspace key
'ó' key
'|' key
'[' key AltGr + f
']' key AltGr + g
'§' key
The Unicode mappings were not properly defined in the Presentation Server
Polish keyboard (.kbd) file. This fix corrects the issue, and the key
combinations work properly.
[From Hotfix MPSE300W2KR01][#84633]
130. Russian keyboard layout with non-Win32 ICA Clients: The following keys and
key combinations did not work as expected in several applications:
'Ë' key
Key just left of the right Shift key
The Unicode mappings were not properly defined in the Presentation Server
Russian keyboard (.kbd) file. This fix corrects the issue, and the key
combinations work properly.
[From Hotfix MPSE300W2KR01][#84634]
131. Slovak keyboard layout with non-Win32 ICA Clients: The following keys and
key combinations did not work as expected in several applications:
';' key
'[' key
']' key
'7' key
'8' key
'9' key
'=' (dead key)
' (quote symbol to the left of the backspace key)
The Unicode mappings were not properly defined in the Presentation Server
Slovak keyboard (.kbd) file. This fix corrects the issue, and the keys and key
combinations work properly.
[From Hotfix MPSE300W2KR01][#84838]
132. Slovenian keyboard layout with non-Win32 ICA Clients: The following keys
and key combinations did not work as expected in several applications:
'C' key
'?' (euro symbol)
'§' key
Shift + '?' key
Shift + 'd' key
Shift + 'c' key
Shift + '?' key
The Unicode mappings were not properly defined in the Presentation Server
Slovenian keyboard (.kbd) file. This fix corrects the issue, and the key
combinations work properly.
[From Hotfix MPSE300W2KR01][#84636]
133. Spanish (incl. Latin American) keyboard layouts with non-Win32 ICA
Clients: Various keys and key combinations did not work as expected in several
applications.
The Unicode mappings were not properly defined in the Presentation Server
Spanish keyboard (.kbd) file. This fix corrects the issue, and the key
combination works properly.
[From Hotfix MPSE300W2KR01][#84639, 83477]
134. Turkish keyboard layouts with non-Win32 ICA Clients: The following key
combination did not work as expected in several applications:
AltGr +'?' (euro symbol)
'¦' key
Caps Lock + 'g' key
Caps Lock + 's' key
Caps Lock + '?' key
The Unicode mappings were not properly defined in the Presentation Server
Turkish keyboard (.kbd) files. This fix corrects the issue, and the key
combination works properly.
[From Hotfix MPSE300W2KR01][#84640, 84641]
135. Publishing an application from a network share in a different domain and
browsing to the application's icon generated the following error message:
"The icon associated with this published application cannot be accessed. If you
typed in the path to the application executable, check that the path is correct
and that the executable is available," and the icon failed to appear in the
farm.
This fix corrects the issue, the error no longer occurs, and the application
icon appears in the farm as expected.
[From Hotfix MPSE300W2KR01][#78094]
136. In Program Neighborhood, when Active Directory users whose user options
were set to "User must change password at next logon" attempted to log on to an
application set without providing a domain name, their session became
unresponsive.
[From Hotfix MPSE300W2KR01][#80466]
137. Important: To get the benefits of this performance improvement, you must
do the following:
1. Install this fix.
2. Deploy MetaFrame Presentation Server Client for 32-bit Windows, Version
8.100.
3. Set the required registry keys (see below).
Transfers of large files over wide-are networks (WANs) tended to be slow
relative to the available bandwidth. This was caused, in part, by the earlier
design of the drive mapping feature. This fix, along with the MetaFrame
Presentation Server Client for 32-bit Windows, Version 8.100 and requisite
registry entries, results in significant performance gains for large file
transfers over WANs.
This fix resolves the situation by introducing a technique where data is
streamed without continually waiting for acknowledgments.
[From Hotfix MPSE300W2K005][#82457]
138. With replicated SQL databases, the printer mapping changes were not
properly propagated to the server on the subscriber database IMA data store.
This was a result of latency in the underlying database replication.
This fix resolves the problem by populating the Local Host Cache (LHC) with the
printer mapping data and reading the printer mapping data directly from the
LHC, not the data store.
[From Hotfix MPSE300W2KR01][#84528]
139. When an NDS user with an expired password attempted to refresh an
application set, a new, temporary session with an NDS password dialog box
should launch, asking the user to change the password. When the user changed
the password, the temporary session became unresponsive or logged into a
working desktop. The problem occurred when the user options in NDS were set to
User must change password at next logon and the users tried to log on to an
application set through Program Neighborhood using their NDS credentials.
Program Neighborhood launches a session so that users can change their
passwords. While creating this session, the code verifies if the domain name
sent the Program Neighborhood virtual channel is the same as the one obtained
from the logged on user token. The problem occurred because the NDS user name
and context were not being checked.
This fix ensures that NDS credentials will be verified.
[From Hotfix MPSE300W2KR01][#84862]
140. A high number of printer drivers installed on servers caused the Local
Host Cache (LHC) to grow large and caused the synchronization of the drivers in
the data store to the LHC to take a long time.
With this fix, the synchronization logic was changed to speed up
synchronization time.
[From Hotfix MPSE300W2KR01][#85052]
141. This is a request for a feature change enhancement involving the following
three scenarios:
1. If Create browser listener on UDP network was not checked in the
Presentation Server Console, typing qfarm.exe /tcp at a command prompt did not
display the server nor did the server and its IP address appear in the command
qfarm.exe.
2. If Create browser listener on IPX network was not checked in the
Presentation Server Console, typing qfarm.exe /ipx at a command prompt did not
display the server nor did the server and its IP address appear in the command
qfarm.exe.
3. If Create browser listener on NetBIOS network was not checked in the
Presentation Server Console, typing qfarm.exe /netbios at a command prompt did
not display the server nor did the server and its IP address appear in the
command qfarm.exe.
This enhancement ensures that the behavior described in the three scenarios no
longer occurs.
[From Hotfix MPSE300W2KR01][#85071]
142. The IMA Service sometimes experienced a fatal error when an administrator
viewed, added, or deleted users on the node of a published application from the
Presentation Server Console. This occurred because one function of the IMA
Service was not checking the error code correctly.
This fix ensures that the function of the IMA Service correctly checks the
error code.
[From Hotfix MPSE300W2KR01][#86433]
143. After reconnecting to disconnected seamless sessions, the foreground
window logic sometimes became invalid in Windows 2003 Server environments.
This fix ensures that after reconnecting, users can get any seamless window
into the foreground successfully.
[From Hotfix MPSE300W2KR01][#86485]
144. Because of changes in Microsoft's IDL compiler (MIDL) in Visual
Studio.Net, IMA RPC communications exposed an error in the Microsoft RPC
runtime that created a memory leak in the IMA Service.
This fix changes the behavior of Microsoft's IDL compiler in Visual Studio.Net
to revert to generating mixed mode stubs for the IMA RPC functions and the
memory leak in the IMA Service no longer occurs.
[From Hotfix MPSE300W2KR01][#86641]
145. You were unable to add MST packages from either the Add Package Wizard or
from Package Properties > Add MST File. This was caused by a conflict between
the original MSI file and the MSI file generated by Installation Manager, which
included the transfers and was thus different from the original MSI file.
[From Hotfix MPSE300W2KR01][#86765]
146. Under rare circumstances, servers running MetaFrame Presentation Server
3.0 for Windows would unexpectedly trap, with the system dump displaying the
following information:
BugCheck 8E, {c0000005, bfa3a823, b65e9204, 0
This was caused by a source code variable being accessed before it was
initialized.
[From Hotfix MPSE300W2KR01][#87483]
147. When using the CHANGEFARM (chfarm.exe) utility to change the membership of
a server running MetaFrame Presentation Server 3.0 for Windows to a farm that
used a different license server, the server continued to use the previous
license server until you restarted the server or modified the server's license
server properties from the Presentation Server Console.
This fix corrects the issue so that you no longer need to restart the server or
modify its license server properties.
[From Hotfix MPSE300W2KR01][#87688]
148. Applications sometimes stopped running if they were configured to use Word
Wrap when Local Text Echo was enabled. The problem resulted from a buffer
overrun
This fix resolves the problem by verifying the buffer sizes and applications no
longer stop running if they are configured to use Word Wrap when Local Text
Echo is enabled.
[From Hotfix MPSE300W2KR01][#87756]
149. This is an enhancement allowing you to limit the list of file types to be
redirected from server to client. By default, server-to-client content
redirection redirects all or none of the following file types: http, https,
rtsp, rtspu, pnm, and mms.
A new registry key is specified to allow certain file types to be excluded from
content redirection. If HKEY_LOCAL_MACHINE \SOFTWARE\Citrix\SFTA
\DisableServerFTA is set, the multistring registry value
HKEY_LOCAL_MACHINE\SOFTWARE \Citrix\SFTA\NoRedirectClasses specifies which file
types are excluded from redirection. If the file type is not in the list, it is
redirected.
To implement this enhancement, make the following value changes to the registry
key using regedt32:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\SFTA
Name: DisableServerFTA
Type: REG_DWORD
Data: 1
Name: NoRedirectClasses
Type: REG_MULTI_SZ
Value: Specify any combination of the following values: http, https, rtsp,
rtspu, pnm, or mms
Note: The values must be line-delimited, for example:
http
https
rtsp
[From Hotfix MPSE300W2KR01][#88380]
150. This is an enhancement allowing you to redirect specific URLs from server
to client, without redirecting other URLs.
A new registry key, HKEY_LOCAL_MACHINE \SOFTWARE\Citrix\SFTA\ValidSites, lets
you specify URLs to be redirected from server to client.
To implement this enhancement, make the following value changes to the registry
key using regedt32:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\SFTA
Name: ValidSites
Type: REG_MULTI_SZ
Data: Specify any combination of URLs
Note: The values must be line-delimited, for example:
www.my_URL.com
*.my_URL.com
The asterisk (*) is supported as a wildcard character.
[From Hotfix MPSE300W2KR01][#88382]
151. QUERYFARM (qfarm.exe) utility: The utility failed to return data after a
large number of servers in a farm were restarted. This was caused by a number
of read-only objects preventing the utility from returning data.
[From Hotfix MPSE300W2KR01][#88608]
152. If the DisableError registry value was turned to ON and client printer
auto-creation fails with the native printer driver but succeeds with UPD, Event
ID 1106 was logged in the event log. This occurred because the registry value
was not checked.
This fix ensures that the registry value is checked so that EventID 1106 will
not be logged.
[From Hotfix MPSE300W2KR01][#89250]
153. After a user created a custom ICA connection and connected to the server
desktop, no client printers were auto-created in the Printers folder. The port
monitor enumerated all existing ports on the system before creating the port
for the auto-created printer. It did not properly catch the error condition and
incorrectly reported that the port to be auto-created already existed.
Note: After applying this fix, you must restart the spooler service.
[From Hotfix MPSE300W2KR01][#90244]
154. Users may not have been able to switch between seamless application
windows after reconnecting to a session. This happened when the global system
time-out value, which sets the amount of time following user input during which
the system does not allow applications to force themselves into the foreground,
was not successfully set to 0. Applications could not set the time-out value
unless they owned the foreground window.
[From Hotfix MPSE300W2KR01][#86405]
155. Instance limits for published applications were occasionally enforced
incorrectly when you connected to several published applications at the same
time. This means that when you connected to a second published application, an
error message may have appeared, stating the instance limit for the application
had been reached when, in fact, it had not.
[From Hotfix MPSE300W2KR01][#91714]
156. The following is a feature enhancement provided in response to customer
requests: In MetaFrame Presentation Server 3.0, seamless connections from
Program Neighborhood Agent and the Web interface honor session sharing over
server zone preference levels. Support has been added for honoring zone
preference levels over session sharing.
Before activating this new functionality, consider the following limitations:
1. With this functionality activated, only Users policy filters are supported;
the Client IP Address, Client Name, and Servers policy filters are not
supported.
2. Connections from Program Neighborhood may not result in session sharing.
To activate this new functionality, you must set the following registry key on
each server:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\IMA\MFRPC
Name: HonorZPFOverSessionSharing
Type: REG_DWORD
Data: 1
[From Hotfix MPSE300W2KR01][#86365]
157. When changing client display settings before reconnecting to a server, the
tray icon of Password Manager occasionally displayed transparent or invisible.
[From Hotfix MPSE300W2KR01][#87609]
158. Users were unable to apply the foreign language versions of the following
transforms to the mps.msi file:
1. Support/Install/Join_Indirect.mst
2. Support/Install/localdb_access_create.mst
3. Support/Install/Thirdpartydb_create_direct.mst
4. Support/Install/Thirdpartydb_join_direct.mst
The issue occurred because of a codepage dependency.
[#89695]
159. On occasion, when connecting to a server, an error message appeared
stating that the logon limit had been reached, even if the limit had not been
reached. The issue occurred when a server lost and then reestablished its
connection to the license server. Upon losing their connection to the license
server, servers create several temporary registry keys that are supposed to be
removed when the connection is reestablished. The temporary keys were not
removed.
[#90208]
160. The Load Manager monitor displayed zeroes for all values to Citrix
administrators with view-only privileges.
[#90619]
161. A "Server busy" dialog box appeared during the rollback process of
Installation Manager's packager. The issue was caused by a lengthy COM
operation.
[#94830]
162. After closing modal dialog boxes of certain published applications in
seamless mode, focus occasionally went to other windows on the client desktop
rather than to the application that launched the dialog, and users had to click
the seamless application title bar to get focus back to the application.
Applications affected by this issue use a zero-sized window at coordinates
(0,0) to hold focus between the time the modal dialog closes and the time the
application window is reenabled. The seamless code recognized this window as
invisible and, therefore, did not send seamless protocol messages to it.
Although this behavior was as designed, it was considered inconvenient by
users, and this hotfix corrects the issue.
[#95001]
163. When a custom administrator with rights to "Edit Load Evaluators" tried to
enable load evaluator logging, the following error message appeared: "Error
turning on/off logging. Error Code: 80000016" and logging was not enabled. The
issue occurred because custom administrators with rights to edit load
evaluators did not have the right to enable logging.
[#96098]
164. Using Windows Explorer, if users attempted to copy a file to the same
folder on a mapped drive in Windows Server 2003, the file copy failed and an
error message appeared. In Windows 2000, the file was copied with a ?Copy of?
prefix.
[#96424]
165. Occasionally, minimizing the language bar in seamless applications
resulted in keyboard failure on the foreground application window.
[#100535]
166. During startup, servers running Presentation Server occasionally
experienced a fatal error. The issue was caused by a race condition.
[#100739]
167. ICA sessions failed to launch the associated media player for URLs
starting with mms:// and the multimedia files did not play back.
[#103537]
168. If an application performed a specific action upon pressing the Escape
key, switching from a seamless window with a menu open to a desktop window
caused that action to be executed, even if the Escape key was not pressed.
[#104173]
169. The Shadow taskbar password was limited to 14 characters.
This release adds support for passwords up to 30 characters long.
[#104860]
170. Occasionally, servers experienced fatal errors indicating a 0x7F - kernel
stack overflow. The issue occurred in combinations of older versions of a
Hewlett Packard network interface card and the Citrix video driver vdtw30.dll
running in ThinWire 1 mode. Occasionally, this combination produced a stack
overflow because too much memory was allocated to the stack in nested function
calls.
[#105825]
171. When launched from a URL shortcut on a published desktop, Internet
Explorer opened in the background without taking keyboard focus. The issue
occurred if client-to-server content redirection was not enabled.
[#108162]
172. Smart card applications running in client sessions appeared slow when
polling for smart card status changes. Wait times during such polls were
considerably longer than those specified for wait time-outs. The issue occurred
because an incorrect multiplier was used to compute the wait timer.
[#111045]
173. With NTLM 2.0 enabled, the shadow taskbar launched successfully even if
users entered an invalid password. The issue occurred because the incorrect
logon was not being identified.
[#111812]
174. When logging on to a published application, servers occasionally
experienced a fatal error. The issue was caused by a buffer overflow.
[#113848]
Citrix Presentation Server 4.0 for Windows Server 2003
1. The MFCOM SDK function IMetaFrameWinApp::Validate reported a failure when a
modified published application was passed in as an argument even though the
application was valid. This occurred because the MFCOM SDK function could not
handle modified applications.
With this fix, the MFCOM SDK function IMetaFrameWinApp::Validate does not
report a failure when a modified published application is passed in as an
argument if the application is valid.
[From Hotfix MPSE300W2K3R03][#84231]
2. By default, the IMA Service uses UTF8 to communicate with an Oracle
database. For Japanese double-byte characters, the variable NLS_LANG is set to
JA16SJIS (Shift+JIS) and the IMA Service cannot communicate with the Oracle
database.
If you have not migrated your data store, use the following command:
DSMAINT MIGRATE /SRCDSN:dsn1 /SRCUSER:user1 /SRCPWD:pwd1 /DSTDSN:dsn2
/DSTUSER:user2 /DSTPDW:pwd2 /RECREATEINDEX
If you have already migrated your data store, run the following command to
rectify the issue:
DSMAINT RECREATEINDEX /DSN:dsn /USER:user /PWD:pwd
[From Hotfix MPSE300W2K3R03][#86413]
2. After a server was running for an extended period of time, the IMA Service
became exceptionally large, exhausting system resources. This was caused by a
memory leak in the IMA Service.
[From Hotfix MPSE300W2K3R03][#88583]
3. Some Installation Manager packages could not be deleted from their package
group.
[From Hotfix MPSE300W2K3R03][#90796]
4. Copying session content to the local device failed.
[From Hotfix MPSE300W2K3R03][#90826]
5. Users accessing Distributed File System (DFS) based file shares did not get
redirected to other replicas if the active DFS share became inaccessible.
[From Hotfix MPSE300W2K3R03][#91067]
6. Charts and graphs, and selected ranges of cells in Microsoft Excel
spreadsheets experienced excessive flickering if SpeedScreen Latency Reduction
and Local Text Echo were enabled.
[From Hotfix MPSE300W2K3R03][#91818]
7. On occasion, ICA sessions did not assume a disconnected state when ICA
Keep-Alive was enabled. This occurred because ICA KeepAlive packets relied on
TCP retransmission time-outs rather than a client response to detect when a
client disconnected.
[From Hotfix MPSE300W2K3R03][#92145]
8. In the Presentation Server Console, published applications that did not have
a 16x16 or 32x32 pixel icon showed the Citrix icon by default. This occurred
because the algorithm responsible for displaying the application icon only
recognized 16x16 and 32x32 pixel icons.
This fix corrects the issue so that application icons with different dimensions
are displayed properly.
[From Hotfix MPSE300W2K3R03][#92320]
9. In large farms, when replicating an updated version of a printer driver to a
server that was using a previous version of the same driver, the update failed
on the destination server even though the event viewer on the source server
reported the update as successful. This occurred because the two versions of
the specific driver had inconsistent printer monitor configuration information
in the registry.
This fix corrects the issue by forcing the installation of the print monitor on
the destination server. If the monitor is not already installed, installation
is performed; otherwise, the driver installation process simply skips this step
and continues as expected.
[From Hotfix MPSE300W2K3R03][#92899]
10. With SpeedScreen Multimedia Acceleration enabled, video files occasionally
stopped playing before all frames were rendered. The issue occurred because
with the default implementation of the underlying DirectShow technology,
servers stopped playing multimedia files when a timer expired. The timer was
calculated based on the multimedia file length. Due to network latency, a
client would start to render frames several seconds after the server started to
generate them. When the server stopped playing, several seconds worth of frames
remained to be rendered but did not.
This fix corrects the issue by modifying the default implementation of
DirectShow so that servers continue playback until the client finishes playing
all frames.
[From Hotfix MPSE300W2K3R03][#92986]
11. If extended characters were used in elements of a seamless window, such as
window titles or the notification area (system tray), the characters may have
displayed incorrectly if the server's system code page was different from the
client's. This occurred because the extended characters were not translated
accurately between server and client.
[From Hotfix MPSE300W2K3R03][#94146]
12. Enumerating users from the shadow taskbar failed for sessions with session
IDs greater than 255. This occurred because the session IDs were being
truncated to a single byte.
[From Hotfix MPSE300R02W2K3001][#94401]
13. Connecting to servers over RDP caused excessive querying of the
SessionTimeZone registry key. This occurred because the code did not discern
between ICA and RDP sessions. For RDP sessions, the queries are unnecessary.
This fix introduces support for limiting the queries to ICA sessions so they do
not occur for RDP sessions. To limit the queries to ICA sessions, set the
following registry key::
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\CtxHook\AppInit_Dlls\Per Session Time Zone
Name: Flag
Type: REG_DWORD
Data: 00000014
[From Hotfix MPSE300W2K3R03][#98019]
14. The 'Í' (AltGr+T) and 'í' (AltGr+J) keys did not work as expected on an HP
Windows CE device on a Hungarian keyboard layout. A previous fix for this
problem did not take into account that there are two ways to produce these
keys.
This fix ensures that both methods of producing these keys is available.
[From Hotfix MPSE300W2K3R03][#98267]
15. On occasion, copying content from local applications and pasting them in
published applications failed on multiprocessor servers. This was caused by
exclusive access blocking for multithreading.
This fix corrects the issue by restricting exclusive access blocking while you
put data on the clipboard.
[From Hotfix MPSE300R02W2K3004][#98286]
16. If Microsoft Outlook was limited to one instance per user and you closed
Outlook but kept an email attachment open, Outlook refused to open again as
long as the attachment was open. After closing the attachment, you could open
Outlook again. This occurred because application limits were not enforced
properly.
This fix corrects the issue. It also introduces a change in behavior so that
Management Console application limits are no longer tracked for applications
that exit immediately after spawning other applications, such as, for example,
write.exe.
[From Hotfix MPSE300W2K3R03][#98468]
17. Using Installation Manager, modifying the command line properties of a
package failed for custom network administrators, and an error message appeared
instead. This occurred because the Installation Manager subsystem was using the
default network rather than the custom network administrator account.
[From Hotfix MPSE300W2K3R03][#99106]
18. The IMA Service could not be stopped on a remote server that had
experienced a ticket request time-out. The issue occurred because of a
dependency of various services.
[From Hotfix MPSE300W2K3R03][#100159]
19. A memory leak was caused by a custom Terminal Services API to enumerate
processes.
[From Hotfix MPSE300W2K3R03][#100466]
20. In farms with more than one server, smart card users could not reconnect to
disconnected sessions. This occurred because sessions of smart card users were
not associated with actual user or computer names, and therefore the server
hosting the disconnected session could not be identified.
[From Hotfix MPSE300W2K3R03][#101409]
21. Occasionally, mapped client drives were not mounted at logon time. This
occurred because the client drive mapping (CDM) network provider was not
consistently being notified of the logon events by Winlogon.
This fix corrects the issue in that the CDM network provider now queries
Terminal Services instead of Winlogon for the necessary information.
[From Hotfix MPSE300W2K3R03][#102051]
22. The printer driver replication feature updated the driver file's creation,
modification, and access date/time stamps to the current date and time when the
file was received by each server on the distribution list.
This fix corrects the issue so that the original date/time stamps of the driver
file are preserved.
[From Hotfix MPSE300W2K3R03][#102960]
23. On occasion, the IMA Service became unresponsive unexpectedly. The issue
was caused by a function with an invalid message handle.
[From Hotfix MPSE300W2K3R03][#103129]
24. This fix introduces a code change to increase code efficiency in
replicating printer drivers.
[From Hotfix MPSE300W2K3R03][#103189]
25. The CtxWinStationQueryClientAddressA and CtxWinStationQueryClientAddressW
APIs would fail unexpectedly and return an ERROR_INSUFFICIENT_BUFFER(0x7a)
error. The issue occurred because a wrong command code parameter passed to a
WinStation API within those CtxWinStation APIs caused the WinStation API to
detect that the corresponding output buffer was too small.
[From Hotfix MPSE300W2K3R03][#103222]
26. If run on computers running Windows Server 2003, the shadow taskbar may
have become unresponsive while enumerating servers. This occurred because of an
invalid memory address lookup.
[From Hotfix MPSE300R02W2K3001][#103290]
27. If a server had more than one network interface card (NIC), but not all
cards were bound to ICA-TCP listeners, incoming ICA connections were attempted
on all NICs, including those not bound to ICA-TCP listeners. This occurred
because Presentation Server operated under the assumption that all NICs were
bound to ICA-TCP listeners.
[From Hotfix MPSE300W2K3R03][#104098]
28. Occasionally, when converting from Windows NT 4.0-format (domain\user) user
names to UPN-format (user@xxxxxxxxxxxxxxxx) user names, the IMA Service
unexpectedly became unresponsive. The issue occurred because the reference
count for certain COM objects were incorrect and caused a DLL to be unloaded.
[From Hotfix MPSE300W2K3R03][#104398]
29. Restarting the IMA Service sometimes produced an error message even though
the operation itself succeeded. The issue was caused by a dependency between
the IMA Service and other services.
This fix corrects the issue by removing the dependency.
[From Hotfix MPSE300W2K3R03][#104452]
30. Under SDK 3.0, calling SpeedScreen plus LoadData SaveData more than once
caused a 0x80010105 error. The issue was caused by an object reference count
that was incorrectly incremented.
[From Hotfix MPSE300W2K3R03][#104521]
31. Microsoft Hotfix 867684 prevented ICA Keepalives from working. The issue
was caused by an incorrect parameter.
[From Hotfix MPSE300R02W2K3006][#104698]
32. Disconnected sessions were displayed as active or not displayed at all in
the Presentation Server Console.
[From Hotfix MPSE300W2K3R03][#104720]
33. If corrupt entries were in the policy table, enumeration failed. For
example, if there were two valid entries and one invalid one, the valid data
was ignored. When this occurred, users could not view, add, or modify any
policies. This was caused by corrupt data nodes in the policy table.
Now when enumerating the policy table, any invalid records are skipped and
users can continue to manipulate the policy table.
[From Hotfix MPSE300W2K3R03][#104869]
34. When restarting computers running Windows Server 2003, error messages 9017
and 9018 appeared in the system event log, indicating that the license server
could not be found even if the license server was up and running. The issue was
caused by a dependency between the termservice service and other services.
[From Hotfix MPSE300W2K3R03][#104890]
35. The Citrix IMA and XML Services were consuming a lot of server CPU time at
the expense of other tasks. This occurred primarily because of periodic updates
made to the data store resulting from changes in the domain trust information.
After the updates were made, the user management subsystem was notified of the
changes and updated its tables accordingly. In a large environment with a large
number of domains this could impact the CPU utilization of the IMA service when
trust changes occurred.
This fix corrects the issue by queuing notification requests and by updating
the tables more efficiently when multiple requests are received.
To queue notification requests, set the following registry keys:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\IMA\IMA_AAMS
Name: UpdateLatency
Type: REG_DWORD
Data: Range = 10 minutes (000927C0) to 120 minutes (6DDD00). Use of any larger
value may produce unexpected results.
Name: PollingInterval
Type: REG_DWORD
Data: Range = 6 hours (1499700) to 7 days (240C8400). Use of any larger value
may produce unexpected results.
Note: UpdateLatency controls how long the IMA service will queue requests
before updating its table of domain trust information for other servers in the
farm. PollingInterval controls how frequently the IMA service will query for
trust changes. The following example shows how to set the UpdateLatency and
PollingInterval to 10 minutes and 7 days, respectively:
Name: UpdateLatency
Type: REG_DWORD
Data: 000927C0
Name: PollingInterval
Type: REG_DWORD
Data: 240C8400
[From Hotfix MPSE300W2K3R03][#106642]
36. Under MFCOM SDK 3.0, retrieving the server name after initialization of the
server object using the InitByServerID function did not work even if the server
was initialized with a valid ID object. The issue occurred because a member
variable of the server object was not being filled with the correct value in
the InitServerByID function.
[From Hotfix MPSE300W2K3R03][#106798]
37. On computers running the French language version of Windows Server 2003,
the qfarm /app command did not return accurate values. The issue occurred
because a resource string was missing a French character symbol introduced in
the French version of Windows Server 2003.
[From Hotfix MPSE300R02W2K3003][#107932]
38. Servers on which SpeedScreen Browser Acceleration was enabled would
unexpectedly restart at periodic intervals with memory dumps indicating the
vdtw30.dll video driver to be at fault. The issue occurred due to improper
error handling when older clients, which do not support ThinWire2 mode, were
connected to the servers in ThinWire1 mode.
[From Hotfix MPSE300R02W2K3003][#108173]
39. Shadowing did not work when shadow logging was enabled. This occurred
because of a code error.
[From Hotfix MPSE300R02W2K3001][#108658]
40. Under MFCOM SDK 3.0, calling SpeedScreen through the IMetaFrameWinFarm5
interface would sometimes cause an error. The issue was caused by an object
reference count that was incorrectly incremented.
[From Hotfix MPSE300W2K3R03][#108915]
41. This feature enhancement adds support for running Microsoft Rights
Management Services (RMS) for Windows on computers running Presentation Server.
Previously, running the RMS client on such computers resulted in the display of
the following error message:
"Cannot verify user information at this time. Contact your administrator if
this problem continues".
The issue was caused by a DLL that was interfering with the RMS client.
To enable this enhancement, you must set the following registry key:
HKEY_LOCAL_MACHINE\Software\Citrix\CtxHook
Name: Flags
Type: REG_DWORD
Data: 0
[From Hotfix MPSE300W2K3R03][#108993]
42. Servers may have experienced a KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e) blue
screen when clients utilized the ThinWire1 virtual channel by connecting at low
resolution and low color depth. For example, a client connecting at less than
800x600 pixels and 256 colors may have caused the exception. This occurred
because of an invalid handle.
[From Hotfix MPSE300R02W2K3003][#110106]
43. The CHANGEFARM (chfarm) utility failed to join a new server to a farm when
using a fully qualified domain name (FQDN) or an IP address. Connections using
a NetBios name were successful and the server was able to join the new farm.
The issue occurred because a transport command did not support FQDNs or IP
addresses.
This fix adds support for FQDNs and IP addresses to the chfarm utility.
[From Hotfix MPSE300W2K3R03][#110427]
44. When logging on to a session using non-smart card credentials and
subsequently inserting a smart card, the session may have become unresponsive.
This occurred because the Microsoft Smart Card Resource manager, resident on
the client device, blocks certain commands while a transaction is pending. If
the server was forwarding commands while such transactions were pending, the
commands would be blocked on the client and result in session unresponsiveness.
This fix corrects the issue in that server commands are now held on the server
until the related client side transaction has completed.
[From Hotfix MPSE300R02W2K3002][#110436]
45. Implementing a smart card removal policy to lock a client device caused all
ongoing ICA sessions from that device to be disconnected. This feature
enhancement introduces support for a registry entry that allows ongoing
sessions to remain connected while such policy is being implemented. To prevent
ongoing sessions from being disconnected while you implement a smart card
removal policy, set the following server-side registry key using regedt32.exe:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\SmartCard
Name: ScLockNoDisc
Type: REG_SZ
Data: 1
[From Hotfix MPSE300R02W2K3002][#111680]
46. After installing Hotfix Rollup Pack MPSE300W2K3R02 and restarting the
server, ICA connections were refused and the following message may have
appeared:
"A problem with Terminal Services functionality has been corrected on the
server running Presentation Server. The correction involves changes to the
registry. Please reboot the server."
This happened if the RDP-TCP listener was deleted before you installed Hotfix
Rollup Pack MPSE300W2K3R02.
This issue was corrected in Hotfix Rollup Pack MPSE300W2K3R03.
[From Hotfix MPSE300W2K3R03][#112020]
47. Smart Card applications run within an ICA session may have exhibited
different behavior than when run in an RDP session. This occurred, in part,
because additional time had been added to certain time-outs in an attempt to
minimize network traffic resulting from polling smart cards. Additionally,
error codes were different based on the session protocol.
This fix corrects the issue in that it applies time-outs as specified by smart
card vendors, and returns error codes that more accurately represent the smart
card state.
[From Hotfix MPSE300R02W2K3002][#112461]
48. When trying to save a Microsoft Excel workbook to a client drive, the
following message appeared:
"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.
[From Hotfix MPSE300W2K3015][#72187]
49. When the following registry entry was set, Sehook20.dll was still loaded in
the session:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\Wfshell\TWI
Name: SeamlessFlags
Type: REG_DWORD
Data: 0x4
In certain situations the registry entry was ignored, causing Sehook20.dll to
be loaded despite the registry setting.
This fix ensures that the registry entry is used to determine whether or not to
load Sehook20.dll in the session.
[From Hotfix MPSE300W2K3007][#83555]
50. The times shown in the Access Suite Console Historical Metric Graph were
incorrect for timezones other than GMT.
[From Hotfix MPSE300W2K3011][#84788]
51. The Citrix Event Provider generated unnecessary disconnected session
alerts.
[From Hotfix MPSE300W2K3011][#85174]
52. Server to client content redirection was not functioning properly with URLs
in Microsoft Outlook 2003 published on servers running MetaFrame XP V. 1.0 with
Feature Release 3. When you clicked the URL, the link opened in an instance of
Internet Explorer published on the server rather than the instance installed on
the client device. This was caused by an incorrect registry key setting.
[From Hotfix MPSE300W2K3R02][#85707]
53. When reconnecting to a disconnected seamless session, users were unable to
maximize the application window by double-clicking its title bar. Although the
application window did get maximized temporarily, it reverted to its previous
size immediately thereafter.
[From Hotfix MPSE300R01W2K3001][#87308]
54. Reconnecting to a logged off session from the Web interface while the
Workspace Control feature was enabled may have launched multiple instances of
the same published applications. This was caused by a flaw in the duplicate
session algorithm of the Workspace Control feature.
[From Hotfix MPSE300W2K3R02][#87318]
55. Applications were attempting to access a smart card reader attached to the
server instead of the one residing on the client. Depending on the way the CSP
vendor implemented smart card support, the previous mechanism used to hook the
smart card functions didn't always work.
This fix introduces a new mechanism that minimizes errors by placing the hook
in the dll function of interest, not every piece of code making a reference to
the DLL function of interest. As a result, users will not see any indication
that an application is attempting to access a smart card reader attached to the
server. The application should be hooked consistently and routed to the smart
card reader attached to the client.
[From Hotfix MPSE300R01W2K004][#87999]
56. Saving a file to a client drive failed if the value of the seconds portion
of the time stamp equaled 59. This occurred because the Client Drive Mapping
feature rounded up the time stamp but failed to propagate the change.
[From Hotfix MPSE300W2K3015][#88799]
57. An error occurred when you attempted to launch an application published on
a server running MetaFrame XP V. 1.0 with Feature Release 2 if the server was
located in a zone with a data collector running MetaFrame Presentation Server
3.0. This occurred because the data collector, running Version 3.0 of the
product, was directing an event to an event handler that handles Version 3.0
events only and generates an error when receiving an event from a server
running an earlier version of the product.
[From Hotfix MPSE300W2K3R02][#89269]
58. When using the Server Default keyboard setting in Program Neighborhood, the
Input Method Editor (IME) user dictionary was created in an incorrect folder.
[From Hotfix MPSE300R01W2K3007][#89688]
59. Due to an access violation, a custom MFCOM application was experiencing a
fatal error while attempting to obtain Citrix virtual channel policy
information. This occurred because the reference count of the wrong MFCOM
object was incremented, which resulted in the original MFCOM object being freed
while it was still in use.
[From Hotfix MPSE300W2K3R02][#90079]
60. Each time a user with auto-created printers connected to a server, printed,
and then logged off, the handle count on the spooler service increased. Also,
after the print spooler service had been running for some time on a server to
which many users were connecting with auto-created printers, you could see many
ports not belonging to any active printers under Printers->File->Server
Properties->Ports. This occurred because the auto-created printer ports were
not deleted upon users' logoff or if there was a problem opening the printers.
[From Hotfix MPSE300W2K3017][#90456]
61. Seamless application windows did not display correctly after session
reconnection if an application running in the session was unresponsive.
[From Hotfix MPSE300R01W2K3001][#90739]
62. Users were sometimes unable to access files or folders with long file names
on mapped client drives and received an error message instead. The issue was
caused by an incompatibility between long file and folder names and session IDs
longer than two characters.
This fix removes the incompatibility.
[From Hotfix MPSE300R01W2K3002][#90860]
63. Requests by SDKs to obtain SpeedScreen Flash Acceleration returned
incorrect values. This occurred because the SDK requests did not call the IMA
Service to update the values.
[From Hotfix MPSE300W2K3R02][#91022]
64. Custom programs or scripts calling the MFCOM SDK function
IMetaFrameApplication::WriteIconToFile got an exception.
[From Hotfix MPSE300W2K3R02][#91025]
65. The following auto-created printers failed to print in client sessions on
servers running Windows Server 2003:
Epson LQ-570 ESC/P 2
Epson LQ-870 ESC/P 2
Epson LQ-1170 ESC/P 2
Epson SQ-870 ESC/P 2
Epson SQ-1170 ESC/P 2
HP Business Inkjet 2230/2280
HP DesignJet 750C (E/A0) Color
HP LaserJet 5/5M - PS
HP LaserJet 5/5M - Standard
Epson Stylus COLOR 800 ESC/P 2
Epson Stylus COLOR 850 ESC/P 2
This occurred because the wrong printer name was sent to the client.
[From Hotfix MPSE300W2K3015][#91223]
66. Occasionally, servers experienced a fatal error, displaying a blue screen.
This fix introduces a code change that corrects the issue.
[From Hotfix MPSE300R01W2K3006][#91404]
67. When writing email in Lotus Notes over low latency connections with Local
Text Echo enabled, text prediction changed to an illegible font.
[From Hotfix MPSE300W2K3R02][#91605]
68. In the Presentation Server Console, when you assigned a policy to a group
and then searched by user name for policies assigned to a particular member of
the group, the search result did not include the policy. The issue was caused
by a flaw in the way the IMA user management subsystem enumerates Active
Directory user groups.
[From Hotfix MPSE300W2K3R02][#92024]
69. Client printing failed for applications published on computers running
Windows 2003 Server if you accessed the applications through a pass-through
client published on computers running Windows Server 2000. This occurred
because the client printer name was passed incorrectly from the server to the
client.
[From Hotfix MPSE300W2K3R02][#92149]
70. Session sharing failed in mixed Windows/NDS deployments if users were using
the same password for both accounts but the application being launched was only
available to Windows domain users.
[From Hotfix MPSE300W2K3016][#92572]
71. A popup window of a custom application running in seamless mode prompted
the display of a dialog as if Windows Explorer was being launched, when, in
fact, it was not.
[From Hotfix MPSE300W2K3017][#92839]
72. In the Client Update Configuration utility, limits on the number of
simultaneous client updates did not work properly. The limits worked properly
for clients connected with Administrator rights, but simultaneous updates to
clients connected with User rights may have exceed the limit you specified.
[From Hotfix MPSE300W2K3R02][#92858]
73. When a client device was locked and you clicked outside the Unlock Computer
dialog box and then clicked inside the dialog box, the User name and Password
text boxes did not respond to keyboard input.
[From Hotfix MPSE300W2K3R02][#93099]
74. When accessing a Web page that contained an AlphaImageLoader object in a
published instance of Internet Explorer in Program Neighborhood Version 7.1 or
later, Internet Explorer experienced a fatal error. This occurred because the
presence of the AlphaImageLoader object on the Web page loads a DLL associated
with SpeedScreen Browser Acceleration even if that feature is not enabled. The
fatal error occurred because the DLL's data structures were not initialized
unless SpeedScreen Browser Acceleration is enabled.
This fix modifies the DLL so that it works properly even if SpeedScreen Browser
Acceleration is not explicitly enabled.
[From Hotfix MPSE300W2K3R02][#94109]
75. Summary database purge jobs failed if the Oracle database was offline due
to or following, for example, backups. This occurred because the Oracle
listener could not be contacted.
[From Hotfix MPSE300W2K3019][#94651]
76. When specifying the domain name, but not the user name, in an ICA file or
in the Connection properties of Program Neighborhood, the client did not pass
the specified domain name to the session logon screen. This occurred because
Presentation Server rejected the domain name sent by the client unless the user
name was also sent.
[From Hotfix MPSE300W2K3R02][#94718]
77. After upgrading to Service Pack 1 of Windows Server 2003, SpeedScreen
Browser Acceleration did not work properly. SpeedScreen Browser Acceleration
hooks into Internet Explorer. Due to changes in Service Pack 1, the hooks did
not work as designed.
[From Hotfix MPSE300W2K3R02][#94723]
78. The IMA Service experienced a deadlock. This was caused by the server down
processor not releasing a lock.
[From Hotfix MPSE300W2K3019][#96163]
79. Client drive mapping failed if you disabled the "System objects: Strengthen
default permission of internal system objects (e.g. Symbolic Links)" base
system object restriction.
Though disabling the restriction is not recommended, client drive mapping no
longer fails if you disable the restriction after applying this fix.
[From Hotfix MPSE300W2K3R02][#96289]
80. Due to different screen resolutions, when shadowing a seamless session you
were unable to locate windows in the session window if you or the shadowee
minimized the session window.
[From Hotfix MPSE300W2K3R02][#97204]
81. Occasionally, if one or more of the following policies were enabled,
servers became unresponsive and stopped accepting new connections after running
for several hours. The issue was caused by a memory leak.
? Client Devices>Resources>Drives>Connection>Connect Client Drives at Logon
? Client Devices>Resources>Drives>Connection>Do not Connect Client Drives at
Logon
? Client Devices>Resources>Drives>Mappings>Turn off Floppy disk drives
? Client Devices>Resources>Drives>Mappings>Turn off hard drives
? Client Devices>Resources>Drives>Mappings>Turn off CD-ROM drives
? Client Devices>Resources>Drives>Mappings>Turn off Remote drives
[From Hotfix MPSE300W2K3R02][#97536]
82. In the Presentation Server Console, under Installation Manager, the
Schedule Time column on the Jobs tab displayed incorrect dates for packages
scheduled for deployment. The issue was caused by a code error.
[From Hotfix MPSE300R01W2K3005][#97644]
83. Occasionally, when a non-Windows client was connecting to a server running
Presentation Server, the server would experience a fatal error. This issue was
caused by unsynchronized access to a global variable by multiple threads.
[From Hotfix MPSE300R01W2K3006][#97822]
84. When attempting to launch an application published on Windows Server 2003
using NDS credentials, the following message appeared:
"You do not have access to logon to this session."
This occurred because NDS was not properly initialized, which caused user
authentication to fail.
[From Hotfix MPSE300W2K3R02][#98490]
85. When trying to establish a pass-through connection from a smart card
authenticated session, you may have received a 1031 virtual driver error.
Separately, smart card developers may have received a 258 or 0x102 error from
the ScardGetStatusChange API when calling with a 0 time-out within a
Presentation Server environment.
This fix introduces a code change to ensure that the proper error code is
returned. Smart card users no longer receive a 1031 virtual driver error when
trying to establish a pass-through connection from a smart card authenticated
session. Also, smart card developers receive a specific SCARD_E_TIMEOUT
(0x8010000A) error code from the ScardGetStatusChange API when calling with a 0
time-out within a Presentation Server environment.
[From Hotfix MPSE300W2K3R02][#98511]
86. Occasionally, servers experienced a fatal error, displaying a blue screen.
[From Hotfix MPSE300W2K3R02][#98528]
87. Custom Administrators were unable to add/remove metrics or adjust metric
properties. Error code:c0160ad8 was displayed.
[From Hotfix MPSE300W2K3019][#99003]
88. After installing Hotfix MPSE300W2K3017, when you ran 'iexplore ?e? in
seamless mode, a warning message stating that the Windows desktop was starting
appeared and obscured the desktop. The warning message was produced in error.
[From Hotfix MPSE300W2K3R02][#99087]
89. When querying an unresponsive SQL Server, the IMA service did not time out.
As a result, the Management Console was not populated properly and command line
tools such as qfarm and chfarm did not work until you restarted the server.
This fix introduces a new registry entry that allows you to configure an
explicit time-out interval for the IMA service.
Create the following registry entry:
HKEY_LOCAL_MACHINE\\Software\Citrix\IMA
Name: DB_CONNECTION_TIMEOUT
Type: REG_DWORD
Data: <time-out value, in seconds>
[From Hotfix MPSE300W2K3R02][#99277]
90. Users were unable to launch published applications if the Session
Reliability feature was enabled and an option other than All network adapters
with this protocol was configured for the ICA protocol in the Citrix Connection
Configuration utility.
This fix introduces support for session reliability even if you limit a
protocol to a particular network adapter.
To enable this functionality:
1. Open the file httpd.conf, located in the Program Files\Citrix\Xte\conf
folder, in a text editor.
02 Below the line #Citrix_End, add the following line:
CgpSpecifiedIcaLocalAddress <server IP address, for example, 10.8.6.192>
3. Save your changes.
41. Reboot the server.
If you have this functionality enabled, assign a static IP to the server or, if
you are using DHCP, create a script to automatically update the IP address of
CgpSpecifiedIcaLocalAddress in the httpd.conf file. If the IP address of
CgpSpecifiedIcaLocalAddress does not match the actual IP address of the server,
you receive an error stating that there is no route to the specified subnet
address.
[From Hotfix MPSE300W2K3R02][#99885]
91. Installation Manager, after installing a package on a server, enabled
logons to that server even if you manually disabled them. This occurred because
Installation Manager, by design, disables logons to a server before installing
a package and then re-enables them when the installation is complete. However,
it ignored the status of the Enable logons to this server option of the
MetaFrame Settings server properties page of the Presentation Server Console
and enabled logons even if that option was disabled.
[From Hotfix MPSE300W2K3R02][#100402]
92. Users without Windows user profiles and users whose profile had been
modified, were unable to launch published applications.
[From Hotfix MPSE300W2K3R02][#101958]
93. Servers may have experienced a fatal error if you ran Microsoft's Driver
Verifier utility while users were logged on or logging on to the server using
smart cards. This occurred because of a lack of synchronization in the smart
card I/O control cancel handler.
[From Hotfix MPSE300W2K3R02][#103495]
94. If the print spooler service stopped during a print job during an ICA
session, logging on to the computer running Presentation 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.
[From Hotfix MPSE300W2K3001][#74290]
95. When playing back sound that was recorded inside of a client session, the
last two seconds of the recorded sound was repeated.
This fix resolves the problem.
[From Hotfix MPSE300W2K3001][#86157]
96. When pausing the playback of sound inside a client session, it sometimes
took up to 10 seconds for the sound to stop playing in a low-latency network.
This was caused by buffering of audio data on the client resulting in pause
request responses being slow.
To enable the new Delayed Callback mode, you must create the following registry
entry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal
Server\WinStations\ICA-tcp\AudioConfig
Name: CallbackDelta
Type: REG_DWORD
Data: (Citrix recommends you start with a value of five or 10 milliseconds)
This fix ensures that the sound will not continue to play for 10 seconds when
pausing the playback of sound in a client session.
[From Hotfix MPSE300W2K3001][#86166]
97. 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 will call only those applications
that are responding. Users can switch to other applications even if one is
unresponsive.
[From Hotfix MPSE300W2K3007][#76070]
98. 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.
[From Hotfix MPSE300W2K3007][#80221]
99. The display speed of the combo list box became very slow if the list box
expanded beyond the area of the background window. The seamless routine that
checked to determine whether or not the target window was a top-level window
ignored the window, causing a delay in the display of the window.
A new API is now used to determine whether or not the target window is a
top-level window. The combo list box appears as quickly as other types of
windows in a seamless session.
[From Hotfix MPSE300W2K3007][#83550]
100. This fix addresses a custom application's performance when run seamlessly.
Some applications appeared to be slower to respond when performing actions such
as moving, resizing, or closing windows. This fix introduces two new registry
settings that allow administrators to configure an explicit time interval for
the seamless engine mechanism to monitor when changes take place in the
seamless applications.
Create the following registry keys:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI
Name: SeamlessFlags
Type: REG_DWORD
Data: 0x4
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI
Name: WorkerWaitInterval
Type: REG_DWORD
Data: <Number of milliseconds allowed> (Values are between 5 ? 500; the default
is 50.)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI
Name: WorkerFullCheckInterval
Type: REG_DWORD
Data: <Number of milliseconds allowed> (Values are between 50 ? 5000; the
default is 500.)
A higher value slows responsiveness but improves scalability; a smaller size
increases responsiveness but decreases scalability slightly. The level of
scalability depends on several factors, such as hardware sizing, types of
applications, network performance, and number of users.
[From Hotfix MPSE300W2K3007][#85657]
101. Computers running Presentation Server could not reestablish a connection
to the license server if the IP address of the license server changed. This was
identified as a problem with a third-party SDK.
This fix ensures that computers running Presentation Server can reestablish a
connection to the license server even if the license server's IP address
changes. See Citrix Knowledge Base article CTX103795 for additional
information.
[From Hotfix MPSE300W2K3005][#86151]
102. 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.
[From Hotfix MPSE300W2K3006][#71243]
103. Users occasionally experienced disconnected sessions when transferring
large amounts of data over low-bandwidth modem connections.
This fix prevents the session from disconnecting.
[From Hotfix MPSE300W2K3006]][#84837]
104. If the following registry key was set with a non-zero value, servers
occasionally experienced a fatal error when users connected to a server farm:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\Wds\icawd
Name: ActiveLatencyPeriodInSeconds
Type: REG_DWORD
This was caused by an error in timing that resulted in the reuse of a buffer
that was already freed.
This fix ensures that the servers no longer experience a fatal error when
connecting to a server farm even if the registry key is set with a non-zero
value.
[From Hotfix MPSE300W2K3006][#87252]
105. Starting with MetaFrame XP Feature Release 3, the server seamless engine
was enhanced to support the Windows XP Theme style. This new functionality was
enabled by default and could not be turned off.
With Windows XP Themes enabled, some custom published applications could not be
displayed or operated properly on Windows XP/2003 clients.
This fix introduces a new seamless global registry flag that, when set,
disables this new functionality as well as the use of client-side metrics. Set
the following server-side registry key to accomplish this:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI
Name: SeamlessFlags
Type: REG_DWORD
Data: 0x4000
Note that this setting forces all published applications to be displayed using
server-side metrics. If the local client-side metrics differ from the
server-side metrics, there will be an inconsistency in the window styles. In
addition, because ICA sessions will not be aware of any client-side metrics,
maximizing windows will ignore any Windows Always On Top toolbar settings.
[From Hotfix MPSE300W2K3007][#87052]
106. Installing or uninstalling multiple computers running MetaFrame
Presentation Server 3.0 in large farms failed intermittently and left partial
data in the data store. A SQL transaction did not retry when it failed to get
the record locks it needed.
The retry count was increased across the board to improve robustness in large
farms. Installing or uninstalling multiple computers running MetaFrame
Presentation Server 3.0 in large farms no longer fails.
[From Hotfix MPSE300W2K3008][#86168]
Note: The following related updates and hotfixes are also available:
? KB Article Number CTX104813 (pre-installation update): Installing or
uninstalling multiple computers running MetaFrame Presentation Server 3.0 in
large farms failed intermittently and left partial data in the data store. A
SQL transaction did not retry when it failed to get the record locks it needed.
The retry count was increased across the board to improve robustness in large
farms. Installing or uninstalling multiple computers running MetaFrame
Presentation Server 3.0 in large farms no longer fails.
? KB Article Number CTX104817 (optional). This optional utility provides a way
to perform validation checks on a server farm's data store. Results are
displayed on the console and written to the event log. The /Clean option
deletes inconsistent records.
107. If the Presentation Server Console was used to create a policy that had
the rule \Client Devices\Resources\Network Printers\Print Job Routing included
and had Send directly from server to printer enabled in the rule, relevant
print jobs were not being sent directly from the server to the printer. The
rule was not being enforced correctly.
This fix ensures that the rule is enforced correctly and print jobs are being
sent directly from the server to the printer.
[From Hotfix MPSE300W2K3009][#84405]
108. The content-redirection for Windows File Type Associations was not reset
when a user modified a (copied) published application's command-line.
This fix ensures that the Presentation Server Console resets the File Type
Association settings whenever a user changes a (copied) published application's
command-line.
[From Hotfix MPSE300W2K3012][#87751]
109. If an administrator changed some of a server's settings under ICA Browser
in MetaFrame Settings on the Presentation Server Console and later executed
dsmaint recreatelhc on that server, the changed setting was not retained. After
executing dsmaint recreatelhc, the changed settings were overwritten with
default values in error.
This fix ensures that changed settings on a server are retained after executing
dsmaint recreatelhc on that server.
[From Hotfix MPSE300W2K3R01][#86011]
110. In interoperability mode, listener values could not be obtained or set
correctly through the MFCOM interface. This occurred 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.
[From Hotfix MPSE300W2K3R01][#81033]
111. The ICA browser could not be started when running MetaFrame XP Feature
Release 3 on a French Windows 2003 platform and switching into interoperability
mode. This occurred because one resource string in the French Windows 2003
platform was incorrect.
This fix ensures that all localized resource strings are correct.
[From Hotfix MPSE300W2K3R01][#82723]
112. When users connected to a published tool called Microsoft Imaging Software
and chose the pen or highlighter mode, the mouse pointer disappeared from the
document area of the screen. This occurred because the ICA video driver was not
supporting 32-bitmaps for the ICA Client.
This fix ensures that when users connect to a published tool called Microsoft
Imaging Software and choose the pen or highlighter mode, the correct mouse
pointer is displayed in the document area of the screen.
[From Hotfix MPSE300W2K3R01][#83045]
113. Iexplore.exe sometimes became unresponsive when displaying images in an
ICA session if SpeedScreen browser acceleration was turned on. A SpeedScreen
acceleration routine did not compute the number of image scan lines
sufficiently to store the image check tag correctly, causing a buffer overrun
and leading to an application fault.
This fix ensures that the number of image scan lines is sufficient to store the
image check tag.
[From Hotfix MPSE300W2K3R01][#87843]
114. When two processes attempted to access a remote smart card reader, all
activity going across the virtual channel stopped. After a time-out period, a
failure would occur on one of the processes and the other would continue. This
occurred because the Microsoft Smart Card Resource Manager blocks certain
commands. If a command was sent from the server while a command from another
process was still in process, activity would stop.
This fix ensures that no additional commands are sent to the client until the
command blocked by the Microsoft Smart Card Resource Manager is released.
Activity will not stop when two processes within a session attempt to access a
remote smart card reader.
[From Hotfix MPSE300W2K3015][#83631]
115. A smart card application was requesting status continually or invalid
smart card status was being received. The reader state information maintained
by the Citrix Device Management component was incorrectly updated. In addition
the smart card state data included some non-documented third-party flags that
were being compared.
This fix ensures the reader state information is properly maintained by the
Citrix Device Management component. The smart card application no longer
continually requests status nor is invalid smart card status being transmitted.
[From Hotfix MPSE300W2K3015][#85780]
116. A server sometimes experienced a fatal system error caused by Cdm.sys with
bug checkcode 50. This occurred because Cdm.sys occasionally accessed a buffer
out of boundary.
With this fix, Cdm.sys no longer accesses a buffer out of boundary.
[From Hotfix MPSE300W2K3R01][#87762]
117. 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 permitted to be sent to the client before
the reconnection sequence has completed.
[From Hotfix MPSE300W2K3015][#80574]
118. When logging on to a server using a smart card, users sometimes received
the message, "The system could not log you on. The requested key container does
not exist on the smart card." This issue was caused by a mechanism used to
track smart card based sessions that was incompatible with the way some CSPs
store logon information.
This fix uses a different tracking mechanism that is compatible with the way
those CSPs store logon information.
[From Hotfix MPSE300W2K3015][#85648]
119. In client sessions, the playback quality of sound recorded in low-quality
mode over a wide area network (WAN) was poor.
This fix addresses the issue in such a way that the playback is of equal
quality on the client as on the server.
[From Hotfix MPSE300W2K3015][#87095]
120. 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.
[From Hotfix MPSE300W2K3R01][#72877]
121. 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 will be correct no matter what the
current date is when scheduling occurs.
[From Hotfix MPSE300W2K3R01][#76147]
122. If Automatic install of native drivers was disabled, no events were
generated in the event log when printers could not be auto-created.
With this fix, events are generated if printers cannot be auto-created.
[From Hotfix MPSE300W2K3R01][#72922]
123. Some printers were not automatically auto-created in an ICA session, and
an Event ID 1107 entry was added to 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 auto-creation should occur without incidents.
[From Hotfix MPSE300W2K3R01][#79268]
124. When you 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 you logged on to the server thereafter, an error was generated
stating that the report file could not be opened because it did not have an
application associated with it.
This fix corrects the issue, and the report file is removed.
[From Hotfix MPSE300W2K3R01][#76592]
125. Belgian French keyboard layout with non-Win32 ICA Clients: The following
key combination did not work as expected in several applications:
AltGr + '^' symbol (on the number 6 key)
The Unicode mappings were not properly defined in the Presentation Server
Belgian French keyboard (.kbd) file. This fix corrects the issue, and the key
combination works properly.
[From Hotfix MPSE300W2K3R01][#80525]
126. Belgian Dutch keyboard layout with non-Win32 ICA Clients: The following
key combinations did not work as expected in several applications:
AltGr + '?' (euro symbol)
AltGr + '\' (backslash symbol)
The Unicode mappings were not properly defined in the Presentation Server
Belgian Dutch keyboard (.kbd) file. This fix corrects the issue, and the key
combinations work properly.
[From Hotfix MPSE300W2K3R01][#80524]
127. Canadian French keyboard layout with non-Win32 ICA Clients: The following
key combinations did not work as expected in several applications:
AltGr + the key next to the left Shift key
AltGr + the third key to the left of the right Shift key
The Unicode mappings were not properly defined in the Presentation Server
Canadian French keyboard (.kbd) file. This fix corrects the issue, and the key
combinations work properly.
[From Hotfix MPSE300W2K3R01][#84624]
128. Czech keyboard layout with non-Win32 ICA Clients: The following key
combination did not work as expected in several applications:
AltGr + various keys at the top of the keyboard ( '2' to '+').
The Unicode mappings were not properly defined in the Presentation Server Czech
keyboard (.kbd) file. This fix corrects the issue, and the key combinations
work properly.
[From Hotfix MPSE300W2K3R01][#80867, 84630]
129. Dutch keyboard layout with non-Win32 ICA Clients: The following key
combinations did not work as expected in several applications:
AltGr + 'cent' symbol key
AltGr + 'broken bar' symbol key
The Unicode mappings were not properly defined in the Presentation Server Dutch
keyboard (.kbd) file. This fix corrects the issue, and the key combinations
work properly.
[From Hotfix MPSE300W2K3R01][#77702]
130. English (Australia) keyboard layout: Keyboard input did not appear in the
SpeedScreen Latency Reduction bubble if English (Australia) was set as the
default locale in an ICA session.
The program failed to load the corresponding keyboard layout DLL if English
(Australia) was set as the default locale. This fix corrects the issue, and the
key combinations work properly.
[From Hotfix MPSE300W2K3R01][#84653]
131. Finnish keyboard layout with non-Win32 ICA Clients: The following key
combination did not work as expected in several applications:
AltGr + '|' (pipe symbol, right of left Shift key)
The Unicode mappings were not properly defined in the Presentation Server
Finnish keyboard (.kbd) file. This fix corrects the issue, and the key
combination works properly.
[From Hotfix MPSE300W2K3R01][#80868]
132. French keyboard layout with non-Win32 ICA Clients: The following key
combinations did not work as expected in several applications:
AltGr + 'ç/9' symbol key
The Unicode mappings were not properly defined in the Presentation Server
French keyboard (.kbd) file. This fix corrects the issue, and the key
combination works properly.
[From Hotfix MPSE300W2K3R01][#80878]
133. Greek keyboard layout with non-Win32 ICA Clients: The following keys and
key combinations did not work as expected in several applications:
AltGr +'?' (euro symbol) and various other keys
Shift + 's' key
's' key did not work with Caps Lock on
Shift + 'h'' key
'h' key did not work with Caps Lock on
Shift + 'w' key
'[' with Caps Lock on turned off the Caps Lock indicator light. Subsequently,
Caps Lock On produced lowercase letters, Caps Lock Off produced uppercase
letters.
The Unicode mappings were not properly defined in the Presentation Server Greek
keyboard (.kbd) file. This fix corrects the issue, and the key combination
works properly.
[From Hotfix MPSE300W2K3R01][#84631]
134. Hungarian keyboard layout with non-Win32 ICA Clients: The following keys
and key combinations did not work as expected in several applications:
AltGr + '^' symbol key
AltGr + '?' (euro symbol)
3rd key left of backspace key
'Í' key next to the left Shift key with Cap Locks on
The Unicode mappings were not properly defined in the Presentation Server
Hungarian keyboard (.kbd) file. This fix corrects the issue, and the key
combinations work properly.
[From Hotfix MPSE300W2K3R01][#84632]
135. Norwegian keyboard layout with non-Win32 ICA Clients: The following key
combination did not work as expected in several applications:
AltGr +'?' (euro symbol)
The Unicode mappings were not properly defined in the Presentation Server
Norwegian keyboard (.kbd) file. This fix corrects the issue, and the key
combination works properly.
[From Hotfix MPSE300W2K3R01][#79182]
136. Polish keyboard layout with non-Win32 ICA Clients: The following keys and
key combinations did not work as expected in several applications:
AltGr + '?' (euro symbol)
3rd key left of backspace key
'ó' key
'|' key
'[' key AltGr + f
']' key AltGr + g
'§' key
The Unicode mappings were not properly defined in the Presentation Server
Polish keyboard (.kbd) file. This fix corrects the issue, and the key
combinations work properly.
[From Hotfix MPSE300W2K3R01][#84633]
137. Russian keyboard layout with non-Win32 ICA Clients: The following keys and
key combinations did not work as expected in several applications:
'Ë' key
Key just left of the right Shift key
The Unicode mappings were not properly defined in the Presentation Server
Russian keyboard (.kbd) file. This fix corrects the issue, and the key
combinations work properly.
[From Hotfix MPSE300W2K3R01][#84634]
138. Slovak keyboard layout with non-Win32 ICA Clients: The following keys and
key combinations did not work as expected in several applications:
';' key
'[' key
']' key
'7' key
'8' key
'9' key
'=' (dead key)
' (quote symbol to the left of the backspace key)
The Unicode mappings were not properly defined in the Presentation Server
Slovak keyboard (.kbd) file. This fix corrects the issue, and the keys and key
combinations work properly.
[From Hotfix MPSE300W2K3R01][#84838]
139. Slovenian keyboard layout with non-Win32 ICA Clients: The following keys
and key combinations did not work as expected in several applications:
'C' key
'?' (euro symbol)
'§' key
Shift + '?' key
Shift + 'd' key
Shift + 'c' key
Shift + '?' key
The Unicode mappings were not properly defined in the Presentation Server
Slovenian keyboard (.kbd) file. This fix corrects the issue, and the key
combinations work properly.
[From Hotfix MPSE300W2K3R01][#84636]
140. Spanish (incl. Latin American) keyboard layouts with non-Win32 ICA
Clients: Various keys and key combinations did not work as expected in several
applications.
The Unicode mappings were not properly defined in the Presentation Server
Spanish keyboard (.kbd) file. This fix corrects the issue, and the key
combination works properly.
[From Hotfix MPSE300W2K3R01][#84639, 83477]
141. Turkish keyboard layouts with non-Win32 ICA Clients: The following key
combination did not work as expected in several applications:
AltGr +'?' (euro symbol)
'¦' key
Caps Lock + 'g' key
Caps Lock + 's' key
Caps Lock + '?' key
The Unicode mappings were not properly defined in the Presentation Server
Turkish keyboard (.kbd) files. This fix corrects the issue, and the key
combination works properly.
[From Hotfix MPSE300W2K3R01][#84640, 84641]
142. Publishing an application from a network share in a different domain and
browsing to the application's icon generated the following error message:
"The icon associated with this published application cannot be accessed. If you
typed in the path to the application executable, check that the path is correct
and that the executable is available," and the icon failed to appear in the
farm.
This fix corrects the issue, the error no longer occurs, and the application
icon appears in the farm as expected.
[From Hotfix MPSE300W2K3R01][#78094]
143. In Program Neighborhood, when Active Directory users whose user options
were set to "User must change password at next logon" attempted to log on to an
application set without providing a domain name, their session became
unresponsive.
[From Hotfix MPSE300W2K3R01][#80466]
144. Important: To get the benefits of this performance improvement, you must
do the following:
1. Install this fix.
2. Deploy MetaFrame Presentation Server Client for 32-bit Windows, Version
8.100.
3. Set the required registry keys (see below).
Transfers of large files over wide-are networks (WANs) tended to be slow
relative to the available bandwidth. This was caused, in part, by the earlier
design of the drive mapping feature. This fix, along with the MetaFrame
Presentation Server Client for 32-bit Windows, Version 8.100 and requisite
registry entries, results in significant performance gains for large file
transfers over WANs.
This fix resolves the situation by introducing a technique where data is
streamed without continually waiting for acknowledgments.
[From Hotfix MPSE300W2K3006][#82457]
145. With replicated SQL databases, the printer mapping changes were not
properly propagated to the server on the subscriber database IMA data store.
This was a result of latency in the underlying database replication.
This fix resolves the problem by populating the Local Host Cache (LHC) with the
printer mapping data and reading the printer mapping data directly from the
LHC, not the data store.
[From Hotfix MPSE300W2K3R01][#84528]
146. When an NDS user with an expired password attempted to refresh an
application set, a new, temporary session with an NDS password dialog box
should launch, asking the user to change the password. When the user changed
the password, the temporary session became unresponsive or logged into a
working desktop. The problem occurred when the user options in NDS were set to
User must change password at next logon and the users tried to log on to an
application set through Program Neighborhood using their NDS credentials.
Program Neighborhood launches a session so that users can change their
passwords. While creating this session, the code verifies if the domain name
sent the Program Neighborhood virtual channel is the same as the one obtained
from the logged on user token. The problem occurred because the NDS user name
and context were not being checked.
This fix ensures that NDS credentials will be verified.
[From Hotfix MPSE300W2K3R01][#84862]
147. A high number of printer drivers installed on servers caused the Local
Host Cache (LHC) to grow large and caused the synchronization of the drivers in
the data store to the LHC to take a long time.
With this fix, the synchronization logic was changed to speed up
synchronization time.
[From Hotfix MPSE300W2K3R01][#85052]
148. This is a request for a feature change enhancement involving the following
three scenarios:
1. If Create browser listener on UDP network was not checked in the
Presentation Server Console, typing qfarm.exe /tcp at a command prompt did not
display the server nor did the server and its IP address appear in the command
qfarm.exe.
2. If Create browser listener on IPX network was not checked in the
Presentation Server Console, typing qfarm.exe /ipx at a command prompt did not
display the server nor did the server and its IP address appear in the command
qfarm.exe.
3. If Create browser listener on NetBIOS network was not checked in the
Presentation Server Console, typing qfarm.exe /netbios at a command prompt did
not display the server nor did the server and its IP address appear in the
command qfarm.exe.
This enhancement ensures that the behavior described in the three scenarios no
longer occurs.
[From Hotfix MPSE300W2K3R01][#85071]
149. The IMA Service sometimes experienced a fatal error when an administrator
viewed, added, or deleted users on the node of a published application from the
Presentation Server Console. This occurred because one function of the IMA
Service was not checking the error code correctly.
This fix ensures that the function of the IMA Service correctly checks the
error code.
[From Hotfix MPSE300W2K3R01][#86433]
150. After reconnecting to disconnected seamless sessions, the foreground
window logic sometimes became invalid in Windows 2003 Server environments.
This fix ensures that after reconnecting, users can get any seamless window
into the foreground successfully.
[From Hotfix MPSE300W2K3010][#86485]
151. Because of changes in Microsoft's IDL compiler (MIDL) in Visual
Studio.Net, IMA RPC communications exposed an error in the Microsoft RPC
runtime that created a memory leak in the IMA Service.
This fix changes the behavior of Microsoft's IDL compiler in Visual Studio.Net
to revert to generating mixed mode stubs for the IMA RPC functions and the
memory leak in the IMA Service no longer occurs.
[From Hotfix MPSE300W2K3R01][#86641]
152. You were unable to add MST packages from either the Add Package Wizard or
from Package Properties > Add MST File. This was caused by a conflict between
the original MSI file and the MSI file generated by Installation Manager, which
included the transfers and was thus different from the original MSI file.
[From Hotfix MPSE300W2K3R01][#86765]
153. If users had several seamless windows open in a session that supports the
Windows XP Themes and Shaped Windows feature and they resized, maximized, and
restored the windows multiple times, occasionally, the seamless windows were
not fully redrawn or even disappeared completely from the screen. The support
of "shaped" windows requires that extra information be delivered from the
server to the client. Occasionally, this information arrived at the client in
the wrong order, which caused the problems with drawing the windows properly on
the client.
This fix ensures that the extra information required for rendering "shaped"
windows arrives in a proper sequence so that the windows are properly redrawn
on the client.
[From Hotfix MPSE300W2K3007][#86943]
154. Under rare circumstances, servers running MetaFrame Presentation Server
3.0 for Windows would unexpectedly trap, with the system dump displaying the
following information:
BugCheck 8E, {c0000005, bfa3a823, b65e9204, 0
This was caused by a source code variable being accessed before it was
initialized.
[From Hotfix MPSE300W2K3R01][#87483]
155. When using the CHANGEFARM (chfarm.exe) utility to change the membership of
a server running MetaFrame Presentation Server 3.0 for Windows to a farm that
used a different license server, the server continued to use the previous
license server until you restarted the server or modified the server's license
server properties from the Presentation Server Console.
This fix corrects the issue so that you no longer need to restart the server or
modify its license server properties.
[From Hotfix MPSE300W2K3R01][#87688]
156. Applications sometimes stopped running if they were configured to use Word
Wrap when Local Text Echo was enabled. The problem resulted from a buffer
overrun
This fix resolves the problem by verifying the buffer sizes and applications no
longer stop running if they are configured to use Word Wrap when Local Text
Echo is enabled.
[From Hotfix MPSE300W2K3R01][#87756]
157. This is an enhancement allowing you to limit the list of file types to be
redirected from server to client. By default, server-to-client content
redirection redirects all or none of the following file types: http, https,
rtsp, rtspu, pnm, and mms.
A new registry key is specified to allow certain file types to be excluded from
content redirection. If HKEY_LOCAL_MACHINE \SOFTWARE\Citrix\SFTA
\DisableServerFTA is set, the multistring registry value
HKEY_LOCAL_MACHINE\SOFTWARE \Citrix\SFTA\NoRedirectClasses specifies which file
types are excluded from redirection. If the file type is not in the list, it is
redirected.
To implement this enhancement, make the following value changes to the registry
key using regedt32:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\SFTA
Name: DisableServerFTA
Type: REG_DWORD
Data: 1
Name: NoRedirectClasses
Type: REG_MULTI_SZ
Data: Specify any combination of the following values: http, https, rtsp,
rtspu, pnm, or mms
Note: The values must be line-delimited, for example:
http
https
rtsp
[From Hotfix MPSE300W2K3R01][#88380]
158. This is an enhancement allowing you to redirect specific URLs from server
to client, without redirecting other URLs.
A new registry key, HKEY_LOCAL_MACHINE \SOFTWARE\Citrix\SFTA\ValidSites, lets
you specify URLs to be redirected from server to client.
To implement this enhancement, make the following value changes to the registry
key using regedt32:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\SFTA
Name: ValidSites
Type: REG_MULTI_SZ
Data: Specify any combination of URLs
Note: The values must be line-delimited, for example:
www.my_URL.com
*.my_URL.com
The asterisk (*) is supported as a wildcard character.
[From Hotfix MPSE300W2K3R01][#88382]
159. QUERYFARM (qfarm.exe) utility: The utility failed to return data after a
large number of servers in a farm were restarted. This was caused by a number
of read-only objects preventing the utility from returning data.
[From Hotfix MPSE300W2K3R01][#88608]
160. If the DisableError registry value was turned to ON and client printer
auto-creation fails with the native printer driver but succeeds with UPD, Event
ID 1106 was logged in the event log. This occurred because the registry value
was not checked.
This fix ensures that the registry value is checked so that EventID 1106 will
not be logged.
[From Hotfix MPSE300W2K3017][#89250]
161. After a user created a custom ICA connection and connected to the server
desktop, no client printers were auto-created in the Printers folder. The port
monitor enumerated all existing ports on the system before creating the port
for the auto-created printer. It did not properly catch the error condition and
incorrectly reported that the port to be auto-created already existed.
Note: After applying this fix, you must restart the spooler service.
[From Hotfix MPSE300W2K3R01][#90244]
162. Users could not print using the Novell iprint (Internet) client. In
addition, users could not print using any Internet printer with names that
contained http://, https://, or ipp://. A print job initiated in a session for
one of these printers spooled to the server's print queue but never reached the
client's local print queue.
Windows 2003 does not allow printer names to contain backslashes. During
printer creation on the server, backslashes ( \ ) are stored as forward slashes
( / ). When auto-created printers are initialized, the forward slashes are
converted to backslashes. This process changed the names of printers that
contained http://, https://, or ipp://.
This fix preserves Internet printer substrings that are of the form http://,
https://, and ipp://. Printer jobs queued to Internet-based printers now print
with no problem.
[From Hotfix MPSE300W2K3R01][#83548]
163. Kana lock of Japanese IME turned off unexpectedly when focus was on an ICA
session connecting to a Presentation Server /Windows 2003 Server.
On Windows 2003 Server, the Terminal Service checks the keyboard attribute
before notifying the keyboard drivers of the KANA_LOCK status change. Even
though the client had a Japanese keyboard, Presentation Server was not
receiving the KANA_LOCK flag because the client continued to tell Terminal
Services to recognize the attached keyboard as an English 101 keyboard.
With this fix, even when the client has a Japanese keyboard, the Kana lock
state is preserved.
[From Hotfix MPSE300W2K3006][#82739]
164. Users may not have been able to switch between seamless application
windows after reconnecting to a session. This happened when the global system
time-out value, which sets the amount of time following user input during which
the system does not allow applications to force themselves into the foreground,
was not successfully set to 0. Applications could not set the time-out value
unless they owned the foreground window.
[From Hotfix MPSE300W2K3016][#86405]
165. If a new session was started upon a failure to reconnect to a disconnected
seamless session, the disconnected seamless window may not have been properly
displayed.
[From Hotfix MPSE300W2K3017][#87317]
166. Instance limits for published applications were occasionally enforced
incorrectly when you connected to several published applications at the same
time. This means that when you connected to a second published application, an
error message may have appeared, stating the instance limit for the application
had been reached when, in fact, it had not.
[From Hotfix MPSE300W2K3016][#91714]
167. The following is a feature enhancement provided in response to customer
requests: In MetaFrame Presentation Server 3.0, seamless connections from
Program Neighborhood Agent and the Web interface honor session sharing over
server zone preference levels. Support has been added for honoring zone
preference levels over session sharing.
Before activating this new functionality, consider the following limitations:
? With this functionality activated, only Users policy filters are supported;
the Client IP Address, Client Name, and Servers policy filters are not
supported.
? Connections from Program Neighborhood may not result in session sharing.
To activate this new functionality, you must set the following registry key on
each server:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\IMA\MFRPC
Name: HonorZPFOverSessionSharing
Type: REG_DWORD
Data: 1
[From Hotfix MPSE300W2K3R01][#86365]
168. When a least loaded server was unresponsive, the data collector continued
to resolve connections to the server. The data collector sent all new
connection attempts and/or ticket requests to that server even though that
server could not respond to these requests. This sometimes caused the entire
server farm to become unresponsive.
If a server is not responding to a ticket request, the data collector is
notified to update the server's load to maximum. This prevents any new ticket
requests to that server. This prevents an unresponsive least loaded server from
causing a farm to become unresponsive.
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 to the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CtxHttp\SocketTimeout
Name: SocketTimeout
Type: REG_DWORD
Data: Time-out number value in milliseconds
[From Hotfix MPSE300W2K3R01][#87613]
169. When changing client display settings before reconnecting to a server, the
tray icon of Password Manager occasionally displayed transparent or invisible.
[From Hotfix MPSE300W2K3R01][#87609]
170. Users were unable to apply the foreign language versions of the following
transforms to the mps.msi file:
? Support/Install/Join_Indirect.mst
? Support/Install/localdb_access_create.mst
? Support/Install/Thirdpartydb_create_direct.mst
? Support/Install/Thirdpartydb_join_direct.mst
The issue occurred because of a codepage dependency.
[#89695]
171. On occasion, when connecting to a server, an error message appeared
stating that the logon limit had been reached, even if the limit had not been
reached. The issue occurred when a server lost and then reestablished its
connection to the license server. Upon losing their connection to the license
server, servers create several temporary registry keys that are supposed to be
removed when the connection is reestablished. The temporary keys were not
removed.
[#90208]
172. The Load Manager monitor displayed zeroes for all values to Citrix
administrators with view-only privileges.
[#90619]
173. A "Server busy" dialog box appeared during the rollback process of
Installation Manager's packager. The issue was caused by a lengthy COM
operation.
[#94830]
174. When a custom administrator with rights to "Edit Load Evaluators" tried to
enable load evaluator logging, the following error message appeared: "Error
turning on/off logging. Error Code: 80000016" and logging was not enabled. The
issue occurred because custom administrators with rights to edit load
evaluators did not have the right to enable logging.
[#96098]
175. Using Windows Explorer, if users attempted to copy a file to the same
folder on a mapped drive in Windows Server 2003, the file copy failed and an
error message appeared. In Windows 2000, the file was copied with a ?Copy of?
prefix.
[#96424]
176. After closing modal dialog boxes of certain published applications in
seamless mode, focus occasionally went to other windows on the client desktop
rather than to the application that launched the dialog, and users had to click
the seamless application title bar to get focus back to the application.
Applications affected by this issue use a zero-sized window at coordinates
(0,0) to hold focus between the time the modal dialog closes and the time the
application window is reenabled. The seamless code recognized this window as
invisible and, therefore, did not send seamless protocol messages to it.
Although this behavior was as designed, it was considered inconvenient by
users, and this hotfix corrects the issue.
[#95001]
177. During startup, servers running Presentation Server may have experienced a
fatal error. The issue was caused by a race condition.
[#100739]
178. ICA sessions failed to launch the associated media player for URLs
starting with mms:// and the multimedia files did not play back.
[#103537]
179. If an application performed a specific action upon pressing the Escape
key, switching from a seamless window with a menu open to a desktop window
caused that action to be executed, even if the Escape key was not pressed.
[#104173]
180. The Shadow taskbar password was limited to 14 characters.
This release adds support for passwords up to 30 characters long.
[#104860]
181. Occasionally, servers experienced fatal errors indicating a 0x7F - kernel
stack overflow. The issue occurred in combinations of older versions of a
Hewlett Packard network interface card and the Citrix video driver vdtw30.dll
running in ThinWire 1 mode. Occasionally, this combination produced a stack
overflow because too much memory was allocated to the stack in nested function
calls.
[#105825]
182. When launched from a URL shortcut on a published desktop, Internet
Explorer opened in the background without taking keyboard focus. The issue
occurred if client-to-server content redirection was not enabled.
[#108162]
183. Smart card applications running in client sessions appeared slow when
polling for smart card status changes. Wait times during such polls were
considerably longer than those specified for wait time-outs. The issue occurred
because an incorrect multiplier was used to compute the wait timer.
[#111045]
184. With NTLM 2.0 enabled, the shadow taskbar launched successfully even if
users entered an invalid password. The issue occurred because the incorrect
logon was not being identified.
[#111812]
185. When logging on to a published application, servers occasionally
experienced a fatal error. The issue was caused by a buffer overflow.
[#113848]
Conferencing Manager for Citrix Presentation Server
1. When users logged onto a farm with a particular zone preference, the zone
preference was not being used in conference rooms. This occurred because
Conferencing Manager did not support zone preferences.
This fix adds zone preference support to Conferencing Manager and zone
preferences are handled properly.
[From Hotfix MCM300W001][#82947]
2. When the network had multiple Active Directory servers and replication was
set to take place at selected intervals instead of when a change occurred,
guest attendees could not gain access to a conference. Guest attendees were
being activated and reset on one server, but the guest logging on was
authenticating against another server, causing an authentication failure.
This fix allows the disable/enable/reset password features to be disabled for
guest attendees, removing the need for replication to occur to update account
information.
To resolve the problem, you need to create a new registry value as follows:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\CMCM\VisitingAttendee
Type: REG_DWORD
Value: DoNotDisableAccountsAndChangePasswords = 1
After setting the registry value, set the number of guest attendees to zero in
the Conferencing Manager Configuration tool, click Apply, then set the number
back to whatever number you want to be available. This deletes and recreates
the guest attendees.
Guest attendees will now authenticate correctly.
Note: Allow sufficient time for Active Directory replication to complete before
the newly created guest attendees appear on all domain controllers.
[From Hotfix MCM300W003][#85629]
3. When the Conferencing Manager user interface displayed a meeting list where
meetings were taking place on more than one conference room server, the
attendee lists for those meetings was reflected correctly only on one of the
conference room servers. This occurred because the user interface failed to get
events for the selected meeting if another meeting taking place on a different
server was previously selected.
This fix ensures all Conferencing Manager interfaces point to the same server
at all times. Attendee lists appears correctly when meetings take place on more
than one server.
[From Hotfix MCM300W010][#88492]
4. Conferencing Manager sometimes became unresponsive when resetting a CRoom
session from the Management Console. This occurred because some callback events
were being processed by a worker thread instead of being processed by the user
interface thread.
This fix ensures that the callback events post a user interface event that is
handled by the user interface thread.
[From Hotfix MCM300W010][#88875]
5. Occasionally, servers experienced a fatal system error when you started a
conference. This was caused by a memory corruption in CMCM.exe.
[From Hotfix MCM300W011][#89319]
6. Clicking Join and then clicking Join again while waiting to join a
conference caused users to be disconnected from the pending connection attempt.
With this fix, the cursor changes to an hourglass after you click Join, to
indicate that the connection is in progress and to prevent users from clicking
Join more than once.
[From Hotfix MCM300W011][#91105]
7. Upon joining a conference, attendees sometimes had keyboard and mouse
control even if the organizer specified that they not have control.
[From Hotfix MCM300W012][#97825]
Other related posts:
- » [THIN] KB: CTX105682 - MetaFrame Presentation Server 4.0 Fixed Issues EN
