For native drivers, use this as you driver path: systemroot%\inf\ntprint.inf Obviously, you'll have to supply %Printer_Name% and %PrintDriverPath% RUNDLL32 PRINTUI.DLL,PrintUIEntry /ia /m "%Printer_Name%" /v "Windows 2000, Windows XP and Windows Server 2003" /f "%PrintDriverPath%" From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Steve Snyder Sent: Monday, January 18, 2010 12:25 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] OT: install a print driver from a print server via script I'm trying to figure out how to install a print driver directly from the print server via script. kix, vbscript, rundll32 printui.dll - whatever works Basically, I'm migrating print servers and the new server has some new (correct) share names and updated drivers. I've got a vbscript that can remap the printers accounting for the name changes and reset the default printer if need be, I can query the print server for the driver name associated with the new queue, I can query the client's installed drivers for that driver name, but every script sample that I've seen for actually installing the driver is for installing it from an INF file which, of course, doesn't exist in the \\print_server\print$ structure. Why via a script you ask? Because it's likely that the printers that I'm trying to install on clients (all Vista) won't already exist on them, hence the users will get prompted for elevated privileges which they don't have. Why not use GPO to set Vista to allow drivers installed from a trusted server you ask? Because the imperial group that controls our AD has deemed that to be a grave security risk. Any ideas, samples, tidbits or other trivia will be welcome!