Advanced configurations

What are advanced configurations?

There are many configuration settings available in PaperCut Hive and Pocket. The advanced configurations section in the Admin console is for complex, organization-wide changes.

Most organizations won’t need to change these settings — but changes might occasionally be required for organizations with very specific requirements. That said, most organizations should consider their Job storage location setting, and update it to “Same network” if preferred, as this is the recommendation. PaperCut highly recommends that you discuss any configuration changes with your PaperCut Authorised Partner before proceeding.

How to access advanced configuration settings in PaperCut Hive and Pocket

Advanced configuration can be found in the PaperCut Hive or Pocket Admin console. To access advanced configuration:

1. Log in to your PaperCut Hive or Pocket Admin console.
2. Select your logged in user in the top right corner of the Admin console. A drop down menu is displayed.
3. Select Settings.
4. Select the Advanced tab.
5. The Advanced configurations option is displayed. Click the Configure button.

Keep reading to learn more about the various advanced configuration settings, including why and when you might want to change them.

Find-Me replication and storage advanced configuration settings

Find-Me replication and storage settings change to how print job copies are created, encrypted, and stored on user clients throughout your entire organization. Let’s go through them in detail.

Print job replication

About the Print job replication setting

When a user prints a job via PaperCut Hive or Pocket on a Windows or Mac device, the print job will be encrypted and securely replicated to other devices based on this setting. The number selected in this in the Print job replication setting is how many times the print job is replicated, and by default a print job is replicated two times in addition to the original print job. The PaperCut client software replicates to others via port 9264.

Print job replication is done to offer redundancy for when the job is released at a printer. For example, if the print job was only stored on the device of the user who printed the job initially, and that person turns their device off, the job will fail to print if the user releases the job. However if the print job also replicated to at least one other device that is online, PaperCut could route the job via this computer, allowing the user to successfully complete their printing. As such, increasing the amount a print job is replicated and stored on clients in your organization also increases the likelihood of successful printing.

Why organizations might change the Print job replication setting

There are a number of scenarios where organizations might like to change or disable replication of print jobs, including:

1. Users are primarily in satellite offices that have network bandwidth limitations. Therefore they do not want the client reaching out to other clients and transferring data, so decide to turn off print job replication.
2. An organization has a lot of clients, and are concerned that too many replication clients could cause excessive network traffic, however they still want the redundancy. In this scenario they may lower the replication count.
3. The site does not allow devices to communicate with other devices on the network. Changing this print job replication to zero will prevent the PaperCut client software from attempting to reach out to other devices for replication.
4. No user device has the ability to reach the printers, so print jobs MUST replicate to the Cloud Node, and be replicated to a dedicated client in the printer’s network. To achieve this, the organization can turn off print job replication.

Job storage location

About the Job storage location setting

If ‘Print job replication’ is set to a number higher than zero, this setting determines the network where the user’s device will attempt to replicate the print job to. The two options available are:

1. Any network (legacy) — this is the default option
2. Same network (recommended)

Why organizations might change the Job storage location setting

We generally recommend that organizations select “Same network” for the Job storage location setting. Here’s why: if your organization has a WAN, selecting “Same network” for the Job storage location can prevent jobs from being replicated across it. This can reduce unnecessary network traffic, because if the replication port (Port 9264) is open on the WAN, the device replicating the job will likely attempt to replicate across the WAN, instead of keeping it in the local network.

The “Same network” option is a new addition, which is why it is currently not the default. This may change in the future, as selecting “Same network” is generally recommended.

Find-Me print release advanced configuration settings

The Find-Me print release advanced configuration settings relate to the delivery of a print job to the printer. This includes how jobs are delivered to, and released from the printers. They may change the speed or reliability of the job.

Enforce print release order

About the Enforce print release order setting

The Enforce print release order setting is only relevant when a user releases a batch of jobs in one go (such as pressing the ‘Print All’ option on the MFD embedded touchscreen). PaperCut will send these jobs sequentially, so that the first job in the list is printed first, etc.

If Enforce print release order is enabled, the system will wait for confirmation the previous job was completed before routing the next job. If Enforce print release order is disabled (the default setting), the system will route the next job as soon as it receives confirmation that the previous job is printing. Even when Enforce print release order is disabled, PaperCut Hive and Pocket will attempt to maintain job order.

Why organizations might change the Enforce print release order setting

In most circumstances, even when Enforce print release order is disabled, PaperCut Hive or Pocket will still maintain the print job order successfully. However if you are finding jobs are not staying in order — and specific print order is a requirement at your organization — then enabling Enforce print release order will ensure that print jobs are printed in the same order they were submitted. This may come at a small speed penalty between jobs, but generally enabling this setting makes minimal speed difference, in particular if job delivery is done via Port 9100.

Port 9100 printer checks

About the Port 9100 printer checks setting

When a print job is released, potential delivery clients are asked to check they can successfully connect to the printer before they accept the task of delivering the print job. This connectivity check is normally done via connecting to the printer via IPP (using Ports 80/443/631, depending on the printer). The Port 9100 printer checks setting allows you to require PaperCut Hive or Pocket to only use Port 9100 for these printer checks.

Why organizations might change the Port 9100 printer checks setting

Some printers respond better to IPP requests than others. If your organization’s printers aren’t responding well to IPP printer check requests, you might discover the following error in print jobs that have been released but failed: printercheck.unreachable.cmdexecutiontimeout

In this situation, you might want to use Port 9100 to do printer checks, and enable the Port 9100 printer checks setting. Printers often respond better to requests via Port 9100, because it is a more mature printing port. Please confirm that port 9100 is open on your internal network between your PaperCut client devices and the printers, otherwise this will fail. If this setting is enabled and the printer check is performed by 9100 and fails, the following error is displayed in the Job Trace.: printercheck.unreachable.9100ping. In this instance, you should further investigate network connectivity between clients and printers.