GlazedHam
join:2004-04-28
Milford, CT
| Force Printer Install on Domain to Workstations
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?
And is there a way to lock down the printer preferences on workstations from a domain?
Thanks for any info you can pass on. |
|
Rob
In Deo speramus, God Bless the USA
Premium
join:2001-08-25
Kendall, FL | I know you can on Windows 2003. Is that what you are using? It's called the Print Management Component. |
|
GlazedHam
join:2004-04-28
Milford, CT | reply to GlazedHam
Yes, we are running Serer 2003. |
|
Rob
In Deo speramus, God Bless the USA
Premium
join:2001-08-25
Kendall, FL | See if this helps:
»www.microsoft.com/technet/techne···rinters/ |
|
huntermcdole
Premium
join:2005-08-01
Tucson, AZ
 ·Cox HSI
3 edits | reply to GlazedHam
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)
The file is named printer.bat
|
|
kc8jwt
join:2005-10-27
Cheshire, OH
| reply to GlazedHam
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)
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.
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. |
|
yaplej
CCNA
Premium
join:2001-02-10
White City, OR
·Charter Pipeline
 ·Clearwire Wireless
| Here is how we do it. This makes the printer a user setting rather than a system setting.
|
|
bilbusb
join:2003-04-10
Tucker, GA | reply to GlazedHam
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.
Google vbs login scripts there are a ton. |
|
tekmunki
Tekmunki
Premium
join:2001-12-06
Lake City, FL
clubs: 
 ·NuVox Communications
| reply to GlazedHam
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.
--
TekMunki
"There are 10 types of people in this world, those who understand binary and those who don't."
www.tekmunki.com |
|
