Printer Spool stops : The problem? Me!!
You'd think after years of working with printers and deploying them on networks using login scripts and the like that I'd have learned a few things about what not to do, or rather what not to forget....
... apparently not.
Anyway, for the satisfaction of those who like to know others are indeed all too human and to avoid someone else making the mistake or just feeling a numpty in company here's one to watch out for.
- Printers were seeing more and more problems with documents failing to print, printers disappearing and various other rather bizarre and weird goings on.
- Amongst other things I tracked down some of the issues to what I thought were VB6 runtimes and re-installed them all which seemed to cure some part of the issue
- Further to that, rewrote the login scripts for users and these seemed to successfully deploy the printers although there were some small errors they would appear in the relevant place fine unless the spooler had crashed earlier in the day, in which case rebooting was required.
- Issues with nvidia machines trying to add a run command to the users registry were resolved with a fix that sorted one issue with clashes but again still not quite there.
Clarity, Silliness and the Solution
- It's all well and good adding printers via a login script for users but unless you've actually deployed the printers as a startup, at some point the drivers will not have been installed properly.
- Quickly writes up a startup script to do just that and guess what... it works! ;)
Ahah! Yes, yes... idiot alert... Good grief, what a goof ball! :yield: :rain: