Installation guide

46 Feature Release 1 and Service Pack 3 Installation Guide
The Service Control Manager sends the SERVICE_CONTROL_SHUTDOWN
event synchronously to all services one at a time when a system shutdown begins.
A service receives the event only when all services that received the event ahead
of it have finished processing the event. If the previous service does not process
the event, the following services never receive the event. The system can shut
down before a service receives the event, which means a service cannot execute
code in its SERVICE_CONTROL_SHUTDOWN event handler. With this hotfix,
the ICA Browser service and the Client Network service have been changed to
use the CTRL_SHUTDOWN_EVENT event (which is an asynchronous handler)
instead of the SERVICE_CONTROL_SHUTDOWN event. This allows other
services to execute their SERVICE_CONTROL_SHUTDOWN event handler.
This change does not guarantee that the %SystemRoot%\Jet*.tmp files will be
deleted during reboot. Even on a base Windows NT Terminal Server installation,
it is possible that this problem could still occur even if MetaFrame is not installed
because other installed services could have the same issue that the MetaFrame
services had prior to this hotfix.
To delete the old Jet*.tmp files, after installing the Service Pack and rebooting the
server, do the following:
At a command prompt, type DEL %SYSTEMROOT%\JET*.TMP.
Some files will display the message “The process cannot access the file because it
is being used by another process.” This message can be ignored; these files are
currently in use and will be deleted when the system is rebooted.
Hotfix Mx180008
1. The Citrix Server Administration utility did not properly display more than ten
add-on licenses.
2. In Citrix Server Administration, disconnected user information was not
displayed unless the information was manually refreshed.
3. Updated Published Application Manager help files.
Hotfix Mx180009
1. DOS client printers print garbage if they are taken offline and placed back
online while they are printing.
2. Communications applications such as HyperTerminal would hang when used
over a client COM port.
3. Client drive mapping could cause a blue screen.
4. The client COM port was slow when using the TCP/IP protocol stack.
5. The 16-bit client failed to maintain the status of the COM port and failed to
detect modem status.