System requirements: Print Deploy and PaperCut NG/MF

This topic covers:

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

IMPORTANT

Make sure there's an Internet connection so that software updates can be automatically installed.

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.

TIP

To see which driver languages work best with PaperCut NG/MF in regards to controlling, tracking, and giving users the ability to change print job settings at the time of release, check the Supported Printers knowledge base article.

Client requirements

  • Windows 7, 8, 8.1, and 10, 64-bit (Microsoft Internet Explorer 9+).

  • macOS X 10.12+ (Sierra) 64-bit.

  • Chromebooks.

  • Linux 64-bit (Modern .rpm & .deb based distributions).

Firewall rules

For an up-to-date list of PaperCut NG/MF 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) 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 TCP (HTTPS), with connections to:

    • https://update.print-deploy.cloud.papercut.com

    • https://storage.googleapis.com

  • TCP 9163/9164 to PaperCut Mobility Print servers when using the Import process.