Papercut Server 2012 R2 > 2019

[DalekSec]

Hi All,

 

We've had it on our job list for awhile (well 2 years now...) to upgrade our Printing Server from 2012 R2 to 2019 (too soon for 2022). Has anyone done this? or any tips? Normally when we do server replacements we do a fresh install but seeing as we have many printers, print deploy, universal print, mobility print etc. all setup I'm not so sure my heart could take it! Papercut are good and have a guide on how to move them all across but it's a lot of work and I hope that doing a upgrade straight to 2019 will be a lot less stressful!

[FN-GM]

Print servers are one of the easier servers to

Migrate.

 

Backup and export all your printers form

The old server.

 

-Backup papercut.

-Build a new server with the same name.

-Restore printers from export

-Install and restore papercut backup.

 

 

Just make sure Papercut is the same version on old and new.

[Michael]

So long as you have a valid license, you may as well upgrade to Papercut v21 (at the time of writing) on your existing print server and new print server.

[DalekSec]

Print servers are one of the easier servers to

Migrate.

 

Backup and export all your printers form

The old server.

 

-Backup papercut.

-Build a new server with the same name.

-Restore printers from export

-Install and restore papercut backup.

 

 

Just make sure Papercut is the same version on old and new.

 

The main PC server is that easy yes, but with all the extensions its a bit more work! https://www.papercut.com/kb/Main/ServerMigration

 

So long as you have a valid license, you may as well upgrade to Papercut v21 (at the time of writing) on your existing print server and new print server.

 

Already on the latest version

[Michael]

The only other consideration is the same IP/same hostname as your existing print server, otherwise you'll have to update the MFPs themselves.

 

If it's a VM, you could always take a snapshot and upgrade Windows Server. I can't see why it wouldn't work myself and save a lot of work.

[Squelch]

 

If it's a VM, you could always take a snapshot and upgrade Windows Server. I can't see why it wouldn't work myself and save a lot of work.

 

I did exactly that with no issues, I just mounted the image, ran setup.exe, sacrificed a few children and it all ended well.

[DalekSec]

I did exactly that with no issues, I just mounted the image, ran setup.exe, sacrificed a few children and it all ended well.

 

What age of children we talking? We're a secondary but do have a sister prep school if I need to send for younger ones. Not willing to sacrifice too many, being a private school they are paying my wages after all!

[gotenks1321]

I did exactly that with no issues, I just mounted the image, ran setup.exe, sacrificed a few children and it all ended well.

 

Ditto, did exactly that over the summer here with no issues. We were already running the latest version of PaperCut so I suspect that helped things a little although our database is on a separate SQL server which was also upgraded afterwards.

[k-strider]

yes i have too... 2012R2 to 2016 then more recently to 2019.... just waiting for Papercut to officially support 2022 then up we go again! no problems at all with papercut

[MatthewL]

If you are upgrading PaperCut make sure both servers are the same PaperCut version when restoring the backup, either do an upgrade before you migrate or install the old PaperCut on your new server, restore then upgrade. Be good to upgrade the old server and check you have no issues first in my eyes.

[Squelch]

What age of children we talking?

 

I picked the most annoying of each year group, pretty sure they weren't missed afterwards (we have from reception to Y12).

[KK20]

VM here. Made sure I had a veeam image, then snapshot and did an inplace upgrade. Ive inplace upgraded ALL of our servers except DC (I promote a temporary, leave to sync, demote the old, leave to sync, inplace upgrade then promote and demote temporary), and I have never inplace upgraded exchange (that would be horrible and seriously unsupported). Hyper-v server is not supported to inplace upgrade neither.

 

Never had an issue in all my years so far. In fact, the "profile and document storage" server started life as a physical 2003 machine and was P2V then upgraded over the years to 2019.

 

Make sure you have a good backup first.

[CrootUK]

Recently done this, no issues.

As always ensure backups are good, take a snapshot.

Edited November 5, 2021 by CrootUK