Choose your language

Choose your login

Support

How can we help?

Lightbulb icon
Lightbulb icon

Here’s your answer

Sources:

Lightbulb icon

Oops!

We currently don’t have an answer for this and our teams are working on resolving the issue. If you still need help,
User reading a resource

Popular resources

Conversation bubbles

Contact us

Multiple Application Server Licensing

THE PAGE APPLIES TO:

We often get asked the question, “Am I allowed to run PaperCut NG/MF on multiple servers?” The short answer is, “yes you can, with a few conditions.”

How can my license be used?

When you purchase a license for PaperCut NG / MF you have the right to install the software into your environment. This installation may consist of a single print server or multiple print servers in your network. The license entitles you to install one Application server into your production environment with either multiple sites servers, multiple secondary servers, and/or multiple direct print clients.

The above scenario works for a large proportion of our customers, with all management and control of their print environment being managed through a single Application server and controlling printing across the entire organization.

Prior to PaperCut NG/MF 24.0, you could also use this same license to install a second PaperCut Application server into your testing environment for validation purposes. However, since PaperCut NG/MF version 24.0, be aware that entitlements (such as the number of purchased devices etc) will be shared between any Application Servers with the same license and CRN (Customer Reference Number). See Important points to know about PaperCut MF licensing (Global set of entitlements) for more information.

Can I use my license or subscription to run a separate PaperCut Application server at multiple sites?

There are some occasions where the ‘one Application Server’ model does not suit all customers. Generally, in these cases, we would expect that if multiple Application servers are to be run in your organization, you would purchase a license or subscription for each new Application server install, or ensure that your single license/subscription covers all entitlements across all sites. This would be valid in cases where you have split IT management of the different sites, and each location runs as a separate entity.

For example: ‘Company X’ operates in Australia, Singapore, and the USA. Whilst it is a single organization each location is maintained separately with a local I.T. team managing the hardware, software, and networks independently. In this scenario the options are:

  • the organization purchases multiple licenses / multiple subscriptions. One license for Australia that covers the entitlements and MFDs in Australia, a separate license for Singapore that covers the entitlements and MFDs in Singapore, and another separate license for USA, that covers the entitlements and MFDs in the USA. In this case, each site would effectively have its own CRN (Customer Reference Number) e.g. Corp USA, Corp Australia, and Corp Singapore.
  • the organisation purchases a single license / single subscription. The single license or subscription covers the total entitlements needed by all 3 regions, and those entitlements are then shared and consumed by the regions. This option requires more co-ordination between regions, since the IT admin in Australia could add 3 more devices than agreed, and it could stop one of the other regions from adding further devices since it’s a single shared pool of entitlements.

See Important points to know about PaperCut NG/MF licensing (Global set of entitlements) for more information.

Can I use my license or subscription in a cluster?

PaperCut NG and MF can support clustering through multiple methods. PaperCut is licensed on a domain/site wide basis and the one license will cover all servers, including multiple nodes inside a cluster. There is no need to purchase a separate license for each node.

In a cluster environment, the Application Server component is often installed on two or more nodes to provide a degree of redundancy and load distribution. The license needs to be installed on each node.

See Clustering and high availability for more detailed information on setting up clustering with PaperCut NG/MF.

PaperCut NG/MF version 24.x and later

If you are using non-PaperCut methods of clustering

For example using Microsoft Cluster Server , Hyper-V or other solutions.

  1. Install the license or activate your subscription on the currently active node.
  2. Copy the server.uuid file (e.g. in C:\Program Files\PaperCut MF\server\server.uuid) from the currently active node, over to the same location on the other node(s). See Step 4 (under Mode 2) in the manual for more information.

Activating / installing on the other node is not required since you’ve already performed this step, and the other node(s) will check in and get their status from the Global Entitlements Service when they become active.

If you are using the PaperCut Application Server Failover feature:

For example using the built-in PaperCut Application Server Failover feature.

Ensure that you are using PaperCut NG/MF version 24.0.5 or later (which resolves Known Issue PO-2220 ).

  1. Install the license or activate your subscription on the currently active node.
  2. No further steps required (you should not copy the server.uuid file in this setup)

Activating / installing on the other node is not required since you’ve already performed this step, and the other node(s) will check in and get their status from the Global Entitlements Service when they become active.

PaperCut NG/MF version 23.x and earlier

(Applies to all methods of clustering and failover)

Option 1 - Manual copy
  1. Install the license as explained in the user guide.
  2. Manually copy the application.license file, e.g C:\Program Files\PaperCut MF\server\application.license from the currently active node and copy across to the same location on other node(s). This file contains the digitally signed license and its presence will license all nodes.
Option 2 - Simulated node failure
  1. Install the license as explained in the user guide. This will license the currently active node.
  2. Simulate node failure so the other node becomes active. Wait a few seconds for the other node to activate, and then repeat the procedure on this node.


Categories: SalesAndLicensing


Keywords: Enterprise , Multiple sites

Comments

Last updated November 22, 2024