Skip to content

Choose your language

  • No results

Choose your login

  • No results
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

Help center

FAQs
Conversation bubbles

Contact us

Search

Configure PaperCut Print Deploy's Direct Print Monitor

This page applies to:

The Direct Print Monitor is a component of the Print Deploy client that tracks and controls direct printing - the print jobs that are sent directly to printers instead of servers.

The Direct Print Monitor sends information about print jobs to the Application Server. By default, the Direct Print Monitor is configured to send this information to the same Application Server that the Print Deploy server service is running on.

Changing the Application Server address

There are some cases where sending the Direct Print communication to a different Application Server address is more suitable:

  • For large environments where you need to split the Print Deploy printer and driver deployment load from the print, copy, scan, and fax load, point the Direct Print Monitor to a completely different Application Server.
  • If you have High Availability enabled or if you have multiple Active-Active Print Deploy servers behind a load balancer, point the Direct Print Monitor to a load balancer or front-end proxy, in front of the PaperCut Application Server.
  1. In the Print Deploy admin interface, click the Settings tab.
  2. In the Direct Print options section, change the Application Server address and Application Server port to the address and port you want to use.
  3. Click Save.

The next time Print Deploy clients call in for an update, the new Direct Print configuration will be applied.

Advanced Direct Print configuration

Modify the advanced config file on the server that’s in [app-directory]/providers/print-deploy/[os]/data/config/client.conf.toml.

This method requires restarting the Print Deploy service for the new config values to be applied.

  1. Open the client.conf.toml file using your favorite text editor and modify the values accordingly.
  2. Save the file.
  3. Restart the Print Deploy Server service . The new config values are applied.

Underneath [PrintProviderConfig], add the following key/value pairs (if missing) to control how the Direct Print monitor should communicate with the Application server.

Config keyDescriptionPossible valuesDefault valueAvailable in Settings tab
ApplicationServerApplicationServer indicates the hostname or IP address of the NG/MF Application Server that the Direct Print Monitor on a client machine calls. If the NG/MF Application Server is running on a different server from the Print Deploy Server, that hostname or IP address must be set instead.
 		A valid IPv4 IP address or a hostname.

Do not include the scheme and the port.		""Y
ApplicationServerPortApplicationServerPort indicates the NG/MF Application Server port number that Direct Print Monitor should use.

When TLS is set to true, then change ApplicationServerPort to use the Application Server HTTPS port instead, in most cases 9195.		A valid port address9191N
EnableRegisterPrintersWindows only

EnableRegisterPrinters instructs if the Direct Print Monitor registers all printers and retrieves all printers' settings at service startup or refresh. If this is set to false, no immediate printer registration and printer settings retrieval happens. Instead, these requests are made on a per-printer basis when a print job to a printer is submitted for the first time after startup or refresh.
 		true/falsetrueN
ServerNameServerName indicates a hostname that the Direct Print Monitor on a client machine reports to the NG/MF Application Server.
 		ServerName should be limited to 15 characters or less, and should only contain alphabetic characters (A-Z), numeric characters (0-9) or the minus sign (-)"pd-client"N
TLSMinProtocolVersionSpecify the minimum TLS version that the Print Provider uses.
 		"TLSv1.0"
"TLSv1.1"
"TLSv1.2"
"TLSv1.3"		TLSv1.2
To configure the Print Provider, to use a minimum of TLS 1.3 you must first “enable strong defaults” in the PaperCut NG/MF Application server as described here: SSL Cipher Configuration - removing weak ciphers.		N
TLSMaxProtocolVersionSpecify the maximum TLS version that the Print Provider uses.
 		"TLSv1.0"
"TLSv1.1"
"TLSv1.2"
"TLSv1.3"		TLSv1.2
To configure the Print Provider, to use a maximum of TLS 1.3 you must first “enable strong defaults” in the PaperCut NG/MF Application server as described here: SSL Cipher Configuration - removing weak ciphers.		N
TLSSpecify whether to use HTTPS or not. If true is set, the Direct Print Monitor uses HTTPS to communicate with the Application Server on the port configured via ApplicationServerPort. It is recommended to use ApplicationServerPort=9195 when enabling TLS.true/falsefalseN
TLSVerifyCertificateSpecify whether the Print Provider verifies the PaperCut NG/MF Application Server's HTTPS certificate. By default, the Application Server uses a self-signed certificate. If certificate verification is enabled, the Application Server must be using a trusted certificate.

More details available here:

https://www.papercut.com/help/manuals/ng-mf/common/tools-ssl-key-generation-certificate-authority/		true/falsefalseN

Comments