Upgrading the OS of your PaperCut Server
Like a high-quality dentist, an operating system upgrade should be a pretty painless procedure. Here’s hoping!
NOTE: As you may have heard PaperCut dropped 32-bit server support back in March 2018 so if you are running PaperCut version 18.0.3 or above and planning to upgrade, you will need to ensure your server OS is 64-bit. You can find more details here.
Here are the recommended steps when performing an in-place OS upgrade:
Whenever making any significant changes to your PaperCut server, it's always a good idea to have a backup available just in case something goes awry. The best way to do this is to create a full-system backup using your organization's preferred 3rd party backup software. Use that to save a snapshot that to include a file-system level backup of everything under your PaperCut installation directory (typically
C:\Program Files\PaperCut NG/MF for Windows or
/Applications/PaperCut NG/MF for macOS).
If thatís not an option, you also can use PaperCutís built-in backup system to make a quick copy of your database, which can be restored in the case of an emergency. If you are running the internal PaperCut database, our backup article - covers all the required steps to perform a database export of PaperCut as a contingency. If you are using an external Microsoft SQL Database, you can backup the database at the Microsoft SQL level.
For Windows servers, we also recommend backing up your print queues too. You can get the low-down on that right here.
- Perform your in-place upgrade as per instructions relevant to your individual server OS.
- Confirm that the OS is working as expected post-upgrade and that you are still able to print to the existing print queues as normal.
NOTE: After completing your upgrade, there a couple of items worth noting, specifically for Windows Server systems:
- If you have enabled PrintService/Operational logs on your server, these will be removed upon upgrading. You can save these if you wish. Once the upgrade is complete, you can follow the steps here to re-enable logging.
- We recommend enforcing Client Side Rendering using the
Set-Printer * -RenderingMode CSRPowerShell command. This will ensure that Windows client machines are in the correct state post-upgrade since the client will honor the server setting. We also mention this method in our Client-Side Rendering article.
Then, without restarting the server, perform an over-the-top installation of PaperCut using the same version of your original installer file. This is also a good time to update the drivers for your print queues to ensure that there arenít any unintended implications with using the old versions. If itís been a good while between installations, you can follow along with our quick install guides.
Thereís no substitute for good testing! Confirm that PaperCut is running, your settings and job logs are visible, and if you are running PaperCut MF, that your devices have reconnected successfully. See our post upgrade article for a checklist.
In the event that PaperCut no longer functions correctly post-upgrade, we suggest completely uninstalling PaperCut from the server and then reinstalling it from scratch. Restoring your database should bring everything back successfully.
Still have questions?
Let us know! We love chatting about whatís going on under the hood. Feel free to leave a comment below or visit our https://support.papercut.com/ for further assistance.
Keywords: upgrade, upgrading, OS, operating system, server