Configure Mobility Print behind a Network Load Balancer

A Network Load Balancer helps to effectively spread the load of incoming print requests across all print servers that sit behind the load balancer. This provides two benefits:

  • Benefit 1: SysAdmins can easily increase load capabilities simply by adding print servers.

  • Benefit 2: If one of the print servers behind a load balancer fails, users can still print because their print jobs are redirected to the remaining active print servers.

For Mobility Print to work behind a Network Load Balancer, you need to configure all of the Mobility Print servers behind the load balancer to:

  • use the same JSON Web Token (JWT) key to encrypt user identities

  • direct users to the address of the load balancer instead of its own address.

To configure the Mobility Print servers:

  1. Stop the Mobility Print services on all the print servers that have Mobility Print installed.

  2. Go to the Mobility Print install folder for one of the backend servers [Mobility Print install folder]\data\config and make a copy of the auth.jwt.key file.

  3. Repeat these steps on all Mobility Print servers in use:

    1. Rename the auth.jwt.key file to auth.jwt.key_old

    2. Copy the file obtained from step 2 into the data\config folder.

    3. In the same folder, open the dns.conf.toml file with Notepad.

    4. Find the entry Accessible IP=" "

    5. Between the quotation marks, type the IP address of the Network Load Balancer.

    6. Save the file.

  4. Restart the Mobility Print services on all Mobility Print servers.

  5. Ask the users to remap their Windows Mobility Print queues, because their tokens will now likely be invalid.

  6. Test. The clients should be able to successfully deliver print jobs to all print servers behind the Network Load Balancer.

For more information, check out the Network Load Balancing page.