Chromebook Kiosk Mode

KB Home   |   Chromebook Kiosk Mode

Main.GCPKioskMode History

Hide minor edits - Show changes to output

July 05, 2018, at 09:50 PM by Arturo - added A workaround with Username Aliasing
Changed lines 13-14 from:
If a printer has been shared using this type of functionality, any user on the device can print to the printer regardless of what user may be logged into Google. In this case, GCP and PaperCut both do not know who is actually  behind the keyboard at that point in time - just that a person has printed on an authorized Chromebook.
to:
If a printer has been shared using this type of functionality, any user on the device can print to the printer regardless of what user may be logged into Google. In this case, GCP and PaperCut both do not know who is actually behind the keyboard at that point in time - just that a person has printed on an authorized Chromebook.
Added lines 19-30:
!!A workaround with Username Aliasing
It might be helpful to "trick" PaperCut into thinking the Chromebook service accounts are system users. To accomplish this ruse, use the Username Aliasing feature's [[https://www.papercut.com/kb/Main/UserNameAliasing|text file option]].

To get the names, you can check the job log as above to find documents that didn't print due to the unknown email/user policy. Another method is to send a job to a paused print queue with on-demand user creation enabled. The new user will show up in the user list. In either case, your new addition to the @@username-aliases.txt@@ file should look like this:

@@ 5fa3aba3f128df2d115a478ad458eec7_5380566666: Chromebook 1 @@
@@ 5da97b31f0d8c75515f51a461384cf66_5380566667: Chromebook 2@@
@@ c67240970f72ed904b9d73e8febeed75_5380566668: Chromebook 3 @@

Once you have all of the new names, save the file. Next, return to the PaperCut user list and DELETE the users created with on-demand user creation so the next time someone sends a job from the Chromebook, it will use the alias.

Changed line 34 from:
[-Keywords: generic, canceled, unknown email address-]
to:
[-Keywords: generic, canceled, unknown email address, username alias-]
March 13, 2015, at 05:57 PM by TimG - Updated to clarify 2 situations involved here
Changed lines 2-5 from:
 
to:

!!!Note that this will apply to both 'Kiosk mode' on a Chromebook, and also when sharing printers with individual devices, rather than with users or user groups.
\\

Changed line 2 from:
to:
 
Changed line 8 from:
to:
 
October 02, 2014, at 06:53 AM by 203.222.91.204 -
Changed lines 5-6 from:
For school administrators using Chromebooks, it may be easier to share local printers out with the actual Chromebook instead of singular users. This allows your users to print whether they are logged into their GCP account or not. The high-level explanation behind this is that the Chromebook itself is given an account to use for GCP enabled printers rather than relying on users to log into Google for printing functionality.
to:
For school administrators using Chromebooks, it has generally been easier to share local printers out with the Chromebook instead of singular users. This allows your users to print whether they are logged into their GCP account or not. The high-level explanation behind this is that the Chromebook itself is given an account to use for GCP enabled printers rather than relying on users to log into Google for printing functionality.
October 02, 2014, at 06:53 AM by 203.222.91.204 -
Changed lines 14-15 from:
PaperCut's recommendation for this type of deployment would be to share out the printers specifically to Google user accounts - or Google Groups, if utilized). Doing this means that the users email address will be printing to the GCP enabled printer rather than the Chromebook. This allows Google and GCP to successfully bind a user to that print job, and allows us to successfully look the email up in PaperCut to find that user.
to:
PaperCut's recommendation for this type of deployment would be to share out the printers specifically to Google user accounts - or Google Groups, if utilized. Doing this means that the users email address will be printing to the GCP enabled printer rather than the Chromebook. This allows Google and GCP to successfully bind a user to that print job, and allows us to successfully look the email up in PaperCut to find that user.
October 02, 2014, at 06:50 AM by 203.222.91.204 -
Changed lines 1-2 from:
(:title Google Cloud Print - Chromebook Kiosk Mode:)
to:
(:title Chromebook Kiosk Mode:)
October 02, 2014, at 06:50 AM by 203.222.91.204 -
Changed lines 1-2 from:
(:title Google Cloud Print - Kiosk Mode:)
to:
(:title Google Cloud Print - Chromebook Kiosk Mode:)
October 02, 2014, at 06:48 AM by 203.222.91.204 -
Changed line 17 from:
''Categories:'' [[Category.Google Cloud Print Articles|+]], [[Category.Troubleshooting|+]]
to:
''Categories:'' [[Category.GoogleCloudPrint|+]], [[Category.Troubleshooting|+]]
October 02, 2014, at 06:48 AM by 203.222.91.204 -
Added lines 1-19:
(:title Google Cloud Print - Kiosk Mode:)

Since the release of [[https://www.papercut.com/release-history/|PaperCut version 13.5]], the ability to print using Google Cloud Print (GCP) has been available to make BYOD easier and more manageable. Our recommended setup process for GCP has been documented and is made available [[https://www.papercut.com/products/ng/manual/ch-google-cloud-print.html|here]].

For school administrators using Chromebooks, it may be easier to share local printers out with the actual Chromebook instead of singular users. This allows your users to print whether they are logged into their GCP account or not. The high-level explanation behind this is that the Chromebook itself is given an account to use for GCP enabled printers rather than relying on users to log into Google for printing functionality.

PaperCut support has seen a few instances where administrators have been using this method and seeing jobs denied from an email that ends with @@@chrome-enterprise-devices.gserviceaccount.com@@

!!What is this email suffix?
If a printer has been shared using this type of functionality, any user on the device can print to the printer regardless of what user may be logged into Google. In this case, GCP and PaperCut both do not know who is actually  behind the keyboard at that point in time - just that a person has printed on an authorized Chromebook.

This will not be able to be used within PaperCut, as there is no ''user'' to account for the job, and there is no ''mailbox'' linked to this alias, which means PaperCut cannot send any authorization requests to that address.

PaperCut's recommendation for this type of deployment would be to share out the printers specifically to Google user accounts - or Google Groups, if utilized). Doing this means that the users email address will be printing to the GCP enabled printer rather than the Chromebook. This allows Google and GCP to successfully bind a user to that print job, and allows us to successfully look the email up in PaperCut to find that user.

----
''Categories:'' [[Category.Google Cloud Print Articles|+]], [[Category.Troubleshooting|+]]
----
[-Keywords: generic, canceled, unknown email address-]

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 July 05, 2018, at 09:50 PM
Printable View   |   Article History   |   Edit Article