[STAW]

I'm in a corporate environment with hundreds of printers spread between several print servers. About twice a day, some random printer on the network will lock up and stop printing, and seemingly the only way to get it up an running again is to connect to the print server, restart the print spooler, then delete the job.

This method of solving the problem has recently come under fire.

The main thing I'm wondering, here, is whether restarting the spooler kills every job currently going through that print server (or, at least, every job under "printing" status), or if it basically lets the pick right up where they left off. Haven't been able to find any info on this in some quick research, just a whole bunch more people who use this same workaround for similar problems.

[STAW]

Bump. No ideas?

[kniht]

See if anything here is of any help.

[STAW]

Thanks for the link, but nothing there is really what I'm looking for. I'm more trying to look at this from a cause and effect standpoint - does resetting the spooler service on a print server kill all of the active jobs on that server? Can it corrupt print drivers or the service itself?

[Squashman]

Using Citrix?
http://support.microsoft.com/kb/888196

[STAW]

Nope, no Citrix.