Re: network printer script error
- From: "asdf" <asdf@xxxxxxxx>
- Date: Sat, 17 Mar 2007 05:31:07 -0400
If the name is legit and legible.
Go for it.
It happens what happens on any window smachine.
It will read from a named connection.
If it is an IP address 30.000 miles away
or on an Mars ice shelf, it will.
Glory to the founders of the protocols.
"Charles Blair" <charles_blair@xxxxxxxxxxx> wrote in message news:%23G4cOEJJHHA.1008@xxxxxxxxxxxxxxxxxxxxxxx
What happens if you copy the script to the server and run it locally?
Charles
"Zac Mutrux" <ZacMutrux@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:842F71B5-21E8-4AAF-B5F9-61608FBCCE31@xxxxxxxxxxxxxxxxI am trying to add a network printer to computers automatically. It seems to
work fine on Windows XP, but it throws an error on Windows Server 2003.
The script:
Set WshNetwork = CreateObject("WScript.Network")
WshNetwork.AddWindowsPrinterConnection "\\server\labprint"
The error:
---------------------------
Windows Script Host
---------------------------
Script: \\VYDC.local\SysVol\VYDC.local\Policies\{F0E4DA90-E6A0-40E8-A1D5-384785B01C89}\User\Scripts\Logon\printers.vbs
Line: 2
Char: 1
Error: The filename, directory name, or volume label syntax is incorrect.
Code: 8007007B
Source: (null)
---------------------------
OK
---------------------------
Thanks for any assistance you may be able to offer.
Zac
.
- Prev by Date: Re: issues with pipe operator causing hang while executing a batch fil
- Next by Date: Re: WSH corrupt but 5.6 overtop doesn't fix it
- Previous by thread: Re: issues with pipe operator causing hang while executing a batch fil
- Next by thread: Re: WSH corrupt but 5.6 overtop doesn't fix it
- Index(es):
Relevant Pages
|
