asked on

Windows 7 Printer Installation Script

Currently running the following script to add network printers shared on a Windows 2003 DC to Windows 7 Pro x64 workstations:

Set objNetwork = CreateObject("WScript.Network")

objNetwork.AddWindowsPrinterConnection "\\server\printer1"
objNetwork.AddWindowsPrinterConnection "\\server\printer2"
objNetwork.AddWindowsPrinterConnection "\\server\printer3"

There is a bug where the script causes the screen to go black on the Win7 workstations when running, sometimes. It eventually shows the desktop and the printers have installed, but it can take 2-10 minutes. I know there is code to say "if printer exists, don't try and add it again". That's what I think I need to avoid this issue each time the workstations login a simple if-then statement for the printer installation code above. If I remove the script from the GPO the black screens stop appearing.

TimAllan

It sounds like it's trying to find the path to your print server, which it is, but it's taking its time.
Just as a test, try using the full path to the print server

eg.
\\server.mydomain.com\printer1

instead of using the IP address or the just the server name

ASKER CERTIFIED SOLUTION

spinzr0

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

sc456a

ASKER

Tim: It's not a path or DNS issue, the workstations can pull it up immediately if you type that into Explorer. It's probably a driver issue related to x64 being on the workstations and x64 printer drivers being wonky on some of the printers, but it will install after a long delay.

spinzr0: I have no idea what that script does - some I'm askeered to try it. :) Can you break it down for me?

spinzr0

Yes. There is a security warning set off witha printer where the driver is being downloaded from the printer server. This bypasses that security warning.

sc456a

ASKER

You were right about the warnings being the cause, although I didn't try your script - it was faster to just run the VBS manually on each machine. I'll be sure to test your script in future installations.