Two posts ago, I wrote about the printer issues at work. At the end, I mentioned that the print role had been moved to a dedicated server, a move I agree with. What is puzzling and perturbing to me is that EXACTLY the SAME drivers were used on the new print server. With the new client desktop image, the clients are able to connect fine, but now anyone with Windows Vista installed (read: most of IT) now has their client print spooler crash on them when they try to connect to some printers. We’re being told to ‘restart your spooler service’. It works the second time around after restarting the print spooler service on the Vista client. Unfortunately however, the HPcdMC32.dll file is not going to be replaced right now. Since it’s only IT that’s affected, the decision has been made to leave printing alone for a while. Could be interesting if it gets forgotten and next year it’s not updated before the organization moves to Vista.
My main concern is that, just like last time, this driver is going to mess up the print spooler service on the server, like the previous incident. We stand a very good chance of losing print services again if the dll is not replaced. The whole operation to fix it would take less than 10 minutes, including time to download the driver from HP.
In other news, the Microsoft Support site has been updated with a new look. Quite nice if you ask me.
0 Responses
Stay in touch with the conversation, subscribe to the RSS feed for comments on this post.