Printer script woes

[witch]

We allocate printers via a logon script - we have done it via GPP before but there were issues so we went back to scripts.

There is a script called "add all printers.vbs" which looks like this:

Set printers

' ******************************

On Error Resume Next

Dim objNetwork

Set objNetwork = CreateObject("WScript.Network")

 

objNetwork.AddWindowsPrinterConnection "\\DCSERVER01\Year5-Laser"

objNetwork.AddWindowsPrinterConnection "\\DCSERVER01\Year7-Laser"

objNetwork.AddWindowsPrinterConnection "\\DCSERVER01\PracticalNew HP 2025"

 

This works absolutely fine. We have just had a networked photocopier installed and so I added a line to the script thus:

Set printers

' ******************************

On Error Resume Next

Dim objNetwork

Set objNetwork = CreateObject("WScript.Network")

 

objNetwork.AddWindowsPrinterConnection "\\DCSERVER01\Year5-Laser"

objNetwork.AddWindowsPrinterConnection "\\DCSERVER01\Year7-Laser"

objNetwork.AddWindowsPrinterConnection "\\DCSERVER01\PracticalNew HP 2025"

objNetwork.AddWindowsPrinterConnection "\\DCSERVER01\RicohPhotocopier"

 

 

It doesn't work. The other printers appear but not the Ricoh. I have reserved it an IP. I can ping it. I have shared it as "RicohPhotocopier"

 

I have also written a script with JUST the Ricoh in it and that doesn't work either.

I created a test OU with my own laptop in it and applied both scripts - again, the other printers appeared but not the Ricoh.

 

Can anyone shed any light on this?

I have been told it might be a driver issue but the Ricoh guys put in the latest drivers. I can print to the Ricoh from the server with no issues.

[FN-GM]

If you run to the server DCSERVER01 in Windows explorer do you see the printer? Can you double click and install it manually? It doesn't look like its the script but rather the printer share.

[witch]

Forgot to say - if I run the script manually it works...

Yes, I can see the photocopier and install it manually

[FN-GM]

Right that throws my theory out of the Window

 

How long did you leave the printer to appear? In the past I have had Konica MFP's take a wile to appear in the printers due to the sheer size of the drivers.

[witch]

..hours....sadly

[sted]

both x64 and x86 drivers installed on server (if you have x86 workstations)?

point and print settings set so it will just get on and install the driver?

[mac_shinobi]

What driver exactly and if you make the sharename shorter and one word does that make any difference so for example

 

RicohMFD

[Arthur]

It doesn't work.

The following might be worth a try?

 

cscript c:\windows\system32\printing_admin_scripts\en-us\prnmngr.vbs -ac -p \\DCSERVER01\RicohPhotocopier

 

Prnmngr.vbs is included with Windows.

[witch]

Both drivers are definitely there - installed by Ricoh engineers - specially modified for the settings we want, apparently

Not sure where to look for the setting you mention - but as I can install it manually presumably it is OK

I keep coming back to the sharename issue but I cannot see anything wrong with it

Edited November 10, 2014 by witch

[sted]

point and print is gpo

user/computer (generally i set it on the pc)administrative templates\printers\point and print restrictions

 

generally I set it to enabled and leave box 1 unticked tick users can only print to machines in their forest

 

then set the next 2 drop down boxes to do not show warning or elevation prompt

[witch]

I've shortened the share name to "Ricoh" but it still won't install. @Arthur - will have a go

[witch]

thanks @sted. Have looked and none of the printer scripts - the working ones included - have any of these settings enabled so it seems unlikely that this is the issue

[sted]

thanks @sted. Have looked and none of the printer scripts - the working ones included - have any of these settings enabled so it seems unlikely that this is the issue

 

depends if the drivers are in the base image or signed as lots of printer drivers arnt signed and this can cause problems

[witch]

I see. Maybe it is a driver signing issue. Will have a go at adding that setting

[witch]

Have added the setting and it hasn't made any difference, sadly.

Cannot get the other one to work at all, @Arthur

[witch]

This is silly - I am sure it is something really daft

[mac_shinobi]

PM sent hopefully that helps some what

[Duke5A]

Sorry if I'm asking questions to things already answered, but point and print is disabled and you don't get any security prompts when running the script by hand?

 

If it isn't working when the logon script fires, but it is when you run it by hand then it could be the system is still processing something and skips over that printer because it's busy. I've had issues when scripting things in VB where I've needed to give it a breather or it would just skip over things. Try adding this right before you add the photocopier:

 

WScript.Sleep (500)

 

It'll pause the script for a half second. You can experiment with different values too.

[witch]

Thanks. Have put a call in to Ricoh support as @mac_shinobi thinks it might be related to their customised driver.

Pausing it makes no difference, unfortunately.

[detjo]

Users have sufficient share and security permissions for this printer?

[Gaz]

What do the event logs say? Are there any errors being recorded?

[witch]

No errors that anyone can see. The script runs, but the last line with the new printer in it just...does nothing...unless you run it manually. So what does the "calling up" of the script ask for that the running it manually does not?

Users have all the share and permissions they need.

 

- - - Updated - - -

 

No errors that anyone can see. The script runs, but the last line with the new printer in it just...does nothing...unless you run it manually. So what does the "calling up" of the script ask for that the running it manually does not?

Users have all the share and permissions they need.

[mac_shinobi]

No errors that anyone can see. The script runs, but the last line with the new printer in it just...does nothing...unless you run it manually. So what does the "calling up" of the script ask for that the running it manually does not?

Users have all the share and permissions they need.

 

- - - Updated - - -

 

No errors that anyone can see. The script runs, but the last line with the new printer in it just...does nothing...unless you run it manually. So what does the "calling up" of the script ask for that the running it manually does not?

Users have all the share and permissions they need.

 

How is the script being run ie as a startup script or a logon script etc as think there are a few ways to make the script run and each way launches the script with different access rights

 

Just a thought

[sted]

who are you manually running it as a user or an admin?

[witch]

It is a login script. Manually running it as admin - users don't have permissions to see it.

It can't be permissions on the "all printers" script as it works fine except for the last line calling up the Ricoh

 

- - - Updated - - -

 

It is a login script. Manually running it as admin - users don't have permissions to see it.

It can't be permissions on the "all printers" script as it works fine except for the last line calling up the Ricoh