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

System requirements

This page applies to:

For PaperCut NG/MF system requirements, see PaperCut NG system requirements or PaperCut MF system requirements .

Printers and drivers

Print Deploy works with the vast majority of printers. This includes, but is not limited to, print languages such as PostScript, PCL5, PCL5e, PCL6, XPS, Epson ESC/P2, Canon UFR, UFRII and more.

Windows

The following driver requirements must be met before Print Deploy will clone the print queue:

  • The driver must have an INF file (Setup Information file).
  • The driver must be package-aware and digitally signed with a trusted certificate, preferably by Microsoft. If the certificate is provided by a third-party vendor, it must be preinstalled on all of the clients.
  • The driver is not a virtual driver like a PDF printer. In other words, the print queue has to point to a physical device or in the case of a Direct Print Find-Me setup, to a local nul-port.

macOS

When Cloning Printers on a macOS machine the otool command line tool is required. macOS should prompt to install this when the Print Deploy Cloner is run.

macOS Screenshot: The otool command requires the command line developer tools. Would you like to install now?

macOS printer drivers may need ‘otool’ in order to be cloned

Linux

Print Deploy requires that Common Unix Printing System (CUPS) is installed before the Print Deploy Client is deployed.

Client requirements

  • Windows 11, Windows 10 (64-bit and Arm64)
  • macOS 11+ (Big Sur) 64-bit
  • Chromebooks
  • Linux 64-bit (Modern .rpm & .deb based distributions)

Firewall rules

For an up-to-date list of PaperCut NG/MF and PaperCut Mobility Print firewall ports, see the Firewall Ports used by NG/MF knowledge base article.

The following ports must be open for the end-user client to be able to communicate with the Application Server:

On the client

  • 9174 (HTTPS) outbound TCP port to Application Server
  • 9164 (HTTPS) outbound TCP port to the Mobility Print server - applicable only if you are deploying Mobility Print queues
  • (Chromebooks only) 9173 (HTTP) outbound TCP port to Application Server. This is only used when the Print Deploy server is not using a CA-signed certificate. Otherwise, it uses 9174 (HTTPS).
  • 9175 and 9176 (HTTP) TCP to localhost — only applicable if third party firewalls are active on the client computer.
  • 9177 (HTTP) TCP to localhost — only applicable if you are deploying Mobility Print queues
  • 9191 (HTTP), 9192 and 9195 (HTTPS) outbound TCP port to Application Server — only applicable if you’re deploying direct print queues, so the Direct Print Monitor on the user’s computer can talk to the Application Server.

On the Application Server

Inbound:

  • 9174 (HTTPS) TCP port for Print Deploy clients
  • 9173 (HTTP) TCP port to support Chromebook clients if the Print Deploy server is not using a CA-signed certificate.

Outbound:

The following port and URL endpoints must be externally available for auto updating:

  • 443 (HTTPS), TCP with connections to:
    • https://update.print-deploy.cloud.papercut.com
    • https://storage.googleapis.com
  • 9163/9164 (HTTP and HTTPS) TCP to PaperCut Mobility Print servers when using the Import process.

Comments