Issue 4988 - Better Centralized Printer Management
Summary: Better Centralized Printer Management
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: OOo 1.0.0
Hardware: PC Linux, all
: P4 Trivial (vote)
Target Milestone: AOO PleaseHelp
Assignee: bettina.haberer
QA Contact: issues@sw
URL:
Keywords: oooqa, rfe_eval_ok
Depends on:
Blocks:
 
Reported: 2002-05-17 14:44 UTC by drichard
Modified: 2005-09-19 22:38 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description drichard 2002-05-17 14:44:41 UTC 
From a server running multiple users of OO at the same time, there needs to be a
better way for IT people to manage the printers and configure them and have
everyone get the changes instantly.  We don't allow the users to configure their
own printers.  Our work around right now is to copy a fresh copy of psprint.conf
into their home directory each time that they run OO, but that blows out their
selected default printer because they are stored in the same file.  psprint.conf
should be soft linked back to a centralized copy for everyone and the default
printer should be stored in another file local to their home directory.
Comment 1 stefan.baltzer 2002-10-01 17:03:19 UTC 
Reassigned to Joost.
Comment 2 philipp.lohmann 2002-10-01 18:01:29 UTC 
The copying is unnecessary. Ooo reads the psprint.conf from the
network installation and the the psprint.conf inside the user
installation, merging the printers configured in there.

Please also note that psprint.conf contains much more than the default
printer: it also contains various other information like which paper
size to use in a new document, which output tray to use, duplex, etc.
All these things are user editable. By implementing what you described
we would take away this flexibility from everybody else.

What one COULD think about was to invent an "editable" attribute to a
printer which would make the printer not editable for the user unless
he has the rights to change the network psprint.conf. Also an
attribute in the network psprint.conf could be invented that prevents
the user from adding new printers.
Comment 3 Joost Andrae 2002-10-02 11:22:38 UTC 
JA->FT: reassigned as RFE to you.
Comment 4 drichard 2003-09-22 19:31:32 UTC 
  This has gotten better with the fact that you can use a global
psprint.conf file now and everyone reads it @ startup time.  However,
OO isn't keeping track of your individual desired printer and
papertray when deployed this way.
Comment 5 falko.tesch 2003-10-01 11:19:47 UTC 
This is an issue for the SCM.
Please assign this to Götz Wohlberg, thx.
Comment 6 falko.tesch 2003-10-01 11:20:10 UTC 
started
Comment 7 drichard 2005-09-12 17:40:27 UTC 
I feel that this issue has gotten much better since I opened this bug over 3
years ago.   It's picking up CUPs printers perfectly now, and centralized
psprint.conf management is working well.

It's marked as "STARTED", but I would say we can close it.
Comment 8 lohmaier 2005-09-19 22:37:00 UTC 
Thanks for the feedback. I'll close it as worksforme.
Comment 9 lohmaier 2005-09-19 22:38:24 UTC 
closing