Re: Network Printers and XP

Tech-Archive recommends: Fix windows errors by optimizing your registry

What groups do the users presently belong to and have you confirmed that in
your present setup the users cannot add network printers?

"jimmy" <jimmy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4B6317F3-21ED-4B55-8C9C-9842D32F883C@xxxxxxxxxxxxxxxx
> If the users are locked down, Should I make them local admins, then
> installl
> the printer, then remove them from this group? I am trying to keep these
> students locked down as much as possible. THANKS...
>
> "Kevin Longley" wrote:
>
>> Network printers are profile related so you must be logged on as the user
>> when adding.
>>
>> "jimmy" <jimmy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:47619191-9B7F-4276-A4F2-6F61B3019C0D@xxxxxxxxxxxxxxxx
>> >I have a 2003 Server with 10 Xp clients. When I add a network printer
>> >logged
>> > on as an admin, all is ok. When I log off and on as a regular user, the
>> > network printer is gone. When I log back on as admin, it re-appears.
>> > But
>> > if I
>> > add a local printer, it shows up when logged on as the reg. user. What
>> > policy
>> > or step am I missing. Thanks..
>>
>>
>>


.

Relevant Pages

  • Re: Outlook 2003 / Cant change printer
    ... Raymond Smith wrote: ... > I have an interesting problem, I have a client where we setup a ... I presume you have network printers? ...
    (microsoft.public.windows.server.sbs)
  • Re: Printing to a Lanier LD160c does not work
    ... my setup is like yours for network printers except of that. ...
    (freebsd-questions)
  • Re: Problems with adding printers
    ... problems adding network printers to the system. ... printtool, setup and the web interface do not seem to be working well with each other. ...
    (RedHat)
  • Re: RM/Cobol - Printing in XP
    ... > The application that we are using has the following setup. ... I have now found that I can print to LPT1 ... > through LPT5 to any of the network printers as long as it is set up with the ... There is a patch available to fix that bug. ...
    (comp.lang.cobol)