<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>Re: Force Printer Install on Domain to Workstations in No, I Will Not Fix Your #@$!! Computer</title>
<link>http://www.dslreports.com/forum/r19523877</link>
<description></description>
<language>en</language>
<pubDate>Fri, 04 Dec 2009 01:33:18 EDT</pubDate>
<lastBuildDate>Fri, 04 Dec 2009 01:33:18 EDT</lastBuildDate>

<item>
<title>Re: Force Printer Install on Domain to Workstations</title>
<link>http://www.dslreports.com/forum/remark,19523877</link>
<description><![CDATA[<A HREF="/useremail/u/532180"><b>tekmunki</b></A> : In 2003 R2, there's a domain policy for pushing out printers.  Of course, I had to push out the client "pushprinters.exe" to the client machines via a login script, but it really does make managing a large amount of pushed printers easier.<br><small>--<br>TekMunki<br>"There are 10 types of people in this world, those who understand binary and those who don't."<br><br><A HREF="http://www.tekmunki.com">www.tekmunki.com</a></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,19523877</guid>
<pubDate>Wed, 28 Nov 2007 10:04:40 EDT</pubDate>
</item>

<item>
<title>Re: Force Printer Install on Domain to Workstations</title>
<link>http://www.dslreports.com/forum/remark,19476512</link>
<description><![CDATA[<A HREF="/useremail/u/797429"><b>bilbusb</b></A> : use a vbs login script you can add printers based on group membership. If the computer is a member of a group such as "lab1" it will install the printer.<br><br>Google vbs login scripts there are a ton.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,19476512</guid>
<pubDate>Tue, 20 Nov 2007 01:06:31 EDT</pubDate>
</item>

<item>
<title>Re: Force Printer Install on Domain to Workstations</title>
<link>http://www.dslreports.com/forum/remark,19459669</link>
<description><![CDATA[<A HREF="/useremail/u/310673"><b>yaplej</b></A> : Here is how we do it.  This makes the printer a user setting rather than a system setting.<br><br><textarea name="code" class="text" cols=50 rows=10>rem add printer1&#012;rundll32 printui.dll,PrintUIEntry /in /n"\\servername\printer1"&#012;rem add printer2&#012;rundll32 printui.dll,PrintUIEntry /in /n"\\servername\printer2"&#012;rem make printer2 default&#012;rundll32 printui.dll,PrintUIEntry /y /n"\\servername\printer2"&#012;</textarea><!--end code block-->]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,19459669</guid>
<pubDate>Fri, 16 Nov 2007 23:31:27 EDT</pubDate>
</item>

<item>
<title>Re: Force Printer Install on Domain to Workstations</title>
<link>http://www.dslreports.com/forum/remark,19431374</link>
<description><![CDATA[<A HREF="/useremail/u/1282323"><b>kc8jwt</b></A> : I am doing this now with Group Policy in Windows 2003 R2 now, but before that I was using a batch file, but it had a twist. Since I am in a school setting, we didn't want all of the printers installed by default. We wanted certain printers installed on certain computers. I embeded it in the login script. I did the following when I did it. (As an example)<br><br><textarea name="code" class="text" cols=50 rows=10>IF EXIST %windir%\dd.txt GOTO DD&#012; &#012;:DD&#012;c:\windows\con2prt /cd \\tccc-server\drafting_hp_laser&#012;c:\windows\con2prt /c \\base-station\hp_plotter&#012;c:\windows\con2prt /c \\tccc-server\cta_hp_plotter&#012;GOTO End&#012;</textarea><!--end code block--><br>The con2prt program I believe I got out of the Windows 2000 Resource kit. We placed a text file on the local machine in the windows directory. There was nothing in the file. We just looked for the file name. The con2prt will also disconnect printers. We have done that when we have changed printers in classrooms to get rid of old print shares.<br><br>We still use this method because I have not found a way yet to set a default printer with group policy when there is more than one printer to install. So we use this method. In some places, we just set one printer and then encode in the group policy a location so that when they browse the active directory, we have already populated a locations so that when they hit search, they only get the printers in that room. It doesn't mean they can't just erase the location and search the entire directory, but if they see the printer they are looking for.<br>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,19431374</guid>
<pubDate>Mon, 12 Nov 2007 18:35:38 EDT</pubDate>
</item>

<item>
<title>Re: Force Printer Install on Domain to Workstations</title>
<link>http://www.dslreports.com/forum/remark,19430999</link>
<description><![CDATA[<A HREF="/useremail/u/1241346"><b>huntermcdole</b></A> : I use a login script to add printers.  Here is how I check for a printer and then add one if needed. (Works on XP Clients, unknown about others)<br><br>The file is named printer.bat<br><br><textarea name="code" class="text" cols=50 rows=10>REM ***** Check and Install Copier*****&#012; &#012;cscript %systemroot%\system32\prnmngr.vbs -l | find "Printer name \\server\TOSHIBA e-STUDIO450Series PCL6"&#012;IF ERRORLEVEL 1 (&#012;cscript %systemroot%\system32\prnmngr.vbs -ac -p "\\server\TOSHIBA e-STUDIO450Series PCL6"&#012;echo "\\server\TOSHIBA e-STUDIO450Series PCL6 installed")&#012;</textarea><!--end code block-->]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,19430999</guid>
<pubDate>Mon, 12 Nov 2007 17:33:04 EDT</pubDate>
</item>

<item>
<title>Re: Force Printer Install on Domain to Workstations</title>
<link>http://www.dslreports.com/forum/remark,19430892</link>
<description><![CDATA[<A HREF="/useremail/u/460388"><b>Rob</b></A> : See if this helps:<br><br>&raquo;<A HREF="http://www.microsoft.com/technet/technetmag/issues/2006/08/ManagePrinters/" >www.microsoft.com/technet/techne&middot;&middot;&middot;rinters/</A>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,19430892</guid>
<pubDate>Mon, 12 Nov 2007 17:15:14 EDT</pubDate>
</item>

<item>
<title>Re: Force Printer Install on Domain to Workstations</title>
<link>http://www.dslreports.com/forum/remark,19430788</link>
<description><![CDATA[<A HREF="/useremail/u/997973"><b>GlazedHam</b></A> : Yes, we are running Serer 2003.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,19430788</guid>
<pubDate>Mon, 12 Nov 2007 16:59:01 EDT</pubDate>
</item>

<item>
<title>Re: Force Printer Install on Domain to Workstations</title>
<link>http://www.dslreports.com/forum/remark,19430541</link>
<description><![CDATA[<A HREF="/useremail/u/460388"><b>Rob</b></A> : I know you can on Windows 2003. Is that what you are using? It's called the Print Management Component. ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,19430541</guid>
<pubDate>Mon, 12 Nov 2007 16:26:22 EDT</pubDate>
</item>

<item>
<title>Force Printer Install on Domain to Workstations</title>
<link>http://www.dslreports.com/forum/remark,19430438</link>
<description><![CDATA[<A HREF="/useremail/u/997973"><b>GlazedHam</b></A> : Is there a way to force a new printer on the Server to get installed on to everyone's computer automatically instead of having the end user go to Add Printer or double clicking on the server name by going Start,Run and typing \\servername?<br><br>And is there a way to lock down the printer preferences on  workstations from a domain?<br><br>Thanks for any info you can pass on.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,19430438</guid>
<pubDate>Mon, 12 Nov 2007 16:08:45 EDT</pubDate>
</item>

</channel>
</rss>
