To delete stuck print jobs from the printer queue manually in WinXP, W2K, WinNT (?):
To troubleshoot stuff other than stuck print jobs:
An Excellent overview of printing in a terminal server environment:
http://www.brianmadden.com/content/content.asp?ID=62
This KB article lists the various registry keys involved in printing:
http://support.microsoft.com/kb/q102966/
I have found that in HKLM\System\CurrentControlSet\Control\Print\Printers there were a dozens of printers listed. Deleting the suspicious ones from remote RDP clients has helped fix a CPU hogging spooler service (spoolsv.exe). Export the registry keys first, just in case. My case happens to be occuring on a system running BBL over terminal server.
Systernals.com' tool "regDelNull" might be needed to remove some of the entries that would not delete manually -- shame on you Mr. Zebra Printer Driver.
e.g. RegDelNull HKLM\System\CurrentControlSet\Control\Print\Printers -s
I ended up blogging about this here:
Spoolsv.exe using lots of CPU on a Terminal Server
I have not tested this tool yet, but I will someday: "Stalled Printer Repair"
http://www.pcworld.com/downloads/file/fid,84019-order,3/description.html
http://www.fantasticfreeware.com/applications/stalled-printer-repair/
tags: printer, spooler, print, winbpl, bbl, winpos, terminal server, spool, printing, problem, terminal, null, delete, registry, rdp