When you're using Mobility Print, the print job owner name is SYSTEM

KB Home   |   When you're using Mobility Print, the print job owner name is SYSTEM

Main.MobilityPrintCanonSystemUsername History

Hide minor edits - Show changes to output

October 30, 2018, at 07:53 PM by Aaron Pouliot - minor edits
Changed lines 1-4 from:
(:title When you're using Mobility Print, the print job owner name is SYSTEM with a Canon Generic PCL6 or Canon PostScript driver :)

When using a Canon Generic PCL6 driver or Canon PostScript driver in conjunction with Mobility Print, the print job owner is changed to SYSTEM from the correct user. Good news! We have a workaround to avoid the issue which involves changing a print driver setting.

to:
(:title When you're using Mobility Print, the print job owner name is SYSTEM:)

''"Help! When users print through Mobility Print the job owner is "SYSTEM" instead of the actual username. Why does this happen and how can we fix it?"''

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
.
Changed lines 8-10 from:
-->1. On the Print Server where the print queue exists, right-click the print queue and select “Printer Properties”.
-->2. Go to the “Device Settings” tab.
-->3. You’ll see a setting called “Spooling at Host”. Set this to “Disabled”.
to:
# 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”.
July 12, 2018, at 07:09 PM by Aaron Pouliot - Removed mention of GUEST user as this was not accurate
Changed lines 1-3 from:
(:title When you're using Mobility Print, the print job owner name is SYSTEM or GUEST with a Canon Generic PCL6 or Canon PostScript driver :)

When using a Canon Generic PCL6 driver or Canon PostScript driver in conjunction with Mobility Print, the print job owner is changed to SYSTEM or GUEST from the correct user. Good news! We have a workaround to avoid the issue which involves changing a print driver setting.
to:
(:title When you're using Mobility Print, the print job owner name is SYSTEM with a Canon Generic PCL6 or Canon PostScript driver :)

When using a Canon Generic PCL6 driver or Canon PostScript driver in conjunction with Mobility Print, the print job owner is changed to SYSTEM from the correct user. Good news! We have a workaround to avoid the issue which involves changing a print driver setting.
July 12, 2018, at 05:27 AM by Mel Zouzoulas - re-created this KB without the double URL
Added lines 1-17:
(:title When you're using Mobility Print, the print job owner name is SYSTEM or GUEST with a Canon Generic PCL6 or Canon PostScript driver :)

When using a Canon Generic PCL6 driver or Canon PostScript driver in conjunction with Mobility Print, the print job owner is changed to SYSTEM or GUEST from the correct user. Good news! We have a workaround to avoid the issue which involves changing a print driver setting.

Here are the steps to take:
-->1. On the Print Server where the print queue exists, right-click the print queue and select “Printer Properties”.
-->2. Go to the “Device Settings” tab.
-->3. You’ll see a setting called “Spooling at Host”. Set this to “Disabled”.

This will allow us to track the print jobs under the correct username.

Want to learn more about Mobility Print? Check out the [[https://www.papercut.com/products/ng/mobility-print/manual/| Mobility Print Help Center]].

----
''Categories:'' [[Category.MobilityPrint|+]]
----
[-Keywords: Secret squirrel , Mobility -]

Comments

Share your findings and experience with other PaperCut users. Feel free to add comments and suggestions about this Knowledge Base article. Please don't use this for support requests.

Article last modified on October 30, 2018, at 07:53 PM
Printable View   |   Article History   |   Edit Article