Skip to main content

Google Cloud Printing using Papercut MF

We have been using Papercut to manage printing for some years and its an excellent piece of software. However, as we have gained more and more ChromeOS devices, there has been a need to have managed Cloud Printing. We have been able to deploy cloud printers, I wrote a document about it here.

This method had the limitation that the printing was not billed to a specific user or account. I had to setup Papercut to charge to one shared account. It also did not allow for printing to copiers as they did not talk to Papercut and required an additional layer of authentication that Cloud Print could never support. The solution appear at the end of last year when I noticed that the latest revision of Papercut supported Google Cloud Printing. As the contract for our copiers was up for renewal, we took the opportunity to get copiers that have embedded Papercut on them. This means they talk directly to our Papercut server.

So we are now on Papercut MF 14. This has an option to enable cloud printing and publish printers to the cloud. So I have published our Mono and Colour copier pools to Cloud printing. These I've shared to groups and as the owner of the groups approved the share. So this basically allows us to cloud print from ChromeOS (or any other device) to our copier pools from anywhere.

So a user selects a cloud printer:

This is the mono pool - so the print job can be picked up at any copier.
If they then do nothing, they will get and email telling them to click on a link to choose an account to print to (or they can go straight to the site rather than wait for the email). At which point they get this browser popup:

The user can then select an account and print or cancel the job. They can then pickup the job from the copier.

This is for staff who print to accounts that as assigned to them. Students print to a print quota, so they can go straight to the copier to pick up a job. When they run out of quota, they cannot print until we give them more.

So we have managed printing from ChromeOS for the first time. It will be interesting to see how in pans out in the coming few weeks. It offers some interesting possibilities - I took a picture on my phone and printed it straight to a copier - modern android phones have cloud print build in.

Some things to consider:
  • This does not work across a non-transparent proxy - then again what does!
  • On Papercut you must have your Google Apps account on all your users - so Papercut syncs with Active Directory to get its users. If your user names on AD and Apps are the same this is easy.
  • You need an account for sharing printers. We use one called printman.
  • Papercut needs to be able to send emails - so this is where it falls down with non-transparent proxies.
  • To get the Papercut popup on cloud print outside your network you need an external IP address for you print server.
  • You need the very latest build of Papercut which is v14 build 26241 at the time of writing - this resolves some timeout issues with the cloud connector. 
  • Its very new - so expect err issues!


Popular posts from this blog

Delete a specific email using GAM

If a user send an inappropriate email to a loads of people or get stung by some sort of email exploit you can quickly delete the email from all of the recipients using a GAM command.
Step 1 - get the email header Go into Google Vault and search for the offending user or someone known to have got the message.
Click show details and grab the email ID. This will be a long string of characters followed by @mail.gmail.com
Step 2 - find out who has the email Go into Google Vault and find the original message sent by the offending user. Look at the details to see who got it. Copy the list and dump it into a spreadsheet. Clean up to just a list of emails with a column header 'mail'. Save as a csv file.
Step 3 - delete messages with GAM Put your CSV file in your GAM folder - this e.g. assumes its called mail.csv
Run:
gam csv mail.csv gam user ~mail delete messages query rfc822msgid:MESSAGEIDHERE doit

The alternative nuke option is:
gam all users delete messages query rfc822msgid:MESSAGEI…

How to push bookmarks to users in Chrome via the management console

With the release of Chrome and ChomeOS 37 an update to the management console has arrived that allows you to push bookmarks to users.

Under Device Management > Chrome > User Settings > User Experience you will now find the option to add managed bookmarks.


In the example above, the bookmarks are applied to the sub-OU of 'students' - so all our students will get these bookmarks. Simply add your url and the bookmark name, click the + and save. These will appear in a folder called 'yourdomain bookmarks' - see below:



Be aware that to get these bookmarks applied on a Windows/OS-X device the user must be signed into Chrome. Update: if you install the latest group policy template you can push the bookmarks via policy on PCs - details are given here.
Video Guide:

Managed Android Apps on ChromeOS on an Edu G Suite Domain

Android Apps via the Play Store have been available on consumer accounts for some time on selected devices. We have 1:1 Acer R11's and have recently had the opportunity to trial them on G Suite Edu accounts.

From the point of view of the end user, they see the Play Store App appear on the shelf and have to agree to the terms and conditions. After that, force installed and pinned apps are immediately installed and they get access to the Google for Work Store. This only contains apps you have approved for that user.

For the administrator the steps are:

Enable Play Store Apps for the domainEnable access to the Play Store for specific Sub-OUs or usersAdd apps to Play for WorkSet permissions for each app - can install, force install or pin to shelf. This can be done differently for each app and each OU and is therefore very granular. 
Issues so far

Apps take a while to appear in the Play Store for users. Initially only force installed apps appear.You cannot set the permissions of multipl…