Search

Hotfix XE104R01W2K010 - For MetaFrame XP 1.0 for Windows 2000 Server

Friday, 09 December 2005 by Michel Roth

Issue(s) Resolved in this Hotfix
1. Disconnected sessions were displayed as active or not displayed at all in the Management Console.

2. When an application set refresh request was done from a client using smart card authentication, the refresh request may have been routed to a server where logons were disabled. As a result, the refresh request failed and the following message appeared: "Remote logins are currently disabled." The issue occurred because the mechanism used to route the refresh request did not consider the state of the destination server before routing the request there.

3. The Management Console did not properly display the state of disconnected sessions. The issue occurred because winstation queries did not update the IMA Service with reconnect/disconnect status changes.

4. After applying HRP01 for MetaFrame XP 1.0 with Feature Release 3/Service Pack 4, sessions launched by way of a batch file or script failed to display under the individual servers nodes in the console. The sessions did display in the Citrix Server Administration tool and when using command lines tools such as quser or qwinsta. The issue occurred because the IMA Service was not being updated with winstation reconnect/disconnect status change information.

5. After installing Service Pack 4 for MetaFrame XP 1.0 with Feature Release 3, shadowed sessions and Java clients were disconnected when the KeepAlive time-out was reached. The issue occurred because the addition of the icm_ping request to implement KeepAlives failed because shadow sessions and Java clients did not respond to the ping request.

6. On occasion, while users were in the process of logging on, their sessions became unresponsive, displaying a blue screen background only. While existing sessions were not affected, no additional sessions could be launched until the server was restarted. The issue occurred when there was a transient connection failure during the logon process that resulted in a call time-out.

7. On occasion, the IMA Service was allocating excessive amounts of memory, causing the service to become unresponsive at random. XML browsing failed intermittently during such times.

This fix corrects the issue by optimizing the IMA Service memory allocations.

8. Users could not create folders on mapped drives using the xcopy or mkdir commands from the command line. The issue occurred because the original file name rather than the canonicalized file name was passed to the client drive mapping policy check routine.

9. IBM Blade servers were experiencing random fatal errors. The issue occurred because a mutex object was being initialized by multiple threads when it should have been initialized only once.

10. On occasion, servers experienced a fatal error, causing an unexpected blue screen. The issue occurred during times of high activity resulting from printing to mapped ports and/or file copying to mapped client drives because the logical port was being destroyed before the data transfers were complete.

11. The amount of Microsoft license information in the data store grew to be very large. Each time a non-Windows client logged on to a computer running Presentation Server, the Microsoft license information obtained by Presentation Server was replicated to the data store. If Presentation Server obtained the same license information.

12. Servers experienced a blue screen with error code 0x00000002 when Driver Verifier was enabled with deadlock detection. The issue occurred because the winstation driver was not releasing resources before unloading.

13. Servers experienced a fatal error, displaying a blue screen when using CDF Tracing using MF_Driver_Cdm. The issue occurred when a CDF trace statement tried to print an improperly formatted buffer.

14. On occasion, servers restarted unexpectedly. The issue was caused by the wdica.sys file and occurred because two resource locks were not released when the driver was unloaded.

15. When using the MFCOM SDK to enumerate sessions, session IDs greater than 9 could not be enumerated. The issue occurred because the IMA Service was using a hexadecimal rather than a decimal session ID to search for sessions.

16. Entries added to the print driver auto-replication list were deleted after 24 hours. The issue occurred because regular replication jobs are deleted if they are not completed after 24 hours; however, auto-replication jobs should not be deleted. This fix corrects the issue in that incomplete auto-replication jobs are no longer deleted.

17. Printing to COM and LPT ports was slow. The issue occurred because the client redirector was not being released before waiting for the client workstation to respond.
This fix corrects the issue, resulting in improved printer performance.

18. Occasionally, servers experienced a fatal error, displaying a blue screen on CDM.SYS. The issue occurred when an applications was accessing drive A in a session using "A:" rather than "A:\" or if it was the first process to access a client drive in a session. The issue was caused by a legacy optimization routine.
This fix corrects the issue by removing the legacy optimization routine.

Download XE104R01W2K010 here.