Intermittent, Unreliable Scripted Printer connections in Windows 7 with 2003 Domain.
Posted on 2010-09-08
I have been struggling with using the logon script to install printers on our new W7 machines for weeks now.
I have found Printui.exe to be the mose reliable, but it is only 85% reliable at best.
This is what is in my script:
echo Using PrintUI to configure printers
printui.exe /in /q /n\\sp2k301\complab_1$
printui.exe /in /q /n\\sp2k301\complab_2$
printui.exe /in /q /n\\sp2k301\library_1$
printui.exe /in /q /n"\\sp2k301\School_4050-W7"
printui.exe /in /q /n"\\sp2k301\Church Copier"
printui.exe /in /q /n"\\sp2k301\School-6030"
printui.exe /in /q /n"\\sp2k301\Color_1$"
printui.exe /in /q /n"\\sp2k301\R2D2"
printui.exe /in /q /n"\\sp2k301\School1$"
printui.exe /y /q /n"\\sp2k301\library_1$"
most of the time this works, but often it doesn't.
It either hangs at "trying to locate driver" or "Cannot connect to Printer"
I have made sure the drivers at the print server are the latest and compatible with Windows 7. In fact, we one driver for three different printers (an HP 4100 Series) and one of the three printers (all using the same driver) fails most of the time. More often than not, it is the Complab_1$ printer, but not always.
If I login, and open a command prompt and run the logon script repeatedly, it will run several times and then it may break. When it breaks, all bets are off until I restart the spooler, which I can only do if I am logged in as admin.
I am at my wits end. I am looking for help. The only thing I haven't tried, before I completely exhaust my efforts is to change the script from a .bat to a .cmd Would this really make any difference?
I'm sure you'll have lots of questions, so bring them on.
Also, I am not interested in deploying through GPO at this time.