We are currently deploying Windows 7 64bit PCs within our organization. Some of the computers need to have their print spoolers restarted in the mornings or else they won't print.
After the spooler has been restarted they seem to print fine.
We deploy printers via Group Policy from Windows 2003 and I administer the print management with Windows 7 so that I can install the Windows 7 64-bit drivers.
We have a variety of printers including Ricoh and HP. None of the printers will work on my PC first thing in the morning. Upon checking the properties of the printers, there is nothing listed in the ports tab when this happens. When I stop and restart the print spooler suddenly everything appears in the ports tab and I am able to print just fine.
I am using mostly the universal PCL 64-bit drivers for the Ricohs and the HPs alike.
I know there has got to be some sort of error that is happening and hanging the print spooler upon start-up, but I'm not sure what it is. I tried setting the print spooler to restart service automatically on subsequent failures, but then that just hung everything up and I had to restart the spooler on the server and then on the PC before I could print again.
There is nothing in the event logs to tell what's going on.
I also have PDF Creator installed if that makes any difference, although it is not installed on any of the other computers and I still had the print problem at least once on one of them.
Restarting the print spooler on the server makes little difference except that I have noticed if I try to connect to the server print management console too many times in a row nothing will show up in the print management console at all unless I restart the 2003 server print spooler as well as my Windows 7 print spooler.
I think that has to do with the fact that Windows client computers are only allowed so many connections to 2003 before it won't allow anymore which is done by design by Microsoft and dumb in my opinion.
If the printers are directly connected to the users via Standard TCP/IP then there is never a problem.
The problem only occurs when the printers are connected via the group policy deployment of the server.
Any ideas? We only have a few Windows 7 PCs right now, but if this is going to continue to be a problem we'll have to cut out deploying printers with group policy. Someone once mentioned disabling bidirectional printer support because a resource might be in use that requires admin or system privileges in order to print, however, this was only a solution to a problem where documents wouldn't print until the print spooler on the server was restarted and then they would print.
Thanks for any advice!
Software/Hardware used: Windows 7 64bit OS on Client, Windows 2003 R2 on Server, HP and Ricoh network printers