Re: Default printers

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

From: Rykymus (Rykymus_at_discussions.microsoft.com)
Date: 09/08/04 

Date: Wed, 8 Sep 2004 08:39:03 -0700

  Everyone has a roaming profile, specifically to be able to logon to a spare
workstation in case theirs goes down. (In fact, they are restricted to only
their own workstation and the spare.) Only the 2 local admin accounts can
roam anywhere, and nobody has mandatory profiles.
  I have tried resetting their defaults, but it always switches back to
whatever printer is the default on the server. I've tried removing the logon
script that was applied by SBS during setup, assigning/denying permissions so
that users should not be able to print to printers that are not in their area
(like the one that is the default on the server), all to no avail. I even
went wading around Group Policies, (an area that I am none to comfortable
with, my expertise is in hardware) and have been unable to find anything that
looks like it might be the cause. (I have not messed with any GPO's out of
fear!)
  My SBS2003 Admin Companion states that the default printer on the server
is installed on the clients unless they have a locally attached printer. But
it says nothing about having multiple printers setup on the server.
  The suggestions about GPO's and logon scripts sound promising, (especially
a logon script that would assign the appropriate printers) but I have zero
experience in scripts. However, I am a fast learner, so if someone could
point me to a resource that might get me started it would be greatly
appreciated.

RCB (who is running out of hair to pull out)

"Lanwench [MVP - Exchange]" wrote:

> Rykymus wrote:
> > Maybe I'm not giving enough info. Any printer that is setup as the
> > default printer on the Small Business 2003 Server is automatically
> > assigned as the default printer for any user that logs in that does
> > not have a printer physically attached to their computer.
> > The server is in the operations office. There is a local printer
> > in the Ops office that is shared via a print server amongst the
> > workstations in the Ops office. There is also another printer in the
> > administration workroom that is shared in the same fashion. I would
> > like to have both printers setup on the server so that any printing
> > to these two printers is done through the server. That way, if a
> > document gets stuck in the print que, it will be stuck in the
> > server's print que which can easily be discoverd and remedied, rather
> > than having to search through 15 workstations' print ques. If I make
> > the Ops Printer the default printer on the server, then the Ops
> > Printer becomes the default printer for everyone in the domain, many
> > of which are in the administration workroom, which is a physically
> > seperate building. I have tried every manner of permissions, all
> > without success.
>
> Have the users change the printer to the default they wish in their own
> profile. This should stick, unless you're doing something funky that
> automatically deletes/reassigns printers, or having people share a common
> mandatory profile, etc.
> >
> > "Lanwench [MVP - Exchange]" wrote:
> >
> >> Rykymus wrote:
> >>> Hello,
> >>>
> >>> We're running pretty much a default out of the box setup here,
> >>> nothing interesting. No ISA, no fax, no SQL. Problem is this.
> >>> There are 18 users, 7 of which share a printer using an external
> >>> Netgear print server. Problem is that if a document gets stuck in
> >>> one users print que, no one can print. I tried setting up the
> >>> printer through the small business server, but it forces everyone on
> >>> the domain's default printer to be the one setup on the small
> >>> business server. This is a problem since a few of the users are in
> >>> different parts of the building and have their own local printer.
> >>> (One of the is the Executive Director.)
> >>
> >> Why does that make a difference? Just don't make it the default for
> >> those users.
> >>
> >>> Unfortunately, these
> >>> adversely affected users are not savvy enough to check that they
> >>> are printing to the correct printer. I have tried denying print
> >>> privileges to those users, but to no avail.
> >>> Any ideas would be greatly appreciated.
> >>>
> >>> RCB
>
>
>
>

Relevant Pages

  • Re: Daily Server Report (Critical Errors, Event ID: 537)
    ... Also, Logon type of 3 is a network logon, this is considered a ... Does this issue happen on client workstation or server? ... Does your server and all clients' workstation work well now? ... issue in your Network? ...
    (microsoft.public.windows.server.sbs)
  • Re: Daily Server Report (Critical Errors, Event ID: 537)
    ... Also, Logon type of 3 is a network logon, this is considered a ... Does this issue happen on client workstation or server? ... Does your server and all clients' workstation work well now? ... issue in your Network? ...
    (microsoft.public.windows.server.sbs)
  • Re: "Classic logon" screen in XP does not remeber the user name
    ... John N ... I recently upgraded a workstation from Windows 2000 Pro to Windows XP Pro. ... can copy missing shortcuts to the new profile. ... you can work from the server and ...
    (microsoft.public.windowsxp.security_admin)
  • Re: DCOM Errors in Event log
    ... A time difference between the workstation and the server do you? ... An error occurred during logon ... Les Connor [SBS Community Member - SBS MVP] ... on the server in the security log we are getting error 537 in the event log. ...
    (microsoft.public.windows.server.sbs)
  • Re: AD Newbie Questions
    ... Remember that though DNS and AD are ... You can copy the profile over, either doing a straight copy (get the ... > I've reviewed a few books on Server2K3, but before I> promote my server to a Domain Controller, there are still a few specifics> where I'd appreciate some guidance. ... I would install Studio.NET on the XP Pro workstation. ...
    (microsoft.public.windows.server.active_directory)