PaperCut Print Deploy Set Up

[JamboD]

Hi all,

 

I'm trying to set up Print Deploy on our PaperCut server to allow our non-domain joined devices to access our print queues with full finishing options, I can get the client installed and logged in but the print queues never appear on the device.

 

If I check the logs I can see that Print Deploy knows what printers are required but the installation fails because it says that the username and/or password are incorrect, even though the client has authenticated against the server and I can print to these queues from a domain joined machine.

 

I have tried deploying them as Mobility Print queues instead (as suggested in another post) and Print Deploy installs them, but when I print the job spools on to the server and is immediately deleted which makes me wonder if there is some setting I have missed on the queue to make this work.

 

Has anyone come across this issue before please?

 

Thanks

[MatthewL]

If you have Mobility Print installed and working why not just download the Windows/Mac installer and run that?

[jasonatpapercut]

Hey JamboD,

 

If Print Deploy is trying to setup a print queue that points to a print server, e.g. Windows Client to Windows Server and the queue is like \\print-server.company.tld\find-me, then the issue will be that they're not domain joined and thus the SMB/UNC authentication wont work. Print Deploy doesn't take over the SMB protocol.

 

This is where Mobility Print comes into play. Windows, macOS, iOS, Android, and Chrome clients will all print via the Mobility Print server which handles the authentication at the OS level.

 

It sounds like the print jobs may be getting to the server already but are being cancelled for some reason. If you open the PaperCut Admin Console -> Dashboard and scroll to Real Time Activity, you should see the print job and more importantly, what PaperCut "did" with the job and why.

 

Do you see the job there?

[JamboD]

Hey JamboD,

 

If Print Deploy is trying to setup a print queue that points to a print server, e.g. Windows Client to Windows Server and the queue is like \\print-server.company.tld\find-me, then the issue will be that they're not domain joined and thus the SMB/UNC authentication wont work. Print Deploy doesn't take over the SMB protocol.

 

This is where Mobility Print comes into play. Windows, macOS, iOS, Android, and Chrome clients will all print via the Mobility Print server which handles the authentication at the OS level.

 

It sounds like the print jobs may be getting to the server already but are being cancelled for some reason. If you open the PaperCut Admin Console -> Dashboard and scroll to Real Time Activity, you should see the print job and more importantly, what PaperCut "did" with the job and why.

 

Do you see the job there?

Thank you for your reply Jason. Yes, I've looked at the log and it appears that the job is not being deleted from the Mobility Print queue, for some reason it's being assigned to SYSTEM ("Holding job printed by "system" in hold/release queue").

[JamboD]

If you have Mobility Print installed and working why not just download the Windows/Mac installer and run that?

 

Hi Matthew, we were hoping to allow the teachers to have access to all of the finishing options available on the photocopiers. I don't believe that that is possible with Mobility Print.

[jasonatpapercut]

Thank you for your reply Jason. Yes, I've looked at the log and it appears that the job is not being deleted from the Mobility Print queue, for some reason it's being assigned to SYSTEM ("Holding job printed by "system" in hold/release queue").

Poking our support teams about this.. There's one known incidence of this.

Do you use Canon drivers? We have a KB article here: https://www.papercut.com/kb/Main/MobilityPrintCanonSystemUsername#overview

Contents are roughly:

If so, try: "Canon Driver properties -> Device Settings -> Spooling at Host" to "Disabled"

 

 

With regards to:

Hi Matthew, we were hoping to allow the teachers to have access to all of the finishing options available on the photocopiers. I don't believe that that is possible with Mobility Print.

When using Print Deploy to deploy a Mobility Queue, you can deploy the native driver instead: https://www.papercut.com/support/resources/manuals/print-deploy/set-up-print-deploy/topics/computers-not-joined-to-local-domain.html

Basically, setup a Mobility queue on your reference machine, change the driver at the OS level, then clone the queue. Thats what will be used on the client machines. Users should have access to all of the finishing features that way.

[JamboD]

Poking our support teams about this.. There's one known incidence of this.

Do you use Canon drivers? We have a KB article here: https://www.papercut.com/kb/Main/MobilityPrintCanonSystemUsername#overview

Contents are roughly:

If so, try: "Canon Driver properties -> Device Settings -> Spooling at Host" to "Disabled"

 

[ATTACH=CONFIG]56345[/ATTACH]

That's brilliant! Thank you so much Jason, we are using Canon devices and changing the "Spooling at Host" option to disabled has allowed me to print to both of the queues we need. Now I just need to get the client installed through InTune and I'll have some very happy staff

Edited January 15, 2020 by JamboD

[jasonatpapercut]

Are memes allowed?

Can I meme here?

I'm going to meme here.

 

 

Glad we could help.