{"id":1616,"date":"2007-11-20T05:29:00","date_gmt":"2007-11-20T05:29:00","guid":{"rendered":"http:\/\/neu.koetzingit.de\/citrix-stressprinters-verstehen-und-nutzen\/"},"modified":"2026-06-02T13:33:34","modified_gmt":"2026-06-02T13:33:34","slug":"citrix-stressprinters-verstehen-und-nutzen","status":"publish","type":"post","link":"https:\/\/www.koetzingit.de\/en\/citrix-stressprinters-verstehen-und-nutzen\/","title":{"rendered":"Understanding and Using Citrix StressPrinters"},"content":{"rendered":"

V<\/span>Many Citrix or terminal server farms have problems with printer drivers, and sometimes the administrator isn't even aware of it. Printer drivers that aren't designed for multi-user environments can have a negative impact on various aspects. Often, these \u201ebuggy\u201c drivers cause a slower login or a sudden spike in CPU usage<\/strong>. In the worst-case scenario, printer drivers can prevent the server from logging in altogether, force the print service to shut down, or cause a \u201eBlue Screen of Death\u201c (BSOD, which is quite rare in Windows 2003 and later versions).<\/p>\n

<\/p>\n

Until now, troubleshooting has often been complex and required in-depth knowledge of printer drivers. Once the driver was finally identified (often by analyzing a crash dump file) and the information was forwarded to the manufacturer, this often ended with the manufacturer stating that the problem could not be reproduced in their environment.<\/p>\n

To identify these \u201ebad\u201c printer drivers\u2014and, even better, to simulate a terminal server scenario\u2014Citrix released a utility called \u201eAddPrinter.\u201c Later, Citrix developers created a Created a GUI for AddPrinter and aptly named it \u201eStressPrinters\u201c<\/strong> equipped with. With StressPrinters, administrators can easily \u201estress\u201c printers, subject them to heavy loads, and thereby simulate a terminal server environment. This is very helpful for administrators, and at the same time, manufacturers can precisely reproduce an existing problem.<\/p>\n

Citrix has already distributed the utility to all major printer manufacturers in the hope that future printer drivers will work seamlessly in terminal server environments. In the meantime, administrators of multi-user farms (Citrix, terminal servers, etc.) are advised to test all their printer drivers with StressPrinters.<\/p>\n

\u00a0<\/p>\n

Understanding Citrix StressPrinters<\/span><\/h3>\n

StressPrinters automatically creates and deletes print objects that were previously defined in the StressPrinters GUI. This creation and deletion takes place within a very short time, thereby Simulated peak times for check-in and check-out<\/strong>. The administrator determines the intensity with which the test should simulate the behavior. Testing printer drivers can be a very high CPU load<\/strong> and should therefore not be run on production servers. StressPrinters does not depend on any specific Citrix component and can therefore be used in any multi-user environment. StressPrinters even runs on a Windows XP workstation. This allows printer manufacturers and their driver developers to replicate the exact same situation and find a solution for it.<\/p>\n

\u00a0<\/p>\n

Use StressPrinters<\/span><\/h3>\n

StressPrinters is very easy to use. You can download StressPrinters from CTX109374. Registration is required, but the download is free. The ZIP file should be extracted to a folder on a non-production server where all the printer drivers used are also installed.<\/p>\n

\u00a0<\/p>\n

The Simple Printer Stress Test<\/span><\/h3>\n

After launching StressPrinters, the following window appears:<\/p>\n

\"Blogs<\/p>\n

Select all printers to be tested and specify the number of times the printer should be added and removed (4\u20135 is recommended). Additional parameters can be set optionally, but are not required. A description of all options can be found in the article mentioned above. Click \u201eRun,\u201c and StressPrinters will start testing the printer drivers. During the test, an \u201eOutput\u201c window will appear, displaying the test status.\u00a0<\/p>\n

\"Blogs<\/p>\n

In the best-case scenario, the output window will simply display \u201eSuccessful\u2026 done with 0 errors.\u201c A few \u201eWarnings\u201c may appear, indicating that the printer driver may need more time to create or delete the printer.\u00a0<\/p>\n

However, if the printer service \u201efreezes\u201c or even crashes completely during the test, this is due to faulty printer drivers. Under no circumstances should these drivers be used in a production environment. As a general rule, it is recommended to test every printer driver with StessPrinters BEFORE deploying it in a production environment. This applies in particular to drivers on print servers accessed by a terminal server or Citrix server.<\/p>\n

\u00a0<\/p>\n

The Advanced Printer Stress Test <\/span><\/h3>\n

There are reasons to perform an extended printer driver stress test. Drivers may pass the test but take an unusually long time or place an excessive load on the CPU. These parameters should be monitored during the test in order to further optimize the login and logout processes.<\/p>\n

\u00a0<\/p>\n

Example: StressPrinters Test with Native and Non-Native Drivers<\/strong>
The following image shows the results from StressPrinters using a native and a non-native printer driver. The HP driver is just an example here, but this could apply to any manufacturer.<\/p>\n

Printer driver test using the following StressPrinters settings:
Number of events for creation\/deletion: 1
Maximum wait time: 0 ms
Test Retake: 0
Detailed mode: active<\/p>\n

\"Blogs<\/p>\n

The \u201ewarnings\u201c aren't that important, and both drivers are generally suitable for a TS environment. What stands out, however, is the time required for the test. The native driver took 9 seconds, while the non-native driver took 54 seconds for the same test!
Here, the stress test should be monitored more closely using Microsoft Performance Monitor; monitor the \u201espoolsv.exe\u201c process.<\/p>\n

HP LaserJet 4100 Series PCL \u2013 Native Microsoft Printer Driver<\/strong>
Time to create\/delete a printer: 9 seconds with max. ~181% CPU usage on an Intel Core Duo
Login: 6 seconds \/ ~181 TP3T CPU, Logout: 3 seconds \/ ~111 TP3T CPU, max. context switches: 1,000<\/p>\n

\"Blogs<\/p>\n

\u00a0<\/p>\n

HP LaserJet 4250 PCL6 Non-Native HP Printer Driver (61.63.461.42)<\/strong>
Time to create\/delete printer: 54 seconds with ~65.1% CPU usage on an Intel Core Duo
Login: 6 seconds \/ ~181 TP3T CPU, Logout: 48 seconds \/ ~651 TP3T CPU, max. context switches 10,000<\/p>\n

\"Blogs<\/p>\n

\u00a0<\/p>\n

The figures above clearly show that the non-native driver uses significantly more server resources than the native driver. This high resource usage has a dramatic impact on the logon and logoff processes. Users often have between 5 and 15 printers set up. If all of these printers require a lot of resources, the logon and logoff processes can take a very long time.<\/p>\n

\u00a0<\/p>\n

Summary<\/span><\/h3>\n

Citrix StressPrinters should be used to test EVERY printer driver before it is installed on production servers (Citrix, terminal servers, print servers). During the stress test, be sure to evaluate CPU load and runtime, and look for a more suitable driver if necessary. Using StressPrinters helps minimize certain login and logout issues caused by poor-quality printer drivers. Many administrators are unaware that printer drivers can have this impact.<\/p>\n

\u00a0<\/p>\n

References<\/strong><\/p>\n