[THIN] KB: CTX107783 - Hotfix Rollup Pack XE104W2K3R02 - For Citrix MetaFrame XP 1.0 for Windows Server 2003

  • From: "Jim Kenzig http://kenzig.com" <jimkenz@xxxxxxxxxxxxxx>
  • To: thin@xxxxxxxxxxxxx
  • Date: Fri, 27 Jan 2006 06:37:44 -0800 (PST)

CTX107783 - Hotfix Rollup Pack XE104W2K3R02 - For Citrix MetaFrame XP 1.0 for 
Windows Server 2003 
  This document was published at: http://support.citrix.com/article/CTX107783 
    Document ID: CTX107783, Created on: Jan 26, 2006, Updated: Jan 26, 2006   
Products: Citrix MetaFrame XP 1.0 for Microsoft Windows 2003 

 Attachment: XE104W2K3R02.msp (11.9 MB) 
               Hotfix readme name: XE104W2K3R02.HTM
Hotfix package name: XE104W2K3R02.MSP
For: MetaFrame XP 1.0 with Feature Release 3/Service Pack 4 for Windows Server 
2003
Replaces: XE104W2K3001, XE104W2K3002, XE104W2K3003, XE104W2K3004, XE104W2K3005, 
XE104W2K3006, XE104W2K3007, XE104W2K3008, XE104W2K3009, XE104W2K3010, 
XE104W2K3R01, XE104R01W2K3006, XE104R01W2K3011, XE104R01W2K3012 
Date: January, 2006
Language supported: English (US) 
Readme version: 1.0 
  Note: You can apply this hotfix rollup pack only to a Windows Server 2003 
with MetaFrame XP Version 1.0 with Feature Release 3 and Service Pack 4 
installed. 
  Where to Find Documentation
  This document describes the issue(s) solved by this hotfix and includes 
installation instructions. You can find more information about MetaFrame XP for 
Windows in the Administrator's Guide. The Administrator's Guide is in the \DOCS 
directory on the Citrix MetaFrame Server CD. All product documentation is also 
available from the Citrix Web site at http://www.citrix.com/support.
  The Administrator's Guide is in an Adobe Portable Document (PDF) format file. 
To view, search, and print the documentation, you need Adobe Reader 5.0.5 or 
later with Search. You can download the Reader for free from the Adobe Web site 
at http://www.adobe.com.
  Important Note about this Release
  See knowledgebase article CTX107233 for important information about upgrading 
from this hotfix rollup pack to Presentation Server 3.0. 
  Known Issue(s) in this Release
    ? Installation of this hotfix rollup pack hides the listing of replaced 
hotfixes and hotfix rollup packs in Add/Remove Programs. For more information, 
see knowledgebase article CTX108735.
  ? If certain hotfixes for MetaFrame XP 1.0 with Feature Release 3 are 
installed on a server, you may be prompted for your MetaFrame installation CD 
when attempting to uninstall this hotfix rollup pack.
  ? Installing and/or uninstalling this hotfix rollup pack may prompt you to 
close the ICA Administrator Toolbar and/or other applications that are running. 
You can safely ignore the prompt or close the specified application(s) and 
continue the install/uninstall process. [#121727]
  ? While installing or uninstalling this hotfix rollup pack, you may encounter 
an error message indicating that the file SmartCardHookBackup.reg cannot be 
exported. You can safely ignore this error and click OK. [#122467]
  ? On computers running Windows Server 2003 with Service Pack 1, published 
application sessions take 60 seconds to log off. For more information about 
this issue, see CTX106049. 
  ? Upgrading from this hotfix rollup pack to Presentation Server 3.0 or 4.0 
removes the rollup pack from the system as designed, but may fail to remove its 
entry from the Add/Remove Programs Control Panel. It is safe to remove the 
entry from the Control Panel by selecting the entry and clicking Change/Remove. 
If you experience difficulty removing the entry, see Microsoft knowledgebase 
article Q243723 for more information.

  Issue(s) Resolved in this Release
  Caution! Several items in this hotfix require you to edit the registry. Using 
Registry Editor incorrectly can cause serious problems that may require you to 
reinstall your operating system. Citrix cannot guarantee that problems 
resulting from the incorrect use of Registry Editor can be solved. Use Registry 
Editor at your own risk. 
    1. When using a Unicode client (UNIX or Mac) to access an application that 
detects its own up/down keystrokes, modified keystrokes (shift, ctrl, alt + 
character) are not handled correctly. 
  [From XE104W2K3R02][#96945]
  2. Sessions may be logged twice in the summary database. 
  [From XE104W2K3R02][#97670]
  3. Disconnected sessions are displayed as active or not displayed at all in 
the Management Console. 
  [From XE104R01W2K3006][#104720, #129862] 
  4. The IMA Service becomes unresponsive at random, and XML browsing fails 
intermittently during such times. The issue is caused by buffer overruns. 
  [From XE104W2K3R02][#104828]
  5. Shadowing from the Management Console over RDP fails, and the following 
error message appears: "Error: Shadow failed. Error code 7050." This occurs 
because the console does not properly detect whether the shadower is logged on 
over ICA or RDP. Subsequently, shadowing fails unless the shadower is logged on 
over ICA. 
  [From XE104W2K3R02][#105619]
  6. The IMA Service will not start if an application has more than 255 file 
extensions associated with it. This occurs because the code is limiting the 
number of supported file types to 255. 
  [From XE104W2K3R02][#106084]
  7. If the language of the operating system and/or the ?Automatically adjust 
clock for daylight saving changes? setting is different between server and 
client, Java published applications display the time configured for the server. 
  [From XE104W2K3R02][#109706]
  8. With NTLM 2.0 enabled, the shadow taskbar launches successfully even if 
you enter an invalid password. This occurs because the incorrect logon is not 
being identified. 
  [From XE104W2K3R02][#111812]
  9. The session shadowing dialog box displays all discoverable servers, 
regardless of the user's permissions to those servers. However, as designed, 
users can shadow sessions only on servers to which they have permissions. 
  [From XE104W2K3R02][#112820]
  10. IMA queries to the SQL database are blocked and the SQL server process 
cannot be terminated. This occurs because when IMA queries to the SQL database 
time-out, the SQL connections are not closed properly. Subsequent IMA queries 
result in additional open SQL connections. 
  This fix introduces a new registry entry that allows you to delay the next 
connection attempt to the SQL database after a time-out. 

  Create the following registry entry: 
  HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\IMA
Name: DB_TIMEOUT_DELAY 
Type: REG_DWORD
Data: <time-out delay, in seconds> 
  The following Event Viewer entries will be written to the Event Viewer on the 
affected server: 
  EventID: 3623
MSG_DSDRIVER_DB_CONNECTION_TIMEOUT_WARNING
The Database Server hosting the Citrix data store has failed to respond to an 
IMA query in a timely fashion. This may be an indication of problems with the 
network, name resolution, or problems with the Database Server hosting the 
Citrix data store. 
  EventID: 3624
MSG_DSDRIVER_DB_CONNECTION_TIMEOUT_ERROR
The Database Server hosting the Citrix data store has failed to respond to an 
IMA query in a timely fashion. This may be an indication of problems with the 
network, name resolution, or problems with the Database Server hosting the 
Citrix data store. 
  [From XE104W2K3R02][#113648]
    11. Autocreated printers with names containing one of the following strings 
fail to print from sessions on servers running Windows Server 2003. This occurs 
because incorrect printer names were sent to the client: 
    o RICOH Aficio 350/355 PCL 6
  o Minolta PageWorks/Pro 20 PS
  o Generic / Text only

  [From XE104W2K3R02][#114103]
  12. Users may not be able to use Internet Explorer to view URLs or files with 
file names or file paths that contain spaces, commas, or non-standard 
characters when using DDE (WM_DDE_EXECUTE) to launch files within the same 
instance of Internet Explorer. This occurs because DDE requires parameters 
containing non-standard characters to be passed in quotes, which is not being 
done. 
  [From XE104W2K3R02][#114190]
  13. Uninstalling Service Pack 4 for MetaFrame XP 1.0 with Feature Release 3 
fails to uninstall hotfixes for Service Pack 4. This occurs because the 
ProductVersion property is not being updated properly. 
  [From XE104W2K3011][#114403]
  14. Users cannot create folders on mapped drives using the xcopy or mkdir 
commands from a command line. This occurs because the original file name rather 
than the canonical form is passed to the client drive mapping policy check 
routine. 
  [From XE104W2K3R02][#114983]
  15. When an application set refresh request is done from a client using Smart 
card authentication, the refresh request may be routed to a server where logons 
are disabled. As a result, the refresh request fails and the following message 
appears: "Remote logins are currently disabled." This occurs because the 
mechanism used to route the refresh request does not consider the state of the 
destination server before routing the request there. 
  [From XE104R01W2K3012][#115473]
  16. On Linux clients, the Caps Lock state is not maintained properly after 
you press the Caps Lock key, then any key, and then release the Caps Lock key. 
  [From XE104W2K3R02][#115747]
  17. IBM Blade servers experience random fatal errors. This occurs because a 
mutex object is initialized by multiple threads though it should be initialized 
only once. 
  [From XE104W2K3R02][#116304]
  18. When run in seamless mode, separate icons for each spreadsheet or slide 
are not present in the taskbar for Microsoft Excel and Powerpoint. This occurs 
because seamless environments do not contain a taskbar. To resolve the issue in 
its entirety, you must also install Hotfix Client 9.154 or later of the 
Presentation Server Client.
  [From XE104W2K3R02][#116561]
  19. On occasion, you cannot configure a published application count metric. 
This occurs when multiple published applications by the same names exist in 
multiple folders. 
  [From XE104W2K3R02][#116582]
  20. On occasion, servers experience a fatal error, displaying a blue screen. 
This occurs immediately after submitting user credentials when reconnecting to 
a disconnected session. 
  [From XE104W2K3R02][#116806]
  21. This fix adds support for Oracle data store query time-outs. The IMA 
Service becomes unresponsive when queries to Oracle data stores do not time out 
properly. This occurs because the IMA code responsible for handling Oracle 
queries does not support time-outs. This fix adds support for two registry 
settings that let you specify the amount of time after which unsuccessful 
Oracle queries time out, and the amount of time by which subsequent queries are 
delayed. 
  To specify Oracle data store query time-outs, you must set the following 
registry keys: 

HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\IMA
Name: DB_CONNECTION_TIMEOUT
Type: REG_DWORD
Data: time (in seconds) 

  Note: DB_CONNECTION_TIMEOUT may be off by several minutes because it takes 
that long for the Oracle APIs to respond.
  HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\IMA
Name: DB_TIMEOUT_DELAY
Type: REG_DWORD
Data: time (in seconds) 
  [From XE104W2K3R02][#116838]
    22. On occasion, while users are in the process of logging on, their 
sessions become unresponsive, displaying a blue screen background only. While 
existing sessions are not affected, no additional sessions can be launched 
until the server is restarted. This occurs when there is a transient connection 
failure during the logon process that results in a call time-out. 
  [From XE104W2K3R02][#116869]
  23. The "DISABLE FULL WINDOW DRAG" registry setting [0xc00 (0x800+0x400)] for 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI\SeamlessFlags
 is not working as expected. As a result, users cannot see the contents of 
windows they are moving with the mouse. 
  [From XE104W2K3R02][#116981]
  24. Servers experience periodic fatal errors, displaying a blue screen. This 
occurs when SpeedScreen Browser Acceleration is enabled and is caused by data 
being queued before the requisite queue and toss buffers are initialized. 
  [From XE104W2K3R02][#117576]
  25. Servers experience periodic fatal errors, displaying a blue screen and 
producing the following error message: "KMODE_EXCEPTION_NOT_HANDLED (1e)." The 
issue is caused by the vdtw30.dll file and occurs because of the way cyclic 
redundancy checks for ThinWire 2 are handled. 
  [From XE104W2K3R02][#117992]
  26. On occasion, you cannot add or edit a printer driver mapping in the 
Management Console. This occurs when the Driver Mapping List contains one or 
more corrupt entries, which causes the console to loop through the drivers 
multiple times until it runs out of memory. 
  [From XE104W2K3R02][#118400]
  27. On occasion, adding or removing package groups to or from Installation 
Manager fails. This occurs when the package group cannot be read from the data 
store. 
  [From XE104W2K3R02][#118612]
  28. With load balancing enabled, certain servers receive significantly more 
sessions than others, eventually overloading those servers. This occurs when 
CPU or memory performance queries produce an error. The error results in 
MetaFrame reporting zero CPU or memory usage for those servers, and subsequent 
session resolutions are directed to those servers.
  This fix corrects the issue by setting the server load to FULL for servers 
that produce errors during performance queries. 
  [From XE104R01W2K3006][#119402]
  29. On occasion, the process WFSHELL.EXE exits unexpectedly. This occurs when 
the device driver has device-specific information and the allocated data size 
is insufficient for the private driver data.
  [From XE104W2K3R02][#119672]
  30. Running the QUERYDS utility returns server values different from those 
set for load evaluators from the Management Console. This occurs because 
changes to load evaluator rules do not take effect until you restart the IMA 
Service. 
  [From XE104W2K3R02][#119879]
  31. On occasion, updating printer and driver information from the server node 
of the Management Console does not work properly. This occurs when you add or 
delete a printer or printer driver for a server remotely without refreshing the 
printer/printer driver information view from the console on that server. It is 
caused by the printer subsystem DLL's inability to forward an update request to 
a single remote server. 
  [From XE104W2K3R02][#120136]
  32. This feature enhancement introduces support for session sharing on fully 
loaded servers. Without this fix, session sharing does not work on fully loaded 
servers. Instead and as designed, users are load balanced to less busy servers. 
To enable this feature enhancement, you must set the following registry key: 
  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI\
Name: SeamlessFlags 
Type: REG_DWORD
Data: 0x100

  [From XE104W2K3R02][#120874]
    33. Servers experience a fatal error, displaying a blue screen. This occurs 
during times of high activity resulting from printing to mapped ports and/or 
file copying to mapped client drives and is caused by a race condition in the 
Citrix CDM redirector code.
  This fix corrects the issue. 
  [From XE104W2K3R02][#121051, 121109]
  34. The amount of Microsoft license information in the data store tends to 
grow very large. This occurs because each time a non-Windows client logs on to 
a computer running MetaFrame, the Microsoft license information obtained by 
MetaFrame is replicated to the data store. If MetaFrame obtains the same 
license information multiple times, the same information is replicated each 
time.
  [From XE104W2K3R02][#121063]
  35. After applying Service Pack 4 for MetaFrame XP 1.0 with Feature Release 
3, remapping LPT ports in ICA sessions to client COM ports fails. The following 
error messages appear instead: "System error 67 has occurred" and "The network 
name cannot be found." This occurs because the code is not checking for 
"\\client\" as a valid name when mapping LPT ports.
  [From XE104W2K3R02][#121743]
  36. This fix resolves the following issues related to the enforcement of 
application limits:
    o Application limits of "0" and "1" are not enforced for certain published 
applications [#97994, 121849] 
  o When reconnecting to disconnected sessions, users may receive an error 
message stating that the application limit has been reached [#120939]

  [From XE104W2K3R02][#121849]
  37. In seamless connections, double-byte characters may display incorrectly. 
This occurs when the server does not have the same fonts available as the ones 
being used by the client workstation. In that case, the Seamless Engine uses 
other installed server fonts, and double-byte characters are displayed 
incorrectly if the substitution fonts do not support double-byte characters. 
  [From XE104W2K3R02][#121975]
  38. The IMA Service may return an error when adding printers to the 
compatibility list. This occurs because Presentation Server examines 
distinguished (mapped) names rather than driver names and fails to add new 
driver entries to the data store if those new entries match existing 
distinguished names. 
  [From XE104W2K3R02][#121977]
  39. In Visio 2003, the "Smooth drawing" and "Higher quality shape display" 
options under Tools > Options > View > Display Options are grayed out and their 
state cannot be changed. This occurs because Presentation Server was disabling 
menu animations in sessions. With menu animations disabled, Visio 2003 disables 
those display options. 
  [From XE104W2K3R02][#122489]
  40. Installing Hotfix Rollup Pack 1 for MetaFrame XP Version 1.0 with Feature 
Release 3 and Service Pack 4 may cause aginst.exe, a command-line utility for 
Installation Manager, to be removed from the system. 
  [From XE104W2K3R02][#122903]
  41. The Management Console does not properly display the state of 
disconnected sessions. This occurs because winstation queries do not update the 
IMA Service with reconnect/disconnect status changes. 
  [From XE104R01W2K3006][#123405]
  42. Servers experience a fatal error, displaying a blue screen when using CDF 
Tracing using MF_Driver_Cdm. This occurs when a CDF trace statement tries to 
print an improperly formatted buffer. 
  This fix corrects the issue. 
  [From XE104W2K3R02][#123645] 
  43. When using the MFCOM SDK to enumerate sessions, session IDs greater than 
9 cannot be enumerated. This occurs because the IMA Service is using a 
hexadecimal rather than a decimal session ID to search for sessions.
  [From XE104W2K3R02][#124118]
  44. When a published application programmatically inquires the screen's 
physical size, the value returned becomes dependent on the client's screen 
resolution rather than the default of 320x240. This occurs because the Citrix 
display driver is calculating the physical screen size depending on the screen 
resolution.
  [From XE104W2K3R02][#124293]
  45. On occasion, the MFCOM Service exits unexpectedly at startup. The issue 
is caused by an insufficient memory allocation.
  [From XE104W2K3R02][#124597] 
  46. After installing Service Pack 4, shadowed sessions and Java Clients are 
disconnected when the KeepAlive time-out is reached. With regard to the shadow 
sessions, the spawned shadow session would disconnect at approximately twice 
the time of the KeepAlive interval. This occurs because the addition of the 
icm_ping request to implement KeepAlives fails because shadow sessions and Java 
Clients do not respond to the ping request. 
  This fix corrects the issue. However, users of the Java Client Version 8.x 
must upgrade to Version 8.4.1693 or later of the client. 

  [From XE104W2K3R02][#124598]
    47. Entries added to the print driver auto-replication list are deleted 
after 24 hours. This occurs because regular replication jobs are deleted after 
24 hours if they do not complete; however, auto-replication jobs should not be 
deleted. With this fix, incomplete auto-replication jobs are no longer deleted. 
  [From XE104W2K3R02][#124759]
  48. New connections may cause continuous high server CPU utilization. The 
issue is related to a change to the seamless engine code introduced in Version 
3.0. This fix modifies the code change so that new connections no longer cause 
high server CPU utilization. 
  [From XE104W2K3R02][#124907] 
  49. On occasion, applications run in seamless mode start to react slowly to 
user commands. Specific functions may fail and eventually render the user 
session unresponsive. The issue is caused by a handle leak.
  [From XE104W2K3R02][#124670]
  50. On occasion, servers experience a fatal error, displaying a blue screen. 
This occurs when a CDF trace statement is trying to print a buffer that is not 
null-terminated.
  [From XE104W2K3R02][#125510]
  51. After applying Hotfix Rollup Pack 1, printing to client COM or LPT ports 
may be slow. 
  [From XE104W2K3R02][#125892] 
  52. After applying Hotfix Rollup Pack 1, sessions launched by way of a batch 
file or script fail to display under the individual server nodes in the 
console. The sessions do display in the Citrix Server Administration tool and 
when using command-line utilities such as quser or qwinsta. This occurs because 
the IMA Service is not being updated with winstation reconnect/disconnect 
status change information. 
  [From XE104R01W2K3006][#126260]
  53. At times of heavy utilization, servers experience a fatal error, 
displaying a blue screen, while clients are connecting. The issue is caused by 
a thread synchronization problem between TSCAL license requests and worker 
thread pings. 
  [From XE104W2K3R02][#126412] 
  54. When generating a report, the following error message may appear in the 
Management Console: 
  "The report Server Snapshot : [...] contains too much data to be displayed by 
the Management Console." 

  This fix corrects the issue; however, you may continue to see the error 
message depending on the number of open report windows. 
  [From XE104W2K3R02][#126549]
    55. Servers experience a fatal error, displaying a blue screen on CDM.sys. 
This occurs when an application is accessing drive A in a session using "A:" 
rather than "A:\" or if it is the first process to access a client drive in a 
session. The issue is caused by a legacy optimization routine. 
  This fix corrects the issue by removing the legacy optimization routine. 
  [From XE104R01W2K3010][#126580]
  56. Servers may restart unexpectedly. The issue is caused by the wdica.sys 
file and occurs because two resource locks are not released when the driver is 
unloaded. 
  This fix corrects the issue. 
  [From XE104W2K3R02][#126585] 
  57. On occasion, servers stop working unexpectedly, producing the following 
output: 
  BugCheck D1, {54, 2, 0, f759d2f6}
Probably caused by : termdd.sys ( termdd!_IcaCancelTimer+20) 
  The issue is caused by a timing problem related to starting and closing the 
write timer. 

  [From XE104R01W2K3012][#126608] 
    58. This fix applies the same benefit as fix #119402 in that it sets server 
loads to FULL for servers that produce performance query errors. While fix 
#119402 does so if errors are reported during the query, fix #126653 does so if 
errors are reported when the query is initialized. 
  [From XE104R01W2K3012][#126653]
  59. Users may encounter the following issues when switching focus between 
applications in seamless mode:
    o Error messages appear stating "Invalid menu handle" 
  o User-invoked popup menus, such as those appearing when right-clicking 
window controls, disappear unexpectedly 

  The issues occur because MetaFrame closes certain types of windows if they 
appear to become unresponsive to change in focus events. 

  [From XE104R01W2K3011][#127287] 
    60. After installing Hotfix Rollup Pack XE104W2KR301, certain applications 
generate a memory error when exiting. 
  [From XE104W2K3R02][#128202] 
  61. Stopping the MFCOM Service may generate the following Dr. Watson error:
  "Could Not Stop the Metaframe COM Server service on local computer, Error 
1067: The process terminated unexpectedly. 
  This is caused by a reference to a deallocated application object. 
  [From XE104W2K3R02][#129552] 
  62. The file CDM.sys exits unexpectedly during times of heavy utilization. 
The issue is caused by an uninitialized stack variable.
  [From XE104R01W2K3012][#129601] 
  63. Not all Novell users in environments with multiple NDS contexts can 
launch published applications. The logic used to perform the query for 
authenticated user information from Novell NDS is incorrect for certain NDS 
contexts.
  [From XE104W2K3R01][#77856]
  64. The following is a feature enhancement to the dsmaint utility. Migrating 
the data store from an Oracle database to a SQL Server or a DB2 database may 
fail if the Oracle8 Client is installed on a server running a Japanese language 
Windows operating system. When you install the Oracle8 Client, you are prompted 
to select a language for database messages. If you select Japanese, Oracle's 
National Language Support (NLS) is set to JA16SJIS (Shift-JIS), which does not 
use UTF-8 character encoding. This results in compromised data when migrating 
the data store to other database products. This feature enhancement to the 
dsmaint utility allows you to recreate the compromised data. 
  To recreate compromised data at migration time, type the following at a 
command prompt: 
  DSMAINT MIGRATE /SRCDSN:dsn1 /SRCUSER:user1 /SRCPWD:pwd1 /DSTDSN:dsn2 
/DSTUSER:user2 /DSTPWD:pwd2 /RECREATEINDEX 

  To recreate compromised data outside of migration time, type the following at 
a command prompt: 
    DSMAINT RECREATEINDEX /DSN:dsn /USER:user /PWD:pwd 
  [From XE104W2K3006][#86413]
  65. You cannot add MST packages from either the Add Package wizard or from 
Package Properties > Add MST File. The issue is caused by a conflict between 
the original MSI file and the MSI file generated by Installation Manager, which 
includes the transfers and is thus different from the original MSI file.
  [From XE104W2K3R01][#86765]
  66. Applications try 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 does not 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 is hooked consistently and routed to the Smart card 
reader attached to the client. 
  [From XE104W2K3003][#87999]
  67. Adding an MSI package in Installation Manager causes the IMA Service to 
fail. The issue is caused by a memory allocation error that occurs when the 
install package contains more than 100 applications or shortcuts. 
  This fix corrects the issue by adding limit checks to prevent the buffer 
overrun condition and doubles the supported number of applications and 
shortcuts to 200. 

  [From XE104W2K3R01][#88320]
    68. 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 XE104W2K3010][#88382]
    69. Due to an access violation, a custom MFCOM application experiences a 
fatal error while attempting to obtain Citrix virtual channel policy 
information. This occurs because the reference count of the wrong MFCOM object 
is incremented, which results in the original MFCOM object being freed while it 
is still in use. 
  [From XE104W2K3001][#90079]
  70. When writing email in Lotus Notes over low latency connections with Local 
Text Echo enabled, text prediction changes to an illegible font. 
  [From XE104W2K3R01][#91605]
  71. Charts and graphs, and selected ranges of cells in Microsoft Excel 
spreadsheets experience excessive flickering if SpeedScreen Latency Reduction 
and Local Text Echo are enabled. 
  [From XE104W2K3R01][#91818]
  72. On occasion, ICA sessions do not assume a disconnected state when ICA 
KeepAlive is enabled. This occurs because ICA KeepAlivepackets rely on TCP 
retransmission time-outs rather than a client response to detect when a client 
disconnects. 
  [From XE104W2K3R01][#92145]
  73. In the Management Console, published applications that do not have a 
16x16 or 32x32 pixel icon show the Citrix icon by default. This occurs because 
the algorithm responsible for displaying the application icon recognizes only 
16x16 and 32x32 pixel icons. 
  This fix corrects the issue so that application icons with different 
dimensions are displayed properly. 
  [From XE104W2K3R01][#92320]
  74. In the Client Update Configuration utility, limits on the number of 
simultaneous client updates do not work properly. The limits work properly for 
clients connected with Administrator rights, but simultaneous updates to 
clients connected with User rights may exceed the limit you specified.
  [From XE104W2K3R01][#92858]
  75. In large farms, when replicating an updated version of a printer driver 
to a server that is using a previous version of the same driver, the update 
fails on the destination server even though the event viewer on the source 
server reports the update as successful. This occurs because the two versions 
of the specific driver have 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 XE104W2K3001][#92899]
    76. When accessing a Web page that contains an AlphaImageLoader object in a 
published instance of Internet Explorer in Program Neighborhood Version 7.1 or 
later, Internet Explorer experiences a fatal error. This occurs 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 occurs because the DLL's data structures are not initialized unless 
SpeedScreen Browser Acceleration is enabled.
  This hotfix modifies the DLL so that it works properly even if SpeedScreen 
Browser Acceleration is not explicitly enabled.
  [From XE104W2K3R01][#94109]
  77. If extended characters are used in elements of a seamless window, such as 
window titles or the notification area (system tray), the characters may 
display incorrectly if the server's system code page is different from the 
client's. This occurs because the extended characters are not translated 
accurately between server and client. 
  [From XE104W2K3005][#94146]
  78. The feature that allows you to limit application launches to one 
concurrent instance per user does not work when a user connects using a UPN 
name. This occurs because the Independent Management Architecture (IMA) 
Service, when comparing the user names associated with sessions that are 
already already open, does not check against UPN names.
  [From XE104W2K3001][#94371]
  79. Enumerating users from the shadow taskbar fails for sessions with session 
IDs greater than 255. This occurs because the session IDs are truncated to a 
single byte. 
  [From XE104W2K3R01][#94401]
  80. After upgrading to Service Pack 1 of Windows Server 2003, SpeedScreen 
Browser Acceleration does not work properly. SpeedScreen Browser Acceleration 
hooks into Internet Explorer. Due to changes in Service Pack 1, the hooks do 
not work as designed.
  [From XE104W2K3R01][#94723]
  81. You cannot browse nested organizational units (OUs) from the Management 
Console if the nested OUs have the same name as the parent OU. This occurs 
because the console uses string representation of user objects to perform 
object comparisons. For more complex container objects, such as Active 
Directory OUs, this approach is inadequate. 
  This fix corrects the issue by using LDAP for object comparison, so that you 
can browse same-name objects at different hierarchy levels from the console. 
  [From XE104W2K3009][#94762]
  82. On occasion, users cannot shadow other users or enumerate the necessary 
objects from the Shadow Taskbar (wshadow.exe). This fix corrects the issue and 
also introduces the following functionality change: 
  By default, only local and Citrix administrators can enumerate the 
Applications node. To enable other users to enumerate the node, you must create 
the following registry key: 

  HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\IMA 
  Name: EnableAppEnumForUsers
Type: REG_DWORD
Data: 0 (Disable) or 1 (Enable) 
    You must restart the IMA Service for the registry change to take effect. 
  [From XE104W2K3010][#94764]
  83. A "Server busy" dialog box appears during the rollback process of 
Installation Manager's packager. The issue is caused by a lengthy COM 
operation. 
  [From XE104W2K3R01][#94830]
  84. After closing modal dialog boxes of certain published applications in 
seamless mode, focus occasionally goes to other windows on the client desktop 
rather than to the application that launched the dialog box, and you must click 
on 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 box closes and the time 
the application window is enabled again. The seamless code recognizes this 
window as invisible and, therefore, does not send seamless protocol messages to 
it. 
  Although this behavior is as designed, it is considered inconvenient by 
users, and this fix corrects the issue. 
  [From XE104W2K3005][#95001]
  85. 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 XE104W2K3R01][#96289]
  86. Note: This fix requires Presentation Server Client Version 9.0 or later. 
File and folder names on mapped drives that contain non-ASCII characters appear 
garbled if the server is set to use a different system language. This occurs 
because the client drive mapping (CDM) server module supports only 
ANSI-to-Unicode conversion and other string related routines using its system 
default code page. 
  This fix corrects the issue in that the CDM module now supports multiple code 
pages. 
  [From XE104W2K3R01][#96892]
  87. After installing Service Pack 1 for Windows Server 2003, servers 
sometimes experience a fatal error while recording packages using Installation 
Manager. This occurs because the server code was accessing invalid locations.
  [From XE104W2K3R01][#97587]
  88. Connecting to servers over RDP causes excessive querying of the 
SessionTimeZone registry key. This occurs because the code does 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 XE104W2K3003][#98019]
    89. On occasion, copying content from local applications and pasting them 
in published applications fails on multiprocessor servers. The issue is 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 XE104W2K3R01][#98286]
    90. 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 occurs because NDS was not properly initialized, which caused user 
authentication to fail.
  [From XE104W2K3005][#98490]
    91. A custom Terminal Services API used to enumerate processes is causing a 
memory allocation error.
  [From XE104W2K3005][#100466]
  92. .CATproduct files located on mapped drives cannot be opened in client 
sessions. This occurs because the CDM module does not support byte range 
locking on files residing on client mapped drives. 
  [From XE104W2K3R01][#101192]
  93. In farms with more than one server, Smart card users cannot reconnect to 
disconnected sessions. This occurs because sessions of Smart card users are not 
associated with actual user or computer names; therefore the server hosting the 
disconnected session cannot be identified. 
  [From XE104W2K3001][#101409]
  94. The Management Console idle counters are not reset to zero in response to 
keystrokes. Instead, only mouse movements reset the counters. As result, 
sessions are disconnected when the idle time is reached if no mouse movements 
occur. 
  [From XE104W2K3R01][#101705]
  95. After reconnecting to a disconnected session, Smart card functionality 
within the session does not work properly until you remove and reinsert the 
Smart card in the reader. 
  [From XE104W2K3R01][#101762]
  96. Users without Windows user profiles and users whose profile was modified 
cannot launch published applications.
  [From XE104W2K3010][#101958]
  97. On occasion, mapped client drives are not mounted at logon time. This 
occurs because the client drive mapping (CDM) network provider is 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 XE104W2K3007][#102051]
  98. On occasion, the IMA Service becomes unresponsive unexpectedly. The issue 
is caused by a function with an invalid message handle. 
  [From XE104W2K3R01][#103129]
  99. If run on computers running Windows Server 2003, the shadow taskbar may 
become unresponsive while enumerating servers or users. This occurs because of 
an invalid memory address lookup.
  [From XE104W2K3005][#103290]
  100. Servers may experience a fatal error if you run Microsoft's Driver 
Verifier utility while users are logged on or logging on to the server using 
Smart cards. This occurs because of a lack of synchronization in the Smart card 
I/O control cancel handler.
  [From XE104W2K3R01][#103495]
  101. ICA sessions fail to launch the associated media player for URLs 
starting with mms:// and the multimedia files do not play back. 
  [From XE104W2K3010][#103537]
  102. On occasion, launching a published application from within a user 
session fails. 
  This fix corrects the issue.

[From XE104W2K3004][#103660]
  103. If a server has more than one network interface card (NIC), but not all 
cards are bound to ICA-TCP listeners, incoming ICA connections are attempted on 
all NICs, including those not bound to ICA-TCP listeners. This occurs because 
MetaFrame assumes that all NICs are bound to ICA-TCP listeners.
  [From XE104W2K3001][#104098]
  104. If an application performs a specific action upon pressing the Escape 
key, switching from a seamless window with a menu open to a desktop window 
causes that action to be executed, even if the Escape key is not pressed.
  [From XE104W2K3005][#104173]
  105. Microsoft Hotfix 867684 prevents ICA Keepalives from working. The issue 
is caused by an incorrect parameter. 
  [From XE104W2K3R01][#104698]
  106. If corrupt entries are in the policy table, enumeration fails. For 
example, if there are two valid entries and one invalid one, the valid data is 
ignored. When this occurs, users cannot view, add, or modify any policies. The 
issue is 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 XE104W2K3006][#104869]
    107. After applying Service Pack 1 for Windows Server 2003, applications 
for which SpeedScreen Latency Reduction is enabled do not launch properly. 
  [From XE104W2K3R01][#105789]
  108. On occasion, the IMA Service experiences a fatal error while performing 
load management tasks to select the least loaded server in a farm. This occurs 
because insufficient space is allocated for a local string, which causes a 
memory allocation error. 
  [From XE104W2K3008][#106078]
  109. No data is returned when running the qfarm command-line utility after 
restarting all servers in a farm. The issue is caused by faulty server 
read-only objects that prevent the utility from returning data. 
  Options were added to dsverify and dscheck to remove the faulty objects. Run 
dscheck or dsverify to restore the data store. 

  With this fix, the IMA Service resumes normal operation and the qfarm utility 
returns the correct data. 
  [From XE104W2K3006][#106118]
    110. The Citrix IMA and XML Services consume a lot of server CPU time at 
the expense of other tasks. This occurs primarily because of periodic updates 
made to the data store resulting from changes in the domain trust information. 
After the updates are made, the user management subsystem is notified of the 
changes and updates its tables accordingly. In a large environment with a large 
number of domains, this can impact the CPU utilization of the IMA Service when 
trust changes occur. 
  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 XE104W2K3002][#106642]
    111. When closing modal dialog boxes pertaining to seamless applications, 
focus goes to a local client window rather than to a window pertaining to the 
seamless application. 
  This occurs with a small number of legacy applications that do not support 
the design that gives users the Minimize All functionality in client sessions.
  [From XE104W2K3R01][#107258]
  112. When using pass-through authentication to log on to the Management 
Console and in farms with servers at different service pack or hotfix levels, 
published application icons may not display properly. The issue is caused by a 
new service ID introduced by more recent service packs but not supported by 
servers where those service packs are not installed.
  [From XE104W2K3009][#108075]
  113. Servers on which SpeedScreen Browser Acceleration is enabled 
unexpectedly restart at periodic intervals with memory dumps indicating the 
vdtw30.dll video driver to be at fault. This occurs due to improper error 
handling when older clients, which do not support ThinWire2 mode, are connected 
to the servers in ThinWire1 mode.
  [From XE104W2K3R01][#108173]
  114. If certain applications are configured to not start printing until the 
last page to be printed is received, the applications do not start printing 
until the application is terminated. Also, printing to a mapped printer from a 
pass-through session launched from within another session does not always work. 
On occasion, servers also experience a fatal error. This occurs because a 
resource release lock and a resource acquire lock calls are missing, which 
results in one thread acquiring the lock and a different thread releasing it.
  [From XE104W2K3R01][#108520]
  115. An access violation sometimes causes servers to experience a Terminal 
Services related blue screen. This occurs if the state of an anonymous user 
session becomes invalid during the logon or logoff process. The session state 
is not verified before calling a Microsoft API.
  [From XE104W2K3005][#108555]
  116. Shadowing does not work when shadow logging is enabled.
  [From XE104W2K3R01][#108658]
  117. Servers fail to restart after installing an Installation Manager package 
even if you specify the ForceReboot option. This occurs when no users are 
logged on to the target server at the time of the installation.
  [From XE104W2K3R01][#108928]
  118. 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 is caused by a DLL that is 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: 0x00000000 
  Note: Setting this registry value to 0x2 disables RMS support. 
  [From XE104W2K3R01][#108993]
    119. When using more than one Management Console to specify printer drivers 
and selecting the "Allow only drivers in the list" compatibility list option in 
one console and the "Allow all drivers except those in the list" option in 
another console, all available printer drivers are autocreated rather than 
those specified in either console. This occurs because the two options are 
mutually exclusive and neither can be enforced over the other. 
  After installing this hotfix, the printer drivers are autocreated according 
to the compatibility list options you specify. 
  [From XE104W2K3R01][#109050]
  120. After applying Service Pack 1 for Windows Server 2003, the ICA 
Administrator toolbar fails to start up at logon. This occurs because the 
service pack requires the entire path of an executable to be launched at logon 
to be included in the registry. 
  This fix adds a script that determines the location of the toolbar executable 
and updates the registry accordingly. 

  [From XE104W2K3R01][#109462]
    121. After upgrading to Windows 2003 Service Pack 1, Internet Explorer 
becomes unresponsive unexpectedly. This occurs because of an incompatibility of 
Citrix code and the Data Execution Prevention feature included in Service Pack 
1.
  [From XE104W2K3R01][#109486]
  122. Servers may experience a KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e) blue 
screen when clients utilize 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 cause the exception. This occurs because of 
an invalid handle.
  [From XE104W2K3R01][#110106]
  123. While opening the properties for a published application in the 
Management Console, the following error message appears: "Error: one or more 
servers failed to complete startup sequence, ... error code :c0180003." This 
occurs if you remove servers from the farm using the console without running 
the chfarm utility or uninstalling MetaFrame. The IMA Service fails to 
completely remove the records pertaining to the removed servers from the 
persistent store.
  [From XE104W2K3R01][#110248]
  124. When logging on to a session using non-Smart card credentials and 
subsequently inserting a Smart card, the session may become unresponsive. This 
occurs because the Microsoft Smart card Resource manager, resident on the 
client device, blocks certain commands while a transaction is pending. If the 
server forwards commands while such transactions are pending, the commands are 
blocked on the client; this results 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 XE104W2K3R01][#110436]
  125. After installing Windows 2003 Service Pack 1, smart card pass-through 
authentication fails. The issue is caused by changes to winlogon introduced in 
Service Pack 1. 
  [From XE104W2K3010][#111392]
  126. Installing Service Pack 4 for MetaFrame XP 1.0 with Feature Release 3 
fails to uninstall hotfixes for MetaFrame XP 1.0 with Feature Release 3. This 
occurs because Service Pack 4 does not call the necessary custom actions to 
uninstall the hotfixes.
  [From XE104W2K3R01][#111614]
  127. Implementing a Smart card removal policy to lock a client device causes 
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 XE104W2K3R01][#111680]
  128. On occasion, when running Driver Verifier, servers become unresponsive.
  [From XE104W2K3R01][#111746]
  129. In sessions using the Linux Client with Spanish keyboard layouts, the 
Print Screen key does not work. This occurs because of an incorrect scan code 
in the Spanish keyboard layout file.

This fix corrects the issue. 
  [From XE104W2K3R01][#111762]
  130. Sessions using Smart cards may become unresponsive. This occurs because 
the client operating system is blocking certain commands during transactions. 
  [From XE104W2K3R01][#111828]
  131. When uninstalling Service Pack 4, the installer dialogs and logs fail to 
show hotfix information for MetaFrame XP 1.0 with Feature Release 3. This 
occurs because custom actions and transform changes are missing. 
  Note: Hotfix information cannot be logged if you have a large number of 
hotfixes installed for MetaFrame XP 1.0 with Feature Release 3. 

  [From XE104W2K3R01][#111891]
    132. Smart card applications run within an ICA session may exhibit 
different behavior than when run in an RDP session. This occurs, in part, 
because additional time was added to certain time-outs in an attempt to 
minimize network traffic resulting from polling Smart cards. Additionally, 
error codes are 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 XE104W2K3R01][#112461]
    133. When connecting to a Windows Server 2003, users who are part of the 
Allow log on through Terminal Services group policy but not of the Allow log on 
locally group policy cannot enumerate the applications in an application set. 
This occurs because the code does not check for the latter policy, which is new 
in Windows Server 2003.
  [From XE104W2K3R01][#112491]
  134. Mapped client drives may not have been accessible after reconnecting to 
a disconnected session. This occurs because the user policy information is not 
filled in properly after session reconnect.
  [From XE104W2K3R01][#112577]
  135. The termservice and IMA Services are pegging the CPU at 100% during 
client logoff. This occurs because of a logic error while enumerating processes.
  [From XE104W2K3008][#113617]
  136. When logging on to a published application, servers occasionally 
experience a fatal error. The issue is caused by a memory allocation error. 
  [From XE104W2K3R01][#113848]
  137. After applying Microsoft article Q121007 to disable 8.3 name creation on 
NTFS partitions, users cannot shadow using the shadow taskbar. Instead, the 
client help window for WFICA32.exe appears.
  [From XE104W2K3R01][#114684]
  138. The function "get_Month for the IMetaFrameTime interface" of the MFCOM 
SDK returns incorrect values. Instead of returning 1 for January, it returns 0. 
This occurs because the MFCOM service is doing time conversions incorrectly.
  [From XE104W2K3R01][#115306]
  139. After applying Service Pack 4 for MetaFrame XP, the wfshell.exe process 
may exit with an access violation during the enumeration of client printers. 
  [From XE104W2K3R01][#115774]
  140. While applying Service Pack 4 for MetaFrame XP, some unversioned 
binaries that are part of previously installed hotfixes may not be updated by 
the service pack.
  [From XE104W2K3R01][#115845]
  141. Client printing fails if the printer name contains a forward slash (/). 
This occurs when an incorrect printer name is sent to the client.
  [From XE104W2K3R01][#116214]
  142. After applying Service Pack 4 for MetaFrame XP 1.0, deploying 
Installation Manager packages may fail with the Event Log showing Event ID 1000 
- Gemini installer failed. 
  [From XE104W2K3R01][#117574]
  143. The Citrix Diagnostic Facility does not trace information from the Smart 
card support module. As a result, you cannot use the utility to trace Smart 
card support problems. 
  This fix modified the utility so you can use it to gather trace information 
from the Smart card support module. 

  [From XE104W2K3R01][#118558]
    144. If the the Language bar of IME 2002 or IME 2003 is running within an 
ICA session, the session remains active even after all seamless published 
applications are closed.
  [From XE104W2K3R01][#118583] 

  Installing and Uninstalling this hotfix rollup pack 
  Notes: 
    ? this hotfix rollup pack is packaged with Microsoft Windows Installer 3.0 
as a .msp file. For more information about deploying these, see Microsoft 
article 884016 or visit the Microsoft Web site and search on keyword msiexec. 
  ? this hotfix rollup pack may or may not prompt you to restart the server 
when the installation or uninstallation is complete. If you are using the 
Access Suite Console, you must restart the server after installing or 
uninstalling this hotfix to ensure that the hotfix is added to or removed from 
the console's hotfix inventory list. 

  To install this hotfix rollup pack: 
    1. Copy the hotfix package to an empty folder on the hard drive of the 
server you want to update.
  2. Close all applications.
  3. Run the executable.
  4. Shut down and restart the server.
  5. If you are using the Access Suite Console, restart the server to ensure 
the hotfix is added to the console's hotfix inventory list.

  To uninstall this hotfix rollup pack: 
    1. From the Start menu, select Setting > Control Panel.
  2. In Control Panel, double-click Add/Remove Programs.
  3. Highlight the hotfix you want to uninstall and click Remove.
  4. Follow the directions on-screen.
  5. If you are using the Access Suite Console, restart the server to ensure 
the hotfix is removed from the console's hotfix inventory list.

  Files Updated
            0000040a.kbd
    7,428
    01/18/2006
    03:27p
      adfp.dll
    393,216
    01/18/2006
    07:38p
      apsdk.dll
    86,016
    01/18/2006
    07:38p
      ccticket.dll
    135,168
    01/18/2006
    07:38p
      cdfdrv.sys
    17,024
    01/18/2006
    07:38p
      CDM.sys
    304,128
    01/18/2006
    07:38p
      cdmprov.dll
    192,512
    01/18/2006
    07:38p
      cdmsvc.exe
    139,264
    01/18/2006
    07:38p
      chgcdm.exe
    139,264
    01/18/2006
    07:38p
      citrix_ima_core.jar
    1,042,409
    01/16/2006
    02:15a
      clm.dll
    229,376
    01/18/2006
    07:38p
      clntsetup.exe
    192,512
    01/18/2006
    07:38p
      cltmgr.exe
    49,152
    01/18/2006
    07:38p
      CPatch.exe
    26,624
    12/20/2005
    05:51p
      cpmmon.dll
    86,016
    01/18/2006
    07:38p
      ctxadmin.dll
    88,064
    01/18/2006
    07:38p
      ctxadpcm.acm
    11,776
    01/18/2006
    07:38p
      ctxdwavo.exe
    21,504
    01/18/2006
    07:38p
      ctxgina.dll
    23,040
    01/18/2006
    07:38p
      ctxnotif.dll
    188,416
    01/18/2006
    07:38p
      ctxprnui.exe
    18,432
    01/18/2006
    07:38p
      ctxrpc.dll
    20,616
    01/18/2006
    07:47p
      cutildll.dll
    49,288
    01/18/2006
    07:47p
      DsCheck.exe
    47,616
    01/16/2006
    12:24a
      DsMaint.exe
    106,496
    01/18/2006
    07:37p
      enblrdrv.sys
    44,168
    01/18/2006
    07:47p
      enblrrecw.exe
    1,245,184
    01/18/2006
    07:38p
      encsvc.exe
    167,936
    01/18/2006
    07:38p
      exceldll.dll
    11,776
    01/18/2006
    04:00p
      excelinterface.dll
    4,096
    01/18/2006
    04:00p
      ibrowser.exe
    106,496
    01/18/2006
    07:38p
      icabar.exe
    90,112
    01/18/2006
    07:38p
      icactls.dll
    25,600
    01/18/2006
    07:38p
      icammdrv.dll
    25,600
    01/18/2006
    07:38p
      icareduc.sys
    12,680
    01/18/2006
    07:47p
      iexplore.exe
    36,864
    01/18/2006
    07:38p
      ImaAccess.dll
    118,784
    01/18/2006
    07:37p
      ImaAppSal.dll
    135,168
    01/18/2006
    07:37p
      ImaAppSs.dll
    303,240
    01/18/2006
    07:47p
      ImaCompat.dll
    6,656
    01/18/2006
    07:37p
      ImaDB2.dll
    118,784
    01/18/2006
    07:37p
      ImaDirect.dll
    69,120
    01/18/2006
    07:37p
      ImaDomain.dll
    155,784
    01/18/2006
    07:47p
      ImaFileSal.dll
    27,648
    01/18/2006
    07:37p
      ImaFileSs.dll
    98,440
    01/18/2006
    07:47p
      ImaLhc.dll
    40,960
    01/18/2006
    07:37p
      ImaMfRpc_Client.dll
    29,696
    01/18/2006
    07:37p
      ImaMsgs.dll
    34,816
    01/18/2006
    07:37p
      ImaNDS.dll
    118,920
    01/18/2006
    07:47p
      ImaOracle.dll
    110,592
    01/18/2006
    07:38p
      ImaOracle7.dll
    110,592
    01/18/2006
    07:38p
      ImaPerf.dll
    34,304
    01/18/2006
    07:38p
      ImaPolicySal.dll
    72,192
    01/18/2006
    07:38p
      ImaPolicySs.dll
    127,112
    01/18/2006
    07:47p
      ImaPort.exe
    22,016
    01/18/2006
    07:38p
      imareduc.dll
    12,936
    01/18/2006
    07:47p
      ImaSql.dll
    163,840
    01/18/2006
    07:38p
      ImaSrvSal.dll
    131,072
    01/18/2006
    07:38p
      ImaSrvSs.dll
    270,472
    01/18/2006
    07:47p
      ImaSs.dll
    35,976
    01/18/2006
    07:47p
      ImaSystem.dll
    233,472
    01/18/2006
    07:38p
      ImaUserSs.dll
    176,264
    01/18/2006
    07:47p
      ImsSs.dll
    643,208
    01/18/2006
    07:47p
      IMUtil.dll
    278,528
    01/18/2006
    07:37p
      LMS20Rules.dll
    34,304
    01/18/2006
    07:38p
      LmsSal.dll
    55,296
    01/18/2006
    07:38p
      LmsSS.dll
    204,936
    01/18/2006
    07:47p
      mfapHook.dll
    122,880
    01/18/2006
    07:38p
      MfAppSal.dll
    135,168
    01/18/2006
    07:38p
      MfAppSs.dll
    450,696
    01/18/2006
    07:47p
      MfBrowserSal.dll
    17,408
    01/18/2006
    07:38p
      MfBrowserSs.dll
    131,208
    01/18/2006
    07:47p
      mfcfg.exe
    389,120
    01/18/2006
    07:38p
      mfcom.exe
    221,184
    01/18/2006
    07:38p
      mfcomsrv.dll
    454,656
    01/18/2006
    04:00p
      MfContentSal.dll
    25,600
    01/18/2006
    07:38p
      MfContentSs.dll
    86,152
    01/18/2006
    07:47p
      MFError.dll
    15,872
    01/18/2006
    07:38p
      MFEvent.dll
    12,288
    01/18/2006
    07:38p
      MfPnSal.dll
    36,864
    01/18/2006
    07:38p
      MfPnSs.dll
    147,592
    01/18/2006
    07:47p
      MfPrintSal.dll
    69,632
    01/18/2006
    07:38p
      MfPrintSs.dll
    401,544
    01/18/2006
    07:47p
      mfreg.exe
    217,088
    01/18/2006
    07:38p
      mfrpcss.dll
    209,032
    01/18/2006
    07:47p
      MFRules.dll
    48,128
    01/18/2006
    07:38p
      MfSrvSal.dll
    172,032
    01/18/2006
    07:38p
      MfSrvSs.dll
    442,504
    01/18/2006
    07:47p
      MFStatus.dll
    13,824
    01/18/2006
    07:38p
      MFXPPerf.dll
    45,056
    01/18/2006
    07:38p
      msi30ca.dll
    29,696
    12/20/2005
    06:38p
      Native.dll
    52,507
    01/18/2006
    07:38p
      Packager2.exe
    2,785,280
    01/18/2006
    07:38p
      pnsvc.exe
    86,016
    01/18/2006
    07:39p
      printcfg.exe
    184,320
    01/18/2006
    07:39p
      PrinterMgr.jar
    319,002
    01/16/2006
    02:15a
      qfarm.exe
    57,344
    01/18/2006
    07:39p
      ResourceManager.jar
    1,419,810
    10/06/2005
    07:08a
      ResourceManager_ja.jar
    1,424,413
    10/06/2005
    07:10a
      RMMonitorSS.dll
    1,167,496
    01/18/2006
    07:47p
      scardhook.dll
    81,920
    01/18/2006
    07:39p
      seamls20.dll
    65,536
    01/18/2006
    07:39p
      sehook20.dll
    16,384
    01/18/2006
    07:43p
      ServerMgrNew.jar
    274,144
    01/16/2006
    02:15a
      SpeedScreenApi.dll
    10,752
    01/18/2006
    07:38p
      SpeedScreenFilter.dll
    962,560
    01/18/2006
    07:38p
      tzhook.dll
    11,776
    01/18/2006
    07:39p
      vclipbd.dll
    27,648
    01/18/2006
    07:39p
      vdtw30.dll
    264,456
    01/18/2006
    07:47p
      wdica.sys
    187,016
    01/18/2006
    07:47p
      wfapi.dll
    22,016
    01/18/2006
    07:39p
      wfshell.exe
    167,936
    01/18/2006
    07:39p
      wpnbr.dll
    106,496
    01/18/2006
    07:39p
      wshadow.exe
    114,688
    01/18/2006
    07:39p
      wsxica.dll
    258,320
    01/18/2006
    07:47p
      zlc_api.dll
    90,112
    01/18/2006
    07:39p
  Copyright © 2006 Citrix Systems, Inc. All rights reserved.





Jim Kenzig 
CEO The Kenzig Group
http://www.kenzig.com
Sponsorships Available!
Blog: http://www.techblink.com
Terminal Services Downloads: http://www.thinhelp.com
Windows Vista: http://www.VistaPop.com
Virtualization: http://www.virtualize-it.com
Games: http://www.stressedpuppy.com

Other related posts:

  • » [THIN] KB: CTX107783 - Hotfix Rollup Pack XE104W2K3R02 - For Citrix MetaFrame XP 1.0 for Windows Server 2003