papercut migration to new server

[janaps]

Hi

We are planning to move our papercut from an old fysical server to an azure vm. We don't want do to a pure physical to virtual migration because we don't trust the config on the old server. So I'm reading this https://www.papercut.com/kb/Main/ServerMigration#3-copy-the-license-file-to-the-new-server.

I wonder if anyone has any experience with this: will the old server keep on functioning if we copy the license file to the new one?

Thx

[MatthewL]

My advice would be when doing any server migration, get PaperCut tidy and how you want it, any print queues that are redundant get rid and remove the old drivers, run PaperCut update so its on latest version. Next run a backup of PaperCut and take a copy of that, also in Print Management backup the queues to a file which you can then restore it saves the work.

 

Next restore your printer backup and then install the same version of PaperCut on new server then restoring your database (check the KB for the commands on this).

 

If you dont trust the config install from scratch but as you already have a working version tidy and sort that out saves the headache for starting from scratch. The backup will restore the license file at the same time.

 

I've migrated hundreds of print servers and its easier to do it that way to save you time. Spend the time to get the config right it will work in your benefit.

[janaps]

Thank you for your reply. In normal circumstances I would do what you suggest, but in this case starting from scratch would be the way to go I'am afraid.

 

Do you, or anyone else have any experience with the license? Does it still work in the old server if you do what is described in the link to the papercut website (https://www.papercut.com/kb/Main/ServerMigration#3-copy-the-license-file-to-the-new-server). Can we operate the two installs for some time, or is this more a cutovermigration?

Thx

[Jaan]

Can the license provider not issue a temp license file for the new server until the old is downed? then transfer the license file?

 

We had an issue here where we have to spin up a new print-server vm and config it whilst our old one was online. We got a temp licence for 30 days iirc

[PotNoodleTech]

Oops - I went through Ricoh my MFD supplier and they did a lot of the donkey work. Edited December 7, 2022 by PotNoodleTech

[janaps]

Thx, maybe contacting ricoh is the way to go (the papercut install is linked to their secure print solution)

Many thanks for the replies

[tg12]

The PaperCut license activates fine on a second server, I did it during the migration of my PaperCut server over the summer and did many other migrations for other schools in my previous job doing the same.

[jonnykewell1]

I've done numerous Papercut server migrations and the advice that @MatthewL has given is spot on. I have found the Papercut documentation to be solid too.

[MatthewL]

The license would still work but the reconfig of all devices i.e. the copiers would be where you would potentially run into issues unless you are farmillar with what needs doing on them. I dont know Ricoh devices but Sharp its easy to sort, not sure if Ricoh is just a case of web on and change the IP.3

 

My advice would still stand and if possible, although doesn't sound it this time do above then give the new server the same IP as the old if possible then devices don't need reconfiguring.

 

A fresh start with PaperCut unless you are clused up in PaperCut I would not recommend, there is a lot of work when it comes to some devices.

 

You can run 2 instances side by side or you could, I know PaperCut now talks back for licensing so it may detect that.