prndrvr.vbs and prnport.vbs work fine on x64
WMI only allows signed driver installation so if unsigned drivers are used prndrvr.vbs will not work on x86 or x64.
WMI also does not support cluster names so the vbs scripts in system32 must be targeted against a non clustered machine
-- Alan Morris Windows Printing Team Search the Microsoft Knowledge Base here: http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
This posting is provided "AS IS" with no warranties, and confers no rights.
"Eric" <ericjdavis[ at ]gmail.com> wrote in message news:1181692321.513243.261190[ at ]a26g2000pre.googlegroups.com...
[Quoted Text] >I would like to script the creation of 50+ printers on a new x64 R2 > Windows 2003 server. That includes 50 ports, with 50 printers shared > out. (using VB script or PowerShell) > > For this task, I normally use a script (vbscript) I wrote which used > PRNADMIN.DLL. (works great remotely or locally on a x32 server) > > However, I've been unsuccesful adding ports and printers using the > same script on an x64 server. (both remotely and locally) - (remotely > was using a x32 client) > > The scripts, prndrvr.vbs & prnport.vbs, (as supplied with the install > of 2003 x64 R2), also do NOT work. > > I HAVE been successful in using RUNDLL32 PRINTUI.DLL,PrintUIEntry to > add the printers, (and even install the drivers), but it only works > LOCALLY on the x64 server, (which is ok i suppose), but the problem > is, I can't figure out how to add the local TCP/IP ports. > > So, the short and simple question is: > > Can anyone tell me how to add TCP/IP ports to a x64 2003 R2 server > using Vbscript or command line? > > -Eric > > ps - (WMI doesn't work either) >
|