VBScript (VBS) - Printer Script Not Working

Hey folks, cool forum. I cant write my question beacause I cant stop reading

I need to solve a printing script problem real bad. I didnt set it up and that person is unavailable. Windows Server 2003 domain, the DC is the file server and print server. Instead of installing printers on users XP machines, it is handled by the server with a 'simple' vbs script. Instead of users seeing just the printer(s) right there in their office, they see all the printers in the building. Id like to change that, but thats not the primary problem. Theyre still getting used to it, sometimes they print to printers 3 floors away. They'll get it.

The problem is printing gets fouled up. When they see no printers at all, the local print spooling service has stopped. I think it was being caused by a particular printer. Even after restarting it, they have to log off/on again or reboot. This printer was giving errors all around the place, something in the driver. I added a

objNetwork.RemoveWindowsPrinterConnection


line to the script, uninstallled it from the server, I thought that worked but it still comes up - sometimes. Here is the script:

On Error Resume Next
Err.Clear

Set objNetwork = CreateObject("WScript.Network")


objNetwork.AddWindowsPrinterConnection "\\server1\ACME-2nd"
objNetwork.AddWindowsPrinterConnection "\\server1\ACME-1st"
objNetwork.AddWindowsPrinterConnection "\\server1\ACME-Marketing"
objNetwork.AddWindowsPrinterConnection "\\server1\StoreroomBlack"
objNetwork.AddWindowsPrinterConnection "\\server1\StoreroomColor"
objNetwork.AddWindowsPrinterConnection "\\server1\ACME-LJ3500"
objNetwork.AddWindowsPrinterConnection "\\server1\ACME-2ndFl-4250"
objNetwork.AddWindowsPrinterConnection "\\server1\center6122"

Some other symptoms: The LaserJet 3800 was in the storeroom, which was moved to the Opportunity office is still shared as 'storeroom' but it is correct in users printers folder as 'opportunity'. The LJ3500 is really a 3005, it is shared on the server as a 3500 and is in the users printers folder as a 3005. On the Terminal Server, we use ThinPrint. In TS sessions, the printers folder show every "local" printer from every session in the past, 53 of them at the moment.

I hope Ive included all the pertinent info. Thanks for taking a look.

Hi whatsys,

Your issue doesn't sound as though it's script related. I don't think the problem is in your script.

It sounds to me like you have a domain logon script that populates a list of printers. When of these is temporarily unavailable, or some kind of error occurs, the local print spooler service is disabled. After restarting the service, your users need to log off and then on again because that's what starts the printer script again.

There is no way to avoid this since you are using a domain logon script. I'd recommend setting up the domain properly and eliminating a need for the script to begin with. You might even consider sharing the printers on the DC and making them always available. Each workstation could then have a default printer that is closest to them.

Can you elaborate?

All the printers are shared and always available. Im gonna try editing the logon script (which maps user drives, among other things) and remove any reference to the printers script. Then, like you said, set up default printers on each workstation.

Sure. I would eliminate any scripts and place users in groups based on their location in the building. Then apply share permissions for each printer based on that grouping. This way, users will only be able to access printers in their area.

If I do not use scripts, what do I do for drive mapping?

If you do not use scripts, you can map a drive letter (to a local folder or a network location) from Windows Explorer or My Computer by choosing Map Network Drive... from the Tools menu.

Yes, I know that. But we're talking about 100+ users, with multiple drives, that occasionally change, almost half are Terminal Server users.

Then you'll want to use a logon script. That's not a static setting so there's no way to set it via Group Policy that I'm aware of.

So Im back to where I started.

Another detail that may be a clue-originally there was an spson R380 in the script. Something in the driver kept loading a printer monitor (ink level etc) to local machines. Turn it off and it reinstalled itself. That printer has been removed from the script and the server. But I suspect that there is a connection between it and the spooling error. Something from that printer is cached somewhere on local machines.

I imagine that the printer and associated drivers are still installed. Disconnecting it will not remove those. Roll out an uninstall for it.