![]() 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. Go straight for it! PaperCut is designed to support “install over the top” upgrades from any version to any newer version. 16.x to 19.x or do I need to go for staggered upgrades? 17.x or 18.x, through to a newer one like 20.x).Ĭan I upgrade straight from e.g. How do I make sure that I’m eligible for the upgrade?Ĭheck 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. 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. Yes! When you perform the upgrade, all your job history, transaction data, balances, configuration and other information is all kept in place. Please some take time to review the Upgrade policy before proceeding.Īre my job logs / job data / user balances / transaction history and printing history kept when performing an upgrade? If your Maintenance and Support is not current, there may be an upgrade cost for major upgrades. Note: The exception to this rule is Site Servers (see below - these have to be upgraded at the same time as the Application Server). Should you request support for a problem where mismatched component versions is detected, this will be the first troubleshooting step. If you encounter unexpected behaviour or problems, please upgrade all components of PaperCut as soon as possible before troubleshooting further. 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. 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 in most cases this isn’t critical. 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. Secondary Server, release station, web print server and user client upgrades Note: Sites running on Microsoft Cluster servers should consult the documentation in Upgrading PaperCut NG in a Microsoft Cluster Environment. Please follow the steps listed in the Installing PaperCut NG/MF section of the help center, for installation instructions for each operating system.′ ![]() You just need to install the latest version “over the top”. Note: Upgrading instructions are the same for Linux, macOS, Windows and Novell. 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. Please note that customer self-service upgrades are only recommended for server and workstation components. PaperCut MF - If you have PaperCut MF then you can obtain the installation software from your PaperCut Authorised Reseller (find them listed on the ‘About’ tab in the PaperCut Administration Console, under the ‘Support’ section), or via the Check for Updates option found on the About tab of your PaperCut administration console.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |