[prev in list] [next in list] [prev in thread] [next in thread] 

List:       thin
Subject:    [THIN] Re: OT: install a print driver from a print server via script
From:       "Joe Shonk" <joe.shonk () gmail ! com>
Date:       2010-01-18 21:00:38
Message-ID: 4b54cbf8.0604c00a.4492.ffffecf5 () mx ! google ! com
[Download RAW message or body]

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@freelists.org [mailto:thin-bounce@freelists.org] On Behalf
Of Steve Snyder
Sent: Monday, January 18, 2010 12:25 PM
To: thin@freelists.org
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!


[Attachment #3 (text/html)]

<html xmlns:v="urn:schemas-microsoft-com:vml" \
xmlns:o="urn:schemas-microsoft-com:office:office" \
xmlns:w="urn:schemas-microsoft-com:office:word" \
xmlns:x="urn:schemas-microsoft-com:office:excel" \
xmlns:p="urn:schemas-microsoft-com:office:powerpoint" \
xmlns:a="urn:schemas-microsoft-com:office:access" \
xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" \
xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" \
xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" \
xmlns:b="urn:schemas-microsoft-com:office:publisher" \
xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" \
xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" \
xmlns:odc="urn:schemas-microsoft-com:office:odc" \
xmlns:oa="urn:schemas-microsoft-com:office:activation" \
xmlns:html="http://www.w3.org/TR/REC-html40" \
xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" \
xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" \
xmlns:Repl="http://schemas.microsoft.com/repl/" \
xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" \
xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" \
xmlns:ppda="http://www.passport.com/NameSpace.xsd" \
xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" \
xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" \
xmlns:ds="http://www.w3.org/2000/09/xmldsig#" \
xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" \
xmlns:udc="http://schemas.microsoft.com/data/udc" \
xmlns:xsd="http://www.w3.org/2001/XMLSchema" \
xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" \
xmlns:ec="http://www.w3.org/2001/04/xmlenc#" \
xmlns:sp="http://schemas.microsoft.com/sharepoint/" \
xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" \
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" \
xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" \
xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" \
xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" \
xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" \
xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" \
xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" \
xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" \
xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" \
xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" \
xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" \
xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" \
xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" \
xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" \
xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" \
xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" \
xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="&#1;" \
xmlns="http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
code
	{mso-style-priority:99;
	font-family:"Courier New";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=EN-US link=blue vlink=purple>

<div class=Section1>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>For native drivers, use this as you driver path: \
systemroot%\inf\ntprint.inf<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Obviously, you&#8217;ll have to supply %Printer_Name% and \
%PrintDriverPath%<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>RUNDLL32 PRINTUI.DLL,PrintUIEntry /ia /m
&quot;%Printer_Name%&quot; /v &quot;Windows 2000, Windows XP and Windows Server
2003&quot; /f &quot;%PrintDriverPath%&quot;<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>

<p class=MsoNormal><b><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> thin-bounce@freelists.org \
[mailto:thin-bounce@freelists.org] <b>On Behalf Of </b>Steve Snyder<br>
<b>Sent:</b> Monday, January 18, 2010 12:25 PM<br>
<b>To:</b> thin@freelists.org<br>
<b>Subject:</b> [THIN] OT: install a print driver from a print server via
script<o:p></o:p></span></p>

</div>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

<p class=MsoNormal>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<span style='font-size:10.0pt;font-family:"Courier New"'><br>
<br>
</span>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.<br>
<br>
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.<br>
<br>
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.<br>
<br>
Any ideas, samples, tidbits or other trivia will be welcome!<o:p></o:p></p>

</div>

</body>

</html>


************************************************
For Archives, RSS, to Unsubscribe, Subscribe or 
set Digest or Vacation mode use the below link:
http://www.freelists.org/list/thin
Follow ThinList on Twitter
http://twitter.com/thinlist
Thin List discussion is now available in blog format at:
http://thinmaillist.blogspot.com
Thinlist MOBILE Feed
http://thinlist.net/mobile
************************************************

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic