Papercut - shared devices

[pooley]

Very new to papercut, have it setup for domain pintng and byod/mobile printing but how are people using it for shared devices? Specifically Windows OS, if I add the printer manually

to the non-domain pc then it caches the credenials used to access the network printer. BYOD/Mobile client only prompts for credentials on install of the app and not every print.

[mikkydoos]

Bit confused by the post but you might be looking for this...

 

https://www.papercut.com/support/resources/manuals/ng-mf/applicationserver/topics/find-me-printing.html

[Rob_D]

So this is a non-domain windows device?

 

I'd just use the Mobile&BYDO options.

 

We've got Web Print set up so people can print from the IPads. People log into web front-end on your server and submit jobs. You set the print queues they have access to. No reason it can't work the same from a windows device as long as it has a network connection. And you don't need to map the printer to the device.

 

Not sure how it would work with direct printing as we have Follow-Me/Find-Me set up with print release stations.

[MatthewL]

Is this via Mobility Print is caches details? If so you need to set it to authenticate per job in the admin side there.

[pooley]

Thanks all.

 

It's a non-domain windows device that was/is using the network credentials I used to install it to authenticate to papercut. I'll have a look at authentication per job and see if that sorts my issue.

[MatthewL]

Are you using Mobility Print or another method its not clear?

[pooley]

I have tried just installing the printer directly from the print server, but when a user prints it uses the network details of the account I used to install the printer.

 

Mobility print app works the same, on install it asks for the account credentials to use, so when you print it uses them by default and doesn't prompt.

[thimon]

Hi @pooley If you're using Mobility Print you only need to enter user credentials the once, then Mobility Print remembers it and communicates back to PaperCut. Even if it's possible I wouldn't want to have to authenticate for every print job, that would be crazy! It sounds like it's working as expected?

 

EDIT: Just seen you said it's using the network details of the account you used to install the printer. I would advise contacting PaperCut support via [email protected] Their support team is amazing!

Edited February 6, 2020 by thimon

[pooley]

I've tried both methods.

 

What I want is to be prompted per print job, these are shared devices with just a generic single login. I wan't any user to be able to pick them up and print to their queue.

 

Ill try support thanks.

 

Si

[Rob_D]

I've tried both methods.

What I want is to be prompted per print job, these are shared devices with just a generic single login. I wan't any user to be able to pick them up and print to their queue.

Ill try support thanks.

Si

 

I still think using web print would give you what you want. You just need to set the browser to not remember the login. That way they log in, submit their print jobs to the queues you've set and when the close the web browser the login session ends.

[gds64]

It sounds like you want to use the unathenticated printing feature: https://www.papercut.com/kb/Main/UnauthenticatedPrinting

[MatthewL]

MobilityPrint is the way forward for PaperCut for BYOD/shared devices, PaperCut are keeping web print as it has certain uses but MobiltyPrint and authenticate per job sounds the right option here.

 

When running on a Windows device there is an installer you can run as apposed to mapping the printer direct.

[pooley]

MobilityPrint is the way forward for PaperCut for BYOD/shared devices, PaperCut are keeping web print as it has certain uses but MobiltyPrint and authenticate per job sounds the right option here.

 

When running on a Windows device there is an installer you can run as apposed to mapping the printer direct.

 

I've tried the installer but it asks for the username and password on install, then uses that each time you print. I can't get a challenge/prompt for username and pass.

[thimon]

I've tried the installer but it asks for the username and password on install, then uses that each time you print. I can't get a challenge/prompt for username and pass.

That's by design. I still don't understand why you would want a user to enter credentials for every print job?

[Rob_D]

That's by design. I still don't understand why you would want a user to enter credentials for every print job?

Because they're shared use/loan devices. Each lesson it might be used by a different user.

Although, if they're windows is there any reason they can be domain joined?

[MatthewL]

They are shared devices, prompting each time is the way to do it to ensure the jobs are logged against the user using it.

 

Pooley will look into something regarding that and come back to you.

[willemgroenewald]

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.

[pooley]

Awesome, thanks very much for this info.

[willemgroenewald]

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.