Users experience 60 to 90 seconds delay when running published applications. This might be reported as a session freeze, hang, or delay. During the delays, sessions and the applications running inside the affected sessions are unresponsive to keyboard and mouse input.
Citrix Presentation Server/XenApp 4.0, 4.5, and 5.0 (share similar general printing architecture).
ICA Client (XenApp Plug-in) 9.x and later (because 9.x is required to use the affected version of the UPD).
Complete the following steps to fix the issue:
Examine the user's printers inside the affected ICA session.
You can use CDF Control or the Access Suite or Access Management Consoles to collect a CDF trace.
CTX104578 - How to use Citrix Diagnostic Facility and the Access Suite Console to Trace Issues
There are a variety of networking, hardware, and performance, related factors which can cause sluggishness, delays, or freezes. In this instance the focus is on orphaned printers as the cause - orphaned printers and the specific conditions causing the problem are further defined.
5 Simultaneous Conditions are Required for this problem to Occur
There must be an orphaned printer present in the user's session - an orphaned printer is a printer that is left behind from a user that previously logged on to a session with the same session ID as the current user and not deleted. Orphaned printers are a problem in and of themselves. By design, client printers must be deleted when users log off their sessions. Additionally, if a problem occurs and the printer cannot be deleted at log off, the Citrix Print Manager service has a clean-up routine which deletes any client printers which do not have sessions associated with them. Orphaned printers are not a common occurrence in a healthy environment.
The orphaned printer must be using the Citrix Universal Print Driver (UPD) for problem occurrence. If the printer is not using the UPD, the query to get device capabilities for the printer is answered on the server without sending a query to the client.
The client machine must not have the orphaned printer installed - the delay occurs because the client does not have the information for the printer (because it was not installed) - it attempts to map the network printer that the orphan represents.
The orphaned network printer must be accessible from the client. If the printer is not accessible, the client fails faster, meaning the session does not have a lengthy delay or hang.
A software component installed on the server with the orphaned printer must request the device capabilities of an orphaned printer. Requesting device capabilities is a common operation performed when Windows applications want to determine the capabilities of a printer device driver, for example, EdgeSight using Windows Management Instrumentation (WMI) to query for printer information.