Yes. You can definitely use Print Deploy in a private cloud, and you don’t need a print server on site. Of course, you can still choose to use an on-premise PaperCut NG or PaperCut MF primary or secondary server. See Step 1: Determine your print environment for guidance on which print environment will work best for you.
Yes, whether your users print via a server or directly to printers, you can use Print Deploy to deploy print queues to their computers, even if their computers are not members of a domain. In other words, Print Deploy allows you to easily track print jobs whether or not the workstations are members of a domain.
Print Deploy's versatility is a great added benefit for organizations that use G Suite or Azure AD where their computers are not members of a local domain.
Yes. The Print Deploy client running on the end user's computer takes care of the authentication, so the computer doesn't have to be joined to a local domain. We support printing for these environments to go either directly to the printer, or via a server. When printing via a server, we use the authentication mechanism of Mobility Print.
For the PaperCut MF 19.1 release, we focused on traditional Windows and Mac environments, and did not specifically tested Citrix environments. Rest assured, we’ll be testing Citrix environments very soon.
By default, the PaperCut NG/MF Mobility Print server uses a self-signed certificate. While the self-signed certificate secures communication, using one means that Windows client machines will not be able to use HTTPS to print unless steps are taken to trust the self-signed certificate or the PaperCut NG/MF Mobility Print server certificate is upgraded to a Public CA (Certification Authority) Signed Certificate.
If this concerns you, these are your two different solutions:
- Export the existing self-signed certificate from the PaperCut NG/MF Mobility Print server and import it into the Windows 'Trusted Root Certification Authorities'
- Use a custom CA Signed & Chained Certificate from a popular Public Certificate Authority.
After completing one of the two solutions above, the PaperCut Print Deploy client will be able to verify the validity of the certificate in use by PaperCut Print Deploy and configure your Windows client to use HTTPS.
Before you start, make sure your PaperCut NG/MF Print Deploy reference machine is using the FQDN (Fully Qualified Domain Name) for the PaperCut NG/MF Mobility Print queue. Using only the server name will likely not match with a valid CA Signed Certificate.
The cloner tool and reference computer
No, you need a separate reference computer for each OS. That is, clone a macOS computer for macOS users and clone a Windows computer for Windows users. However, many Windows drivers support multiple versions of Windows, and in those cases you can set up just the one reference computers for all version of Windows.
It deploys native drivers, including their default settings like grayscale and duplex, and their capabilities, like stapling and hole punching.
Yes. On the reference computer, create a print queue using the same name for print queue but change the settings. When you clone it, it will update the existing queue with the latest driver and settings, and will automatically deploy the updated driver to users. Also take a look at Maintain your print environment with Print Deploy.
You can set up new queue(s) on any reference computer at any time and clone them into Print Deploy, just like when you set up the original queues. Cloning adds the new queues to the existing list on the Print Deploy page.
- If your print server is running the same operating system as your users’ computers, and you want to convert your existing computers to use Direct Printing instead of printing via the server, then you can clone your server.
- If you are already running PaperCut NG/MF on the server, you should not clone the print queues from that server.
- If you want to configure computers to print via the server, then you should not clone from the server; you should clone from reference computers instead.
Yes. You can clone and deploy a Find Me queue to users. Find Me print provides a great experience for users as they print to a single print queue and release their document at any printer. A globally distributed organization can choose to have a Find Me print queue per region, and deploy each region’s queue only to relevant users based on their location.
No, you don’t need to keep a reference computer on. In fact, we recommend you use a virtual machine for you reference computer, so that you can easily shut it down to be used later.
Absolutely, there is no dependence on the original reference computer and there’s also no need for the original reference computer to stay switched on.
Zone and user group configuration
Yes. IP ranges can overlap, and users connecting to multiple zones will get the print queues from all of those zones.
Print Deploy automatically removes print queues that were deployed by Print Deploy and are no longer applicable to the zone the user is in. Print Deploy does not remove printers that were manually installed, for example home printers.
To access the User Groups feature, you must upgrade to PaperCut NG/MF version 19.2.
Adding a group via Add/Remove groups is most certainly reflected in the User Group list for creating or modifying zone. Deleting a user group will instantly remove that group from any existing zone.
Adding/Removing a User Group via a server command is also reflected in the User Group list for creating or modifying zone. However, deleting a group will not immediately remove that group from any zone. It will be deleted when the Print Deploy server runs its nightly maintenance task.
The zone will default to use the All users option, which means all users with matching IP addresses defined in the zone will have access to that zone.
Check if the user has somehow been removed from PaperCut NG/MF. If yes, add the user back into the group.
Yes! You can choose to skip the installation of the bundled Direct Print Monitor when installing the Print Deploy client. Simply follow these steps on how to deploy print queues but not the monitoring tool.
Check that the computer the client is running on is Windows 7, 8, 8.1 or 10, 64-bit version. The above error occurs on 32-bit versions.
Absolutely. The Print Deploy client sets the default printer (default print queue) based on if a print queue name is a Find me / Follow me queue (or variation of, with spaces/hyphens in between). However, if Windows has been set up to manage the default printer for users, then the client honors the Windows setting.
Usually no, except when the user has been asked to install the Print Deploy client themselves.
You can use a Mobile Device Management (MDM) tool like Microsoft Intune, SCCM, GPO, or Jamf to push out the client. The user will then get the popup for authentication and the printers get installed without requiring them to have admin rights.
If you do not have an MDM and your users don’t have admin rights, then you can still log in manually on their computer as an admin user and install the Print Deploy client.
Not yet, but Print Deploy will support this soon.
Yes, as long as the names are identical. Print Deploy replaces the previously installed queue, which makes it easy to clean up old deployments with the latest drivers.
No. Print Deploy only removes print queues that it has installed.
No, only Direct Print queues deployed through Print Deploy are tracked and controlled by PaperCut NG/MF. This allows users to install printers at home without PaperCut NG/MF tracking those print jobs.
No, Print Deploy is responsible for deploying queues. If the user’s computer can’t reach Print Deploy for any reason, even during outages, their print queues will remain active and printing will work. The only thing that will be impacted is that new print queues won’t be installed on the computer.
Yes. Print Deploy monitors only printers that were installed using Print Deploy, with one exception: if you are overwriting a non-Print Deploy queue with a Print Deploy queue that has the same name. We track those!
A check is made to see if the Direct Print Monitor (in ‘print deploy mode’) is installed. This check is the config key: pdclientsupport=true in the Direct Print Monitor config file.
If there is already a Direct Print Monitor in 'print deploy' mode installed (this would only be within the PD client install directory) the new install will continue.
If there is already a direct print monitor as part of a PaperCut installation (in the PaperCut MF/NG directory) installed on the client machine, the install will fail gracefully—for manual installations it will exit and inform the user; for automated (GPO, Microsoft Intune, Jamf) installs it will fail silently.
If you are migrating users from manually deployed Direct Printing over to using Print Deploy, then you should first uninstall the Direct Print monitor before you deploy the Print Deploy client.
No, it doesn't. You can still use the PaperCut User Client for account selection or interaction with Advanced Printer Scripting. For account selection, you can consider letting users select Shared Accounts at the copier if you run PaperCut MF.
Configure the Mobility Print Chrome app to talk to your Print Deploy server when:
your organization’s Chromebooks are all managed
each user signs in on their computer with their own account
you want fine control over which printers users see depending on their IP and/or group membership.
However, we advise you using the Mobility Print Chrome app without Print Deploy in any of these scenarios:
your devices are shared, that is, one or more users are using the same account or session
you’re in a BYOD environment where users bring in their own Chromebooks
you want to track printing per print job.
As long as the user has selected the Remember Me checkbox, there is only a once-off request that occurs the first time the user’s list of printers is displayed. It will only ask for credentials again if new printers are added to the user’s zone.
No. To make that happen, use the Mobility Print Chrome app without Print Deploy and configure your print queues to authenticate per job from the Mobility Print server.
Unfortunately not. Configuring policies for apps on Chromebooks is only possible via Google’s Admin Console.
Currently, only Mobility Print queues can be deployed.
No. If both are set in the policy file, the Print Deploy configuration will take precedence over the known host configuration.
Not yet, but it is coming very soon.
Every 24 hours, the Application Server automatically checks with PaperCut NG/MF for, and if required installs, Print Deploy updates. Similar to how Mobility Print automatically updates.
The Print Deploy client checks in with the Application Server every 24 hours, and applies any updates. Similar to how Mobility Print automatically updates. Both automatic updates ensure you have the most recent version of the Print Deploy cloner tool and Print Deploy client.
If your Application Server does not have internet access, you can still install regular PaperCut NG/MF releases manually, and these releases will include Print Deploy updates.
Yes. The updated package is downloaded from the Application Server and installed without requiring any input from the user.
Yes, and in fact the time is randomized by default.
Print Deploy clients check in with the Application Server at a scattered rate according to the initial and ongoing randomization setting. The randomized setting can be from 1 second to 24 hours, evenly distributed across all computers. This means that all computers check for updates at least once, if not twice a day.
For details about how to change the default time, take a look at Change the polling time.
If you roll back to an earlier version of PaperCut MF (say, to a version that doesn’t have Print Deploy, that is, prior to PaperCut MF 19.0), the clients won’t be able to talk to the Application Server and will fail silently in the background. However, for versions 19.1 and later, the PaperCut Print Deploy client will never be ahead of the server version-wise because it will always get the update from the server that it talks to.
Print Deploy is very light on server resources. Delivering large print drivers to clients might consume a lot of network bandwith depending on the driver size in question. SysAdmins can configure Print Deploy clients to check for updates less frequently, and you can also configure randomization times and backoffs to avoid significant bandwidth usage spikes.