How to ignore a user in PaperCut

KB Home   |   How to ignore a user in PaperCut

Main.IgnoreUser History

Hide minor edits - Show changes to output

May 12, 2017, at 02:02 AM by Daniel Stoeski - Please ensure that at the end of each config key, a comma follows the last username.
Added lines 17-18:

Please ensure that at the end of each config key, a comma follows the last username.
April 04, 2017, at 08:52 PM by Adam Byer - added "irc". it is in the config editor but not listed above as pointed out by customer in comments
Added line 80:
irc
December 08, 2016, at 12:13 AM by 139.130.165.134 -
Added lines 15-16:

'''Important: '''This config key can contain a maximum of 1,000 characters. If your list is longer than 1,000 characters, subsequent config keys will be created (for example, user-source.ignored-users.1). If you want to add user names to the list, make sure you add them to the last config key in the sequence.
December 07, 2016, at 11:26 PM by 139.130.165.134 -
Changed lines 10-12 from:
Ignoring a single user can be done by adding the username to the PaperCut Config Key: [@user-source.ignored-users@]

The list of user names is a simple comma separated list of
values.
to:
Use the PaperCut config key: [@user-source.ignored-users@] to specify a comma-separated list of usernames to be ignored.

You can ignore:
* a single username
* multiple usernames (using a regular expression). Regular expression
values must start with "/" and end with "/".
September 30, 2015, at 11:17 PM by Kyle - more keywords
Changed line 112 from:
[-Keywords: ignored, missing user, missing users-]
to:
[-Keywords: ignored, missing user, missing users, reserved,reserved username, sAMAccountName, username-]
January 28, 2013, at 02:20 PM by rick - clarify that ODCU will add ignored users
Changed lines 18-19 from:
If you need to ignore users that do print you may want to arrange for them to print to an [[https://www.papercut.com/products/ng/manual/ch-printer-mgmt.html#ch-printer-mgmt-add-remove-printer | Ignored Print queue]] or carefully consider modifying [[https://www.papercut.com/products/ng/manual/ch-sys-mgmt-user-group-sync.html#ch-sys-mgmt-user-group-sync-user-mgmt | On Demand User]] creation settings.
to:
If you need to ignore users that do print you may want to arrange for them to print to an [[https://www.papercut.com/products/ng/manual/ch-printer-mgmt.html#ch-printer-mgmt-add-remove-printer | Ignored Print queue]] or carefully consider modifying [[https://www.papercut.com/products/ng/manual/ch-sys-mgmt-user-group-sync.html#ch-sys-mgmt-user-group-sync-user-mgmt | On Demand User]] creation settings to make sure that ignored users are not added.
Changed lines 16-17 from:
By adding a username to this list they will not be imported in to PaperCut by the overnight sync process. However if the user(s) print to a monitored print queue they will be added, as well if they run the PaperCut User Client or log into the PaperCut User Web Client.
to:
By adding a username to this list they will not be imported into PaperCut by the overnight sync process. However if the user(s) print to a monitored print queue they will be added, as well if they run the PaperCut User Client or log into the PaperCut User Web Client.
Added lines 18-19:
If you need to ignore users that do print you may want to arrange for them to print to an [[https://www.papercut.com/products/ng/manual/ch-printer-mgmt.html#ch-printer-mgmt-add-remove-printer | Ignored Print queue]] or carefully consider modifying [[https://www.papercut.com/products/ng/manual/ch-sys-mgmt-user-group-sync.html#ch-sys-mgmt-user-group-sync-user-mgmt | On Demand User]] creation settings.
Changed lines 16-17 from:
By adding a username to this list they will not be imported in to PaperCut by the overnight sync process. However if the users print to a monitored print queue they will be added, as well if they run the PaperCut User Client or log into the PaperCut User Web Client.
to:
By adding a username to this list they will not be imported in to PaperCut by the overnight sync process. However if the user(s) print to a monitored print queue they will be added, as well if they run the PaperCut User Client or log into the PaperCut User Web Client.
Changed lines 16-17 from:
By adding a username to this list, all print jobs, copy jobs and authentication requests by that user will be ignored.
to:
By adding a username to this list they will not be imported in to PaperCut by the overnight sync process. However if the users print to a monitored print queue they will be added, as well if they run the PaperCut User Client or log into the PaperCut User Web Client.
Added lines 22-56:
___vmware_conv_sa___
_avbdeviced
_ces
_coreaudiod
_cvmsroot
_devicemgr
_dovecot
_dovenull
_dpaudio
_ftp
_installassistant
_kadmin_admin
_kadmin_changepw
_krb_anonymous
_krb_changepw
_krb_kadmin
_krb_kerberos
_krb_krbtgt
_krbtgt
_lda
_locationd
_netbios
_netstatistics
_networkd
_pcastlibrary
_postgres
_screensaver
_scsd
_softwareupdate
_taskgated
_timezone
_trustevaluationagent
_usbmuxd
_warmd
_webauthserver
Changed lines 105-107 from:
gridcontroll
@]
to:
xgridcontroller@]
Changed line 110 from:
[-Keywords: ignored, missing user, missing users-]
to:
[-Keywords: ignored, missing user, missing users-]
Added lines 18-72:
By default PaperCut ignores a number of standard system users.  They are:

->[@
Any user starting with _ (underscore)
amavisd
appowner
appserver
ard
atsserver
backup
bin
calendar
clamav
cvs
cyrus
cyrusimap
daemon
devdocs
eppc
games
installer
jabber
lp
mail
mailman
man
mcxalr
mdnsresponder
mysql
news
nobody
pcastagent
pcastserver
postfix
proxy
qtss
sandbox
securityagent
serialnumberd
spotlight
sshd
svn
sys
teamsserver
tokend
unknown
update_sharing
uucp
windowserver
www
www-data
xgridagent
gridcontroll
@]

Changed lines 6-11 from:
System accounts used in batch printing
System accounts that will never print and hence should not appear in reports (e.g. the sever server www account)
Special users who should not be tracked (e.g. "the boss")
... i'm sure you've come across more reasons that I know about that have come up through support.


to:
* System accounts used in batch printing
* System accounts that will never print and hence should not appear in reports (e.g. the sever server www account)
* Special users who should not be tracked (e.g. "the boss")
Added lines 5-11:
You may want to ignore a user for one of the following reasons.
System accounts used in batch printing
System accounts that will never print and hence should not appear in reports (e.g. the sever server www account)
Special users who should not be tracked (e.g. "the boss")
... i'm sure you've come across more reasons that I know about that have come up through support.

Changed lines 5-6 from:
This can be done by adding the username to the Config Key: [@user-source.ignored-users@]
to:
Ignoring a single user can be done by adding the username to the PaperCut Config Key: [@user-source.ignored-users@]
Added lines 1-16:
(:title How to ignore a user in PaperCut:)

Under certain, rare circumstances a customer may wish to ignore a username. A better option in most cases for restricting the users imported into PaperCut is to use a Group or Organizational Unit (OU) in your directory source as described here: [[https://www.papercut.com/products/ng/manual/ch-sys-mgmt-user-group-sync.html | User and Group Synchronization]]

This can be done by adding the username to the Config Key: [@user-source.ignored-users@]

The list of user names is a simple comma separated list of values.

Use of the Config Editor is explained here in the [[https://www.papercut.com/products/ng/manual/sys-mgmt-config-editor.html | PaperCut Manual]]

By adding a username to this list, all print jobs, copy jobs and authentication requests by that user will be ignored.

----
''Categories:'' [[Category.Users|+]]
----
[-Keywords: ignored, missing user, missing users-]

Comments

Share your findings and experience with other PaperCut users. Feel free to add comments and suggestions about this Knowledge Base article. Please don't use this for support requests.

Article last modified on May 12, 2017, at 02:02 AM
Printable View   |   Article History   |   Edit Article