Choose your language

Choose your login

Contact us

Set up Web Print: Default mode

This page applies to:

Default mode involves running the Web Print software on the same system as the PaperCut NG/MF Application Server. It is the fastest and easiest way to get Web Print working. It is suitable for testing Web Print functionality or where only PDF support is required.

In Default mode, the Web Print software runs as a service (background process or daemon) that is responsible for watching a directory for documents submitted by users e.g. PDFs. When a new document is detected, the background process opens the document and prints it.

Set up Web Print Default mode: Windows servers (PDF and picture files Only)

This section describes how to configure Web Print on the same Windows system as the PaperCut Application Server. This is the fastest and easiest way to get Web Print up and running on a Windows system. Due to the inability of Microsoft Office or XPS Viewer applications to run as a system service, these file formats are available on Windows only when Web Print is configured in sandbox mode. See Sandbox mode setup for more information.

Web Print Default mode supports the printing of PDF documents and image files on Windows systems. No additional configuration is required.

To confirm that everything is configured correctly:

  1. Select Enable Printing > Mobile & BYOD.
    The Mobile & BYOD page is displayed.

  2. In the Web Print area, check that the Status is 8.

  3. Click the Printers tab.
    The Printer List page is displayed.

  4. Select a printer.
    The Printer Details page is displayed showing the Summary tab contents.

  5. In the Advanced Configuration area, select the Enable Web Print (users may upload documents to print) check box.

  6. Repeat step 3-5 for all printers that will use Web Print.

If there are any status issues, or if basic Web Print testing produces some errors, consider these limitations/requirements:

  • The printers targeted for use via Web Print must be queues that are managed by the primary PaperCut Server. This includes print servers with the PaperCut secondary server installed.

  • If you want to print to remote printers, then the PaperCut NG/MF Web Print server needs to run under a user account that has permission to access these printers.

    Create a new user account called webprint (or equivalent). If it is not possible to create a domain user or the system is not a member of a domain, then create a local user account instead. Set the password for this account to never expire. At a minimum, this account needs access to all the printers you want to print to.

  • The printers (as configured on the server) must have working compatible drivers.

  • The following log file is useful in diagnosing issues: [app-path]/providers/web-print/[platform]/logs/web-print.log

Set up Web Print Default mode: Mac and Linux servers (PDF Only)

The Web Print Default mode supports PDF documents on Mac and Linux systems (running CUPS). No additional configuration is required.

To confirm that everything is configured correctly:

  1. Select Enable Printing > Mobile & BYOD.
    The Mobile & BYOD page is displayed.

  2. In the Web Print area, check that the Status is OK.

  3. Click the Printers tab.
    The Printer List page is displayed.

  4. Select a printer.
    The Printer Details page is displayed showing the Summary tab contents.

  5. In the Advanced Configuration area, select the Enable Web Print (users may upload documents to print) check box.

  6. Repeat step 3-5 for all printers that will use Web Print.

If there are any status issues, or if basic Web Print testing produces some errors, consider these limitations/requirements:

  • The printers targeted for use via Web Print must be queues that are managed by the primary PaperCut Server. This includes print servers with the PaperCut secondary server installed.

  • The printers (as configured on the server) must have working compatible drivers.

  • Linux: The primary server must be running CUPS version 1.2 or higher.

  • The following log file might be useful in diagnosing issues: [app-path]/providers/web-print/[platform]/logs/web-print.log

Comments