If a printer's language is not recognized, PaperCut NG/MF cannot detect any pages and record the print job as a zero page count. However, it should be noted that there will need to be PaperCut accounts associated with the device email addresses.īasically, you'll want to verify that you have the printers shared out to either users or groups of users and NOT the devices themselves, since when shared out to the devices themselves, you'll get these errors where PaperCut isn't able to authenticate the user, as the job is instead coming from the device, and not the actual user.PaperCut NG/MF currently supports about 90% of printers on the market. This is especially handy for Chromebook labs where you want to limit sharing to specific devices, and are not concerned with which users are printing, but rather where printing is happening. If you only have a small handful of Chromebooks or don’t mind collecting all of the on device accounts you can set up a Google Group containing all of these device email addresses. To ensure that all group members can print there will need to be an Owner of the group, and the Owner account will need to accept the share. PaperCut support has seen a few instances where administrators have been using this method and seeing jobs denied from an email that ends with customers with fleets of Chromebooks we are presently unable to deploy Google Cloud Print print queues to these devices directly using Google Apps Admin Device controls.Īt this time our recommended workaround is to set up Google Groups and “deploy” the GCP print queues to them via the Sharing interface. 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. This allows your users to print whether they are logged into their GCP account or not. "For school administrators using Chromebooks, it has generally been easier to share local printers out with the Chromebook instead of singular users. Which relates back to what we mention here: and here: In the logs for the time you mentioned, we're getting back the following error: It may come down to how you're deploying/sharing the printers out. Below is the resulting support response after my back and forth troubleshooting with Papercut. I would suggest really doing a deep dive review of how you want to be able to print and how Papercut handles GCP before switching over. If you were able to harvest the device email address you could theoretically get it to work however, Google does not have any way to export this information. We want to assign printers to chromebooks (devices) and not users, Chromebooks are static within a building, users move every year. as usual, Scholars and Ladies/Gentlemen I appreciate all of your assistance.įor us Papercut is awesome aside from their Google Cloud print which does not work for us. What does everyone think, would you suggest something else?Įdit: wow, thanks for the wonderful responses everyone, it sounds like papercut really is all its made out to be, I was also given some other suggestions to play with. Is it as easy to assign printers as GPO's and GCP? I already its reporting is great. So who is using Papercut, particularly "mobility print", how do you like it, is it as set and rely on as it should be? Which I could deal with if I didn't have to do it whenever it wants aaaand whenever the print server or host server reboots. printers would just go offline in GCP, the only solution I have found is straight deregistration of the service, removing all printers and assignments and redoing it all again. it didn't take long however and we noticed weird printing problems and stability issues. Once it was originally setup in a stable manner things seemed ok, reporting blew but admin was ok with that. We have been trying to use google cloud print for printing for both our staff and student chromebooks.
0 Comments
Leave a Reply. |