Configuring PaperCut Mobility Print behind a Network Load Balancer
A network load balancer helps to effectively spread the load of incoming requests across multiple servers sitting behind the load balancer. This provides two effective benefits when applied:
- This allows incoming requests to be easily split across multiple servers and allows a Systems Administrator an easy method to increase load capabilities simply by adding additional print servers.
- If one of the print servers fail behind a load balancer the users will be able to continue printing as the jobs will be redirected to the remaining active print servers.
In order for Mobility Print to work behind a network load balancer, you need to configure all the Mobility Print servers behind the load balancer to:
- Direct users to the address of the load balancer, instead of its own address.
- Configure each Mobility Print Server to use the same JSON Web Token (JWT) key, which is used to authenticate print jobs.
- Configure all the Mobility Print servers to host all the same print queues. Thankfully there are easy methods to migrate print queues from one Windows server to another, and this could be automated with scheduled tasks and PrintBRM.exe
- Obtain a copy of the
auth.jwt.keyfile from one of the Mobility Print servers. This file will be found in the
[Mobility Print install folder]\data\config\. It will be copied to all the other servers so they use this token as well.
- Then on each of the other Mobility Print servers perform these steps:
- Stop the Mobility Print Services on each Mobility Print server.
- Navigate to
[Mobility Print install folder]\data\config\and rename the auth.jwt.key file to auth.jwt.key_old.
- Copy auth.jwt.key from step 1 into the
[Mobility Print install folder]\data\config\folder on each Mobility Print server.
- In the same folder on each Mobility Print server open the file
dns.conf.tomlwith a text editor like Notepad.
- Edit the line
Accessible IP=“ ”to put the IP address of the Network Load Balancer in between the quotation marks.
- Save the file.
- Restart the Mobility Print Services on each Mobility Print server.
- Windows users may need to re-add Mobility Print queues to their workstations, as their tokens will now likely be invalid.
- Test. The clients should now be able to successfully deliver print jobs to all print servers behind the Network Load Balancer.
Keywords: Network, Load, Balancing, Balancer, F5, Citrix, Netscaler, Mobility Print