Upgrading PaperCut MF & NG (upgrade procedure)
Last modified on 10 August 2020 04:28 PM
This article covers the steps needed to upgrade PaperCut MF or NG. There’s a couple of related articles which may be of help too:
Check out the FAQs further down the page, which cover questions around whether you can ‘jump’ from one version to another without doing the upgrades in between, or whether all your data is retained after an upgrade before beginning the upgrade process.
If you’re using PaperCut MF: please contact your PaperCut support partner (located on the ‘About’ tab in the PaperCut administration console, under the ‘Support’ section) to let them know about the upgrade so that they can assist with licensing, device and other upgrade advice - and can also then be available in the unusual event that something goes wrong.
Getting hold of the latest version of the software:
If you are migrating from PaperCut NG to PaperCut MF, then please contact your PaperCut Authorised Reseller for support, since there will be licensing changes needed, and device-specific steps will need to be completed to get your devices working with PaperCut MF.
Note: Upgrading instructions are the same for Linux, macOS, Windows and Novell. You just need to install the latest version “over the top”. Please follow the steps listed in the Installing PaperCut NG/MF section of the help center, for installation instructions for each operating system.′
Note: Sites running on Microsoft Cluster servers should consult the documentation in Upgrading PaperCut NG in a Microsoft Cluster Environment.
The upgrade procedure:
It’s highly recommended that any ‘other’ components (secondary servers, release stations, user clients, sandbox web servers) are also upgraded at the same time as the Application Server. However in most cases this isn’t critical. We make sure that there is basic backward compatibility for secondary servers, user clients, devices, release stations, web print servers etc - this allows upgrades involving a large number of servers, or multiple sites, to be staggered, breaking up and localising downtime. However you will likely not be able to take advantage of all the component-specific new features until those components are upgraded (for example if there is a new feature with a release station or user client, then there is a high chance that the release station or user client would need to be upgraded to make the most of that new feature.
If you encounter unexpected behaviour or problems, please upgrade all components of PaperCut as soon as possible before troubleshooting further. Should you request support for a problem where mismatched component versions is detected, this will be the first troubleshooting step.
Note: The exception to this rule is Site Servers (see below - these have to be upgraded at the same time as the Application Server).
Secondary Server upgrade
As with the Application Server, this is just a matter of installing the latest version ‘over the top’ of the current version on the Secondary Server. It’s the same process as Installing a Secondary Server, but all your previous configurations and log files will be retained during the upgrade, so you don’t have to re-apply any configuration again after the upgrade.
If you’re wondering how to get the software, check out this article on Getting the Secondary Server Software. If you have just done the Application server upgrade above, you already have the installer that you need to do the upgrade on the secondary server too.
If you’re using Linux, it’s also worth checking out the Linux Secondary Server upgrade article.
Release Station upgrade
Depending on how you have Installed your release station you may either have to do nothing (yay!) if you are running the release station software directly from the release station share on the Application Server, or, you may have to copy the latest release folder (under [app-dir]/release) from the Application Server to the Release station - as documented in the installation instructions.
If you are copying the entire folder over and running the release station locally, it’s worth taking a backup of the following files, and restoring them after the directory copy, so that you retain all your previous settings:
Web Print Sandbox server upgrade
Again, just like the Application Server upgrade or Secondary Server upgrade, for the Web Print Sandbox Server upgrade you just need to run the PaperCut NG/MF installation package and then follow the Web Print Sandbox Server install directions, to install over the top of your current install on the Sandbox Server - make sure to select ‘Web Print server installation (sandbox mode)’ when running the installer for the Web Print Sandbox Server!
Note that if you’re running Web Print in Default mode, then the upgrade was already taken care of as part of the Application Server upgrade.
User client upgrade
Check out our separate article on Upgrading the PaperCut client software.
Download the latest version of the gateway from the Payment Gateway Setup and Installation page (Step 2), and perform the upgrade just like the original installation.
It’s also worth taking a backup of the config files for the gateway that you’re using, so that you can copy these back into place after the re-installation:
PaperCut MF users should now follow any upgrade instructions outlined in the embedded solution documentation for their devices. Your PaperCut partner/reseller will also be able to provide an appropriate resource to assist with this procedure - their contact details can be found in the PaperCut Administration Console, under the ‘About’ → ‘Support’ section.
Site servers should now be upgraded to the same version as the primary server (see the Site Server Installation section of the help center for instructions).
Until they are upgraded, any site servers associated with the primary server will continue to run in offline mode, with reduced functionality (see the Site server offline section of the help center for more information about what functions are available or not.
If you’re interested in a video of the upgrade process, the following runs through an Application Server upgrade of PaperCut NG/MF:
Do I need to pay for the upgrade?
Minor releases upgrades are always free. If your Maintenance and Support is not current, there may be an upgrade cost for major upgrades. Please some take time to review the Upgrade policy before proceeding.
Are my job logs / job data / user balances / transaction history and printing history kept when performing an upgrade?
Yes! When you perform the upgrade, all your job history, transaction data, balances, configuration and other information is all kept in place. You’ll be able to perform the upgrade, and after the upgrade still see job history from previous months/years, and all your users will have the same balances as just prior to the upgrade.
How do I make sure that I’m eligible for the upgrade?
Check out the Upgrade Policy documentation to make sure that you’re ok to upgrade - especially if you’re moving from an older version (e.g. 17.x or 18.x, through to a newer one like 20.x).
Can I upgrade straight from e.g. 16.x to 19.x or do I need to go for staggered upgrades?
Go straight for it! PaperCut is designed to support “install over the top” upgrades from any version to any newer version.
However, from a best practices point of view, if you’re on quite an old version (say v12 and before) and are looking to move straight up to our latest version, you would be better off minimising the risk of the upgrading accidentally failing by staggering your updates. The best judge of this is check whether there’s been a large number of database schema changes or features implemented between versions. If it seems like a lot we would recommend a staggered upgrade approach, e.g. v15 → v17→ v19. Obviously, a easy way to mitigate this risk is by taking a backup of your server or PaperCut install beforehand.
For significant jumps between versions, we also recommend optimizing your database beforehand.
If you need help accessing interim release versions of PaperCut for a staggered upgrade, as a MF customer, you will need to contact your PaperCut Reseller. As a NG customer, you can download old versions of PaperCut NG.
Do I need to upgrade my server before upgrading PaperCut NG/MF?
Please look at our server sizing guide to make sure that your system can perform adequately when supporting the newer features in current versions of PaperCut NG/MF.
Will my 32-bit servers and workstations still work?
PaperCut has stopped support for 32-bit operating systems since version 19.0, so there may be additional work required in your environment if you still need to support 32-bit clients. Check out our article on End of life for 32-bit operating systems for more information.
Are there any known issues that I should know about before upgrading?
It’s worth checking out the latest information on PaperCut NG/MF Known Issues to make sure you know what to expect with the new version.
Where can I get the latest update from?
In the PaperCut admin console, head over to the
Can I upgrade the Application Server but keep the clients and secondary servers on a previous version?
The PaperCut Application Server is designed to be backwards compatible, so you can have a newer version of the Application Server being used with older versions of the Secondary Servers, Release Stations, and Clients for the purposes of the upgrade (note, Site Servers are not on this list). However, we highly recommend upgrading those other components to match the primary Application Server as soon as possible, so that you gain the benefits of upgrading all the components in your environment.
You cannot have an older version of the Application Server being used with a newer version of the Secondary Server, Release Station, or Client software.
Is the same true for Site Servers?
If you have Site Servers, they must be maintained at the same version as your Application Server. Site Servers have an especially close relationship with the Application Server and it is not possible to support older versions of the Site Server. When your Application Server is upgraded, your Site Servers will operate in offline mode until they are also upgraded.
What will happen if someone tries to print while the upgrade is in process?
The PaperCut Print Provider service will be stopped during the installation, but the print spooler service will continue to process print jobs allowing printing to continue without PaperCut control. The Print Provider service will be restarted automatically at the end of the upgrade. We recommend that you perform the upgrade during a period of minimal print activity on the network.
How long will the upgrade take?
The answer is ‘it depends’… mostly on how much data you have in your database. The actual upgrade of the binaries and other config files is relatively quick (under 5–10 mins) but it’s worth looking through the Database upgrades KB to see how to (very roughly) estimate an upgrade duration for your environment. If you really want to know for sure, there’s no better way than creating a PaperCut test environment to try out the upgrade.
I’m a PaperCut Chargeback customer, how do I move up to PaperCut NG?
Check out this KB on Upgrading Chargeback.