B
Bruce Lautenschlager
I notice that in in Windows XP, Microsoft wisely seems to have configured
the print spooler service to restart if it crashes.
Unfortunately, I've still got about 1000 Windows 2000 PCs on my domain, and
it seems like when I update a (or more correctly, install a new) driver on
my Windows 2003 Print Server, it likes to update EVERY network printer on
EVERY PC, even if the models and drivers aren't even the same (thank you
very little, HP).
When that happens, about 10% of the PCs crash their spooler service, until
they think they've updated ALL of their printer drivers (even though, again,
their 9050, 4600, and 4000 drivers didn't change a wink just because some
a--hole started purchasing P4015's and now we have yet another crapass HP
driver on our server).
Anyone know of any way to change the spooler service to recover
automatically via GPO or registry hack? I know it's a band-aid (I'm thinking
of reverting to only using HP 4 drivers...seriously) - but it would really
help.
Thanks,
Bruce
the print spooler service to restart if it crashes.
Unfortunately, I've still got about 1000 Windows 2000 PCs on my domain, and
it seems like when I update a (or more correctly, install a new) driver on
my Windows 2003 Print Server, it likes to update EVERY network printer on
EVERY PC, even if the models and drivers aren't even the same (thank you
very little, HP).
When that happens, about 10% of the PCs crash their spooler service, until
they think they've updated ALL of their printer drivers (even though, again,
their 9050, 4600, and 4000 drivers didn't change a wink just because some
a--hole started purchasing P4015's and now we have yet another crapass HP
driver on our server).
Anyone know of any way to change the spooler service to recover
automatically via GPO or registry hack? I know it's a band-aid (I'm thinking
of reverting to only using HP 4 drivers...seriously) - but it would really
help.
Thanks,
Bruce