Archive | PapercutMF RSS feed for this section

Papercut and AD

20 Apr

Good read if you are new to Papercut and AD

Papercut MF – Post Upgrade Checks :)

21 Oct

PaperCut is designed to support fully automated install-over-the-top upgrades. Normally no manual upgrade tasks need to be performed, however like all server-side applications, system administrators should devote some time to testing post upgrade. Administrators may find the following checklist useful. The test plan may equally be applied to new installs or server migrations.

The testing procedure is designed to take no longer than 15-minutes and encompasses operations in all critical areas of the application. It is advisable to print out this page (Printable View link is in the menu on the left) and check off the steps as the tests are performed.

  • Verify that administrators (e.g. the built-in admin user) can log into the interface at
  • View the About screen and ensure the expected version number is listed.
  • View general cost and system configuration settings and ensure that settings and data are still present after the upgrade:
    • User accounts are listed under the Users section
    • Shared Accounts listed under the Account section
    • Printer cost settings (if used)
    • Internet cost settings (if used)
    • Historical print and log data
  • Verify that end-users can log into the end-user web interface at http://servername:9191/user. e.g. use a test account to verify this.
  • Log into a workstation and ensure that the client starts as expected and list the current logged in user’s account balance (assuming you have deployed the client).
  • Perform a small manual adjustment on a test user account (Users -> [Select User] -> Adjustment & Charges). Ensure the adjustment is applied to the account balance and the user’s Recent Transactions as expected.
  • Print a print job under a test user account and confirm:
    • Print jobs list as expected under Printers -> Print Log
    • Ensure the job has charged the user as expected.
    • Ensure a corresponding transaction is listed under the user’s recent transactions list.
  • If users (or some users) are using the account selection popup to select and charge to shared accounts, perform some printing under an appropriate user account and ensure the popup is working as expected.
  • Check the App. Log (Application Event Log) section for any recent Warning or Error level messages.
  • If you have any PaperCut NG extensions installed (for example, custom web layout/design, extension modules, or integration with 3rd party systems), perform some tests and ensure these are working/displaying as expected.
  • Verify that you have a regular off-disk backup procedure in place and is continuing to backup as per your desired schedule. (editors note: every year we hear horror stories about how someone thought things were backing up. Now is a good time to check!)
  • If PaperCut is running on top of an external database system (e.g. Microsoft SQL Server, MySQL, etc.), verify that your off-disk backup procedure includes the host database.
  • Do you have any external equipment, scripts, resources? For example, scripts using the PaperCut API? If so, spend some time testing these external resources/services.
  • Take some time to explore and play with any new features! The release history page is a good place to start to gain a quick overview of what’s new. Also check out the known issues list for any important notes associated with this release. Generally print management software is pretty run-of-the-mill but we try and slip in an exciting feature inPaperCut from time to time!

Enable Email Notifications in Papercut

26 Feb

Configuring Email Notifications

Before sending notifications via email, the system needs to know the SMTP server to deliver emails to. The SMTP server can be internal or external to your organization however it must allow forwarding of emails to your users. The SMTP server will typically be the same server that users set in their email application to send emails.

To set the SMTP server:

  1. Navigate to OptionsNotifications.
  2. Find the Email Options section.
  3. Enter the SMTP server in the field provided.
  4. It is also recommended that the subject and from address are changed to be applicable for your environment.
  5. Press the Apply button.

The following advanced SMTP configuration settings are also available in the configuration editor (see the section called “Using the Config Editor”).

Name Description
notify.smtp.enable-tls Set to Y to enable STARTTLS, or N to disable it. STARTTLS is for connecting to an SMTP server port using a plain (non-encrypted) connection, then elevating to an encrypted connection on the same port.
notify.smtp.port The port to connect to on the SMTP server. Common ports include 25 or 587 for SMTP, and 465 for SMTPS.
notify.smtp.username Username for SMTP authentication. Commonly an email address.
notify.smtp.password Password for SMTP authentication.
notify.smtp.debug Produces extra SMTP related logging for troubleshooting.

Table 15.6. Advanced email notification (SMTP) settings

Important

Anti-virus software running on the PaperCut server can block/disallow SMTP connections because it attempts to block spam sent by viruses and trojans. Ensure that any anti-virus software is configured to allow PaperCut to make SMTP connections (e.g. add an exception or disable the SMTP blocking).

When anti-virus is blocking email delivery PaperCut NG will log errors like: Mail server connection failed. Software caused connection abort.. These errors are displayed in the application log or on-screen when performing email notification tests.

If there are other SMTP connection problems, you should check that your firewall allows SMTP connections, and that your SMTP server is configured to accept connections from the PaperCut server.

Email Notification Configuration Examples

Name Value
SMTP server Your internal SMTP server hostname.
notify.smtp.enable-tls N
notify.smtp.port 25
notify.smtp.username Blank.
notify.smtp.password Blank.

 

Papercut on a Mac Server – OSX and iOS Printing

16 Feb

Configuring a Macintosh Secondary Print Server

This section describes the process of setting up a secondary Mac print server. The primary Application Server may either be a Windows, Mac or a Linux basis system. PaperCut NG has full support for “mixed” or heterogeneous printing environments.

Step 1 – Ensure primary server is set up correctly

Before installing a secondary server you should take some time to ensure the primary server (central application server) is set up and running correctly. If it is not running fine now adding an extra server will only “add an extra variable to the equation” and complicate troubleshooting. Take some time now to verify that the primary server is functioning correctly. For example, verify that:

  • Printers on this server are being tracked.
  • Users are allowed top login to user pages from their workstations.
  • Administrators can access the system.

Step 2 – Ensure firewall software is set to allow access to port 9191

Secondary server needs to communicate (initiate a TCP connection) on port 9191. Administrators should ensure that any firewall software on the primary Application Server is not set to block any incoming local network traffic on this port.

Step 3 – Create the host user account

PaperCut NG runs under a non-privileged user account called “papercut”. This invisible system account is created automatically upon first install. Advanced system administrators may however have a preference to create this account manually. If you fall into this category, create the papercut account now prior to installation.

Step 4 – Install the print provider

Install the print provider software onto the secondary server. Download the latest Mac DMG disk image and execute the contained installer called PaperCut NG Secondary Server Installation.pkg.

Step 5 – Configuration

The Print Provider on the secondary server needs to know where the primary server is installed. The installer may open the appropriate configuration file after the install completes.

  1. Open a text editor such as TextEdit.
  2. Open the file:

    [app-path]/providers/print/ mac/print-provider.conf

  3. Locate the line starting with ApplicationServer= and change localhost to the name or IP address of the primary server.
  4. Save the file and exit the text editor.

Double-click on the command script /Applications/PaperCut NG/Control Printer Monitoring.command, and enable monitoring on the appropriate printers.

Step 6 – Test

The secondary server should now be configured. Log into the system as “admin” and verify that the printers are now listed under the Printers section. Perform a multi-page test print on each printer and verify that print jobs are tracked correctly.

Papercut Post Upgrade – Test it all works!

12 Feb

PaperCut is designed to support fully automated install-over-the-top upgrades. Normally no manual upgrade tasks need to be performed, however like all server-side applications, system administrators should devote some time to testing post upgrade. Administrators may find the following checklist useful. The test plan may equally be applied to new installs or server migrations.

The testing procedure is designed to take no longer than 15-minutes and encompasses operations in all critical areas of the application. It is advisable to print out this page (Printable View link is in the menu on the left) and check off the steps as the tests are performed.

  • Verify that administrators (e.g. the built-in admin user) can log into the interface at
  • View the About screen and ensure the expected version number is listed.
  • View general cost and system configuration settings and ensure that settings and data are still present after the upgrade:
    • User accounts are listed under the Users section
    • Shared Accounts listed under the Account section
    • Printer cost settings (if used)
    • Internet cost settings (if used)
    • Historical print and log data
  • Verify that end-users can log into the end-user web interface at http://servername:9191/user. e.g. use a test account to verify this.
  • Log into a workstation and ensure that the client starts as expected and list the current logged in user’s account balance (assuming you have deployed the client).
  • Perform a small manual adjustment on a test user account (Users -> [Select User] -> Adjustment & Charges). Ensure the adjustment is applied to the account balance and the user’s Recent Transactions as expected.
  • Print a print job under a test user account and confirm:
    • Print jobs list as expected under Printers -> Print Log
    • Ensure the job has charged the user as expected.
    • Ensure a corresponding transaction is listed under the user’s recent transactions list.
  • If users (or some users) are using the account selection popup to select and charge to shared accounts, perform some printing under an appropriate user account and ensure the popup is working as expected.
  • Check the App. Log (Application Event Log) section for any recent Warning or Error level messages.
  • If you have any PaperCut NG extensions installed (for example, custom web layout/design, extension modules, or integration with 3rd party systems), perform some tests and ensure these are working/displaying as expected.
  • Verify that you have a regular off-disk backup procedure in place and is continuing to backup as per your desired schedule.(editors note: every year we hear horror stories about how someone thought things were backing up. Now is a good time to check!)
  • If PaperCut is running on top of an external database system (e.g. Microsoft SQL Server, MySQL, etc.), verify that your off-disk backup procedure includes the host database.
  • Do you have any external equipment, scripts, resources? For example, scripts using the PaperCut API? If so, spend some time testing these external resources/services.
  • Take some time to explore and play with any new features! The release history page is a good place to start to gain a quick overview of what’s new. Also check out the known issues list for any important notes associated with this release. Generally print management software is pretty run-of-the-mill but we try and slip in an exciting feature in PaperCut from time to time!

Papercut MF Basics – Adding a new printer

27 Jan

add printer on windows server

under devices within papercut check and printer

On mac server add printer with same name

check queue output settings within the devices tab and make sure they are pointing to the right devices

Run cups script on mac server /MFPapercut