HP Inkjet (& Lasers?) Solution that's worked
After sooooo many threads where folks have complained about driver issues, spooler shutdowns, stalled queues, etc... I've been slowly working through every variation of possible setup at one of my schools.
In the end it seems the simplest and most workable solution was to setup VMWare on a lesser used server, install a vanilla Win Server 2003 R2, join it the network as a client NOT as an Active Directory controller and then install all those printers using the driver only installs.
After that, deploy as normal using startup and login scripts (vbs)
Startup script installs one of each printer type to the machine which helps remove any of the "not quite setup properly" driver install issues that come with login scripts.
The login scripts handle all the printers required for that user.
So far, touch wood, the only problem I've seen is that I need to put more memory in the host machine as it's complaining about using insufficient Virtual memory based on the 762Mb or virtual RAM I assigned it... I should be able to up it to 2Gb+ once I've got the extra sticks installed.
I'm aware that the use of a vanilla installation of Win2k3r2 (without the dross) probably helps enormously, but the lack of other services, particularly AD, DNS, etc... is something that's been hinted at being a big contributor, so combined these approaches seem like the winning solution.
Oh and to top if off, I have a script that runs every 40 minutes, checks for stalled jobs, if it finds anything older than 40 minutes it kills the print spooler service, kicks the stalled job and then restarts the spooler again...
Hope this proves useful and input definitely welcome...