Re: loading a printer driver w/ a script
From: Parley (pdkennellynot_at_yahoo.com)
Date: 02/13/04
- Next message: Parley: "Re: AD Printers missing"
- Previous message: Anthony: "Re: printer subsystem unavailable"
- In reply to: Parley: "loading a printer driver w/ a script"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 13 Feb 2004 11:10:43 -0800
Well,
I'm guessing since no one answered, that no one knows the answer to my
question. I was able to fix my problem by eliminating the -h \\path and
just including the path with the filename like:
-i \\server\path\driver.inf
If this is not the way MS intended this to work then they should change the
documentation or correct the script itself, but as of right now the
documentation does not support the actual functionality of the script.
I hope that this information is useful to someone else out there as well.
-Parley
"Parley" <pdkennellynot@yahoo.com> wrote in message
news:u5UQLaZ8DHA.2412@TK2MSFTNGP09.phx.gbl...
> Hi, I am trying to automate my printer management and am able to do
> everything except add a driver. I'm using the following command, but I
keep
> getting an error code 87. Any suggestions. This is the EXACT path that I
> use when adding the printer via the add a printer wizard. Please excuse
the
> wrapping.
>
> cscript prndrvr.vbs -a -m "hp deskjet 970c series" -h
> \\server\install\printers\970Cse\win2k_xp\enu\drivers\win2k_xp -i
> hpf970k.inf
>
>
> TIA
> Parley
>
>
- Next message: Parley: "Re: AD Printers missing"
- Previous message: Anthony: "Re: printer subsystem unavailable"
- In reply to: Parley: "loading a printer driver w/ a script"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|