Managing network printer connections on workstations has always been a
nuisance. Where I work, we insist that network printer connections be
created only on a per computer basis, which helps (see 2 below). We manage
these connections centrally, but unfortunately, some people still add per
user printer connections.
1. network printer connections are, by default, per user not per computer.
This means that that printer connections only have meaning for logged on
users.
2. it is possible to make per computer network printer connections - see for
example
http://members.shaw.ca/bsanders/NetPrinterAllUsers.htm
3. there are some printer related scripts that might help - see
http://members.shaw.ca/bsanders/Printer Scripts.htm. Unfortunately, the
prnmngr.vbs does not list network printer connections
4. Windows 2003 R2 has the Printer Management Console - this is a very handy
tool, but unfortunately does not have a way to show which network printers
are currently defined on which workstations. If you have a domain at the
Windows 2003 R2 functional level, you can push printer connections per user
or per computer using the Print Management Console in conjunction with a
GPO. Then users don't have to add printers themselves and it is easier to
manage printers.
