Chromebooks are in the same enterprise OU logged on as the same user.

Deleted: 20180511_115015.jpg 1.5 MB

	20180511_115015.jpg 1.5 MB View Download

hawlbe@ I am unable to reproduce the issue mentioned after triggering an update from M66.0.3359.139 10452.85.0 stable to M66.0.3359.158 10452.85.0 stable.  I was able to the list of cloud printers on my end.

Could you attach the policies and logs?

The printers have started to show up on the HPs now.  Not sure what the issue was last week, but spotty issue like this have happened with the google cloud print service before.  We usually have to restart the service, and sometimes take it to the un-register re-register level.  This is the first time we have seen that even that didn't fix it for all chromebooks in the same OU.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sean, could you please find an owner for this bug?

thestig@: Do you know if this is a KI?  If you don't have time to investigate, assign it back to me.

Not KI. I don't see any changes on the browser side between 66.0.3359.137 and 66.0.3359.158 that is related to printing.

Thank you katierh@ for the ping. 

Plan to work with Paolo on this one. 

The issue seems very puzzling. For the records, which is the sharing mechanism of the printers? Group sharing with the users? Or sharing with the device?

cloud printers are shared from the print server to device OUs via cloud print service

Are the devices owned by the same OU?

I have the same issue in Chrome 64-66 in a production EDU environment, issue currently escalated to Google Engineers.

I am also chiming in to say that I am experiencing this problem too. I recently updated on of my Windows servers using the Chrome print connector. Upon adding printers back in and re-registering no Google Cloud Print printers will come down to any of my fleet of Chromebooks. 

My test Chromebook is on 66.0.3359.181

>My process is to use the Windows Chromeprint service
>Add printers to my Windows server
>Login to Google Admin > Device Settings > Add Google Cloud printers to specific OUs.

Currently the Windows service is registered, I see the cloud printers added in the cloud print web dashboard for the Google account registered, and Google Admin will see them as the list of available printers to assign to OU's, however, they never appear on my Chromebooks now when assigned. 

I used this connector here: https://tools.google.com/dlpage/cloudprintservice

and this one: https://github.com/google/cloud-print-connector

and built a new server from scratch to test with no effect.

As an important note, if a printer is deregistered and reregistered, this is not readded automatically to OUs. What may actually happens is that the admin console shows the OLD printer instead of the one! If that is the case a possible fix is - all within the admin console - removing the existing printers and adding them back.

Like the original author; my printers are now appearing immediately after assigning them to specific OU's now. Not sure if there was some sorta slow issue on the Cloud Print back-end or what?

Was it determined that there is a client issue here or a problem with the console?