Papercut Mobility Print - Hits queue as SYSTEM

[snagrat]

I have setup Papercut Mobility Print and can successfully install the client, sign in and the printers appear.

 

But when we print from home the job gets added to the queue from the user SYSTEM. This means we cannot release using our cards or by the user logging into the web GUI.

 

Any suggestions when it doesn't go in with the username of the user?

[Mark182]

We have this set up for a couple of SEN students on their SEN devices. When setting up we use DOMAIN\USERNAME and password and then use a pin code to release the jobs.

[snagrat]

We have this set up for a couple of SEN students on their SEN devices. When setting up we use DOMAIN\USERNAME and password and then use a pin code to release the jobs.

 

We use Google authentication rather than a domain so not sure that is an option.

[EssentialRug]

I have setup Papercut Mobility Print and can successfully install the client, sign in and the printers appear.

 

But when we print from home the job gets added to the queue from the user SYSTEM. This means we cannot release using our cards or by the user logging into the web GUI.

 

Any suggestions when it doesn't go in with the username of the user?

 

We had a similar issue with prints from users appearing as system rather than their username. The below worked for us.

 

We’ve heard of this happening with very specific drivers (in particular the Canon Generic PCL6 driver and Canon PostScript driver). When these drivers are used in conjunction with Mobility Print, the print job owner is SYSTEM instead of the correct user account. Fortunately we know of a simple workaround which requires changing the settings of the driver.

Here are the steps to take:

On the Print Server where the print queue exists, right-click the print queue and select “Printer Properties”.

Go to the “Device Settings” tab.

You’ll see a setting called “Spooling at Host”. Set this to “Disabled”.

[snagrat]

We had a similar issue with prints from users appearing as system rather than their username. The below worked for us.

 

We’ve heard of this happening with very specific drivers (in particular the Canon Generic PCL6 driver and Canon PostScript driver). When these drivers are used in conjunction with Mobility Print, the print job owner is SYSTEM instead of the correct user account. Fortunately we know of a simple workaround which requires changing the settings of the driver.

Here are the steps to take:

On the Print Server where the print queue exists, right-click the print queue and select “Printer Properties”.

Go to the “Device Settings” tab.

You’ll see a setting called “Spooling at Host”. Set this to “Disabled”.

 

This was the issue! Some of the drivers didn;t even have it showing as it was using a custom config. Setting it to iR-ADV and I can change the setting and it works.

 

Thanks so much!

[EssentialRug]

This was the issue! Some of the drivers didn;t even have it showing as it was using a custom config. Setting it to iR-ADV and I can change the setting and it works.

 

Thanks so much!

 

Nice! Glad you got it sorted!