willemgroenewald

The real fix for Print Nightmare is Windows Protected Print mode (https://www.papercut.com/discover/the-complete-guide-to-windows-protected-print-wpp/), which was released last week. Windows protected print mode removes support for manufacturer drivers all together, and instead uses IPP. You can sign-up for early access for our first release that supports Windows protected print mode here: https://www.papercut.com/products/percolator/windows-protected-print-for-papercut-mf-ng/ With Print Deploy, users don't need admin rights to install print queues. If you only require basic finishing options, you can deploy Mobility Print queues with Print Deploy using this quick guide: https://www.papercut.com/help/manuals/print-deploy/set-up/import-printers/import-mobility-print-queues-quick/. If you need manufacturer drivers to support options like stapling, follow this guide: https://www.papercut.com/help/manuals/print-deploy/set-up/import-printers/import-mobility-print-queues-advanced/

Willem here, product manager at PaperCut looking after Print Deploy. The latest Print Deploy release fixed an issue that could cause print server queues to get unshared. Still, we want to confirm with customers who reported the issue that it addressed their issue and that there isn't potentially another cause that we haven't fixed. Let me know if this release fixes this issue for you. To test, deploy print server queues to a user running Windows Print Deploy client version 1781 and who has manage printer privileges on the server. This known issue includes some tips on getting the latest client: https://papercut.com/support/known-issues/?id=PD-1911#mf

Ok, no need to switch the feature toggle anymore. Since version 1.2.1045 (Feb 17 2020), shared Windows devices are supported when deploying Mobility Print queues with Print Deploy: https://www.papercut.com/support/resources/manuals/print-deploy/release-history.html For others stumbling across this post, it is how you can authenticate printing on Windows computers that are not joined to a local domain, which is often the case for zero trust networks.

Here is a solution for you. Mobility Print is designed for BYOD devices, and for Windows it assumes only one user will be using it. The user's identity is encrypted and included into the printer url in order to identify the owner of the job. For shared Windows devices that are not joined to a local domain, check out Print Deploy. Follow this guide to deploy Mobility Print queues to users using Print Deploy. https://www.papercut.com/support/resources/manuals/print-deploy/set-up-print-deploy/topics/computers-not-joined-to-local-domain.html Mobility Print is only used for authenticating printing. But, the trick is to switch on an unreleased feature to support shared Windows devices. Here is an internal video that explains how it works and how to switch it on: We'll officially release it soon, but feel free to start using it. PS, I work for PaperCut.

Hey Thimon, Willem here from PaperCut. If DNS or mDNS was an issue on your BYOD WiFi, then you could try the "Known Host" option which doesn't require DNS at all. https://www.papercut.com/support/res...nown-host.html. This option essentially tells the client where the Mobility Print server is at the time of setup. If your BYOD WiFi is completely separated from your network and you don't want to expose any servers to it, then I have good news for you. We are working on bringing cloud printing to Mobility Print, which will be available in a couple of months. There will be no additional cost for it, and you will not have to open inbound network traffic to your Mobility Print server. If you want to get a notification when this is available, you can sign up on the "got notified" form on this page: https://www.papercut.com/products/fr...obility-print/

Can you drop us a mail at [email protected] and we can help you out. When setting up a Mobility Print queue on a computer, a generic driver is installed. When the print job is received at the Mobility Print server, it is reprinted to the print queue on the server using the driver you installed on the print queue. However, when you deploy a Mobility Print queue using Print Deploy, Print Deploy assumes you are happy with the driver, default settings and finishing options that was installed on the reference computer. Therefor, when the print job is received at the Mobility Print server, the job is not reprinted, and instead the spool file is passed through to the destination queue as is. My suspicion is that the driver installed on your reference computer is not compatible with the printer. Try to manually update the driver, and then clone the queue from the reference computer.

If you setup PaperCut to sync and authenticate with Azure AD over Secure LDAP, then the Print Deploy once off authentication will authenticate the user's credentials against Azure AD. So it does help with authentication and you can get rid of any local Active Directory.

When your computers are not joined to a local domain, for example, connected to Intune only, then you need to 1. Install Mobility Print on your print server and publish your "FollowMe" print queue. 2. On your reference machine, install your "FollowMe" queue, but instead of your normal server shared queue, use the Mobility Print queue. 3. Update your driver, default setting and finishing options based on what you want to deploy 4. Run the cloner, and deploy this Mobility Print cloned queue to your Azure joined computers. This page explains how to install printers on computers joined to Azure AD / Intune. For these non domain joined computers, users will receive a once off authentication popup. Note, that if the default text is not optimal for your organisation, then you can customise it. With this setup, Mobility Print takes care of authenticating print jobs. Spooling of print jobs will be done locally on computers, so your server load will be minimal. Drop us a mail at [email protected] if you need any additional help.

For people who do come across this post, PaperCut 19.1 is available now. Checkout Print Deploy: https://www.papercut.com/tour/print-deploy/. With Print Deploy you can deploy any print queues and drivers, including Mobility Print queues to users via Intune or other MDM deployment tools. Print Deploy is available under the new Enable Printing tab in the Admin interface. Documentation is available here: https://www.papercut.com/support/resources/manuals/print-deploy/home-print-deploy.html

If it helps, the official release will be available mid August.

Hi Bicky, I've got a solution for you. Drop me a mail at [email protected], and I can hook you up with an early version of a feature coming out in our next release that will make deployment via Intune a breeze.

@OllyM, Willem here from PaperCut. We actually have an update coming up in 19.1 that will make it possible for you to deploy a small client via Intune. The client does a few things. - Deploy print queues, including a native driver, default printing options and capabilities like stapling, hole punching etc. - Authenticate the user, so the computer does not have to be joined to a local domain. Drop me a mail at [email protected], and I'll hook you up with an early version if you want.