Tag Archives: Papercut

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!

iOS 9 – Unable to Print via Papercut

19 Oct

What has changed in IOS9?

iOS9 shifts the way iOS devices have traditionally talked on a network by using IPv6 communication:
→Lots of hexadecimal numbers with colons in-between fe80::xxxx:xxxx:xxxx:b71d
if available before it uses IPv4 communication:
→The pattern of 4 of decimal numbers we have come to know 10.xxx.xxx.xxx

This includes IPv6 Link Local addresses if it possibly can, provided the infrastructure can support them.

So how does this affect PaperCut?

PaperCut uses one of the few constant things known about an iOS device, it’s IP address, to link jobs to users.
On an iOS 9 device, printed jobs present from the IPv6 address. However when logging on to the PaperCut app, the address presented is an IPv4 one, and we do not make the connection.
In many existing set-ups, this may not be a problem, as IPv6 may not be supported or the device may be iOS 8 or older, so we will only ever see an IPv4 address.
However if after upgrading to iOS9 you find that users report their jobs not showing up in the print queues to be released, you may find that iOS9 has found a way to use IPv6 on the network.

How do I get my devices printing again?

In most networks, we have found that turning off IPv6 will work around the issue, and restore the ability to print.
This is a relatively simple process that you only have to do on the interface the Mac uses to talk to the iOS devices. In the majority installations this is the Ethernet adapter on the Mac mini.

To disable IPv6on the Ethernet port:

There is no GUI option to disable IPv6, it must be done from a terminal session.
1. Launch Terminal
2. Type the following command:

networksetup -setv6off Ethernet

or for WiFi? is you use it

networksetup -setv6off wi-fi

3. Go to the system settings and verify the command has worked, you should be able to see an extra menu item called “off” with a tick against it.

“I still can not print” or “I need IPv6 on for my network”

If you can not disable IPv6 for any reason, support may have alternative workarounds that should allow iOS9 devices to print in your environment, please contact us for more information.