If you are on server 2003 R2, you can use the new printer deployment tool.
It works great, the only problem, you cannot set a default printer. This is
not an issue if you do not have any other printers installed, including the
office image writer.
http://www.windowsnetworking.com/articles_tutorials/Deploying-Printers-Group
-Policy-Windows-R2.html
Travis Cousineau
HelpDesk Coordinator
Gainey Transportation Services
616-530-8558 x1286
http://www.gaineycorp.com
-----Original Message-----
From: MSU Network Administrators Group [mailto:[log in to unmask]] On
Behalf Of Troy Murray
Sent: Thursday, July 26, 2007 2:17 PM
To: [log in to unmask]
Subject: Re: [MSUNAG] Pesky network printer connection
It was nice for us because it would first look at the printer they had
set as the default, if it was a network printer it would store the
path, then delete all of the network printers, then re-attach all of
the network printers including any new ones, then set the default
printer again if they had a network one set as such in the past.
Worked great for me at the insurance company I used it at and the lab
on campus I help with .
-t
On 7/26/07, Ehren Benson <[log in to unmask]> wrote:
> Interesting, I might run this in a test environment and see how it does
> but that could be handy if it works out.
>
> Thanks!
>
> Ehren J. Benson, MCSE
> Windows Systems Administrator
>
> [log in to unmask]
> 517-355-9200 x2569
>
>
> -----Original Message-----
> From: MSU Network Administrators Group [mailto:[log in to unmask]] On
> Behalf Of Troy Murray
> Sent: Thursday, July 26, 2007 1:57 PM
> To: [log in to unmask]
> Subject: Re: [MSUNAG] Pesky network printer connection
>
> Not sure if this would help you or not, I would map the network printers
> through a script that runs when they would login to my AD.
> We were only using XP so I can't confirm that this works with Windows
> 2000 workstations as I know the WSCRIPT is newer with XP.
>
> -t
>
> PS: Of course you need to change the extension to .vbs to run it
>
>
> On 7/26/07, Ehren Benson <[log in to unmask]> wrote:
> >
> >
> >
> >
> > Hey NAG-
> >
> >
> >
> > I have a sticky problem that is eluding me causing grief. In one of
> > our labs I this command to connect a network printer and make it
> > available to all users of the computer:
> >
> >
> >
> > rundll32 printui.dll,PrintUIEntry /ga /n\\server\%printername%
> >
> >
> >
> > The command seems to have worked because when I connect with any user
> > that has admin rights the printer shows up and works just fine.
> > However when I log in with the normal account that would be used on
> > the computer which is just a normal user account the printer does NOT
> show up.
> >
> >
> >
> > Also when I browse for the printer and right click on it and click
> > connect to connect it manually I get the following error:
> >
> >
> >
> > "You do not have sufficient access to your computer to connect to the
> > selected printer".
> >
> >
> >
> > When I add this user to the local administrators group and log off and
>
> > log in, as I said the printer shows up and works. Then if I remove
> > them from the local administrators group and log off and log back on
> > it does not and will not even let me manually connect to it.
> >
> >
> >
> > I am assuming that the error is why the printer is not showing up.
> > Does anyone have any ideas what I can do to give that user sufficient
> > access to the computer to connect to the printer?
> >
> >
> >
> > With 2003 that error is easy to fix as you just add that user that is
> > enabled on the "enable users to install printer drivers", but in XP
> > there is no such local policy (that I can find) Client OS is XP Pro
> > SP2. Has anyone else ran into this?
> >
> >
> >
> >
> >
> > Ehren J. Benson, MCSE
> >
> > Windows Systems Administrator
> >
> > Department of Physics and Astronomy
> >
> > Michigan State University
> >
> > 1209 A Biomed Phys Sci
> >
> >
> >
> > [log in to unmask]
> >
> > 517-355-9200 x2569
> >
> >
>
>
> --
> Troy D Murray
> Blog: http://troymurray.blogspot.com/
> AIM: troymurray72
> Skype: troy.murray
>
--
Troy D Murray
Blog: http://troymurray.blogspot.com/
AIM: troymurray72
Skype: troy.murray
|
