User continues to print after remove / disable via admin console |
||||||
Issue descriptionChrome Version: (copy from chrome://version) 58 Beta (not with device.. cannot recall exact version... can update later if needed) OS: CrOS What steps will reproduce the problem? (1) Add a CUPS printer via User Settings in Device Management (ensure printing from device works) (2) Remove or Disable the CUPS printer from User Settings (3) Cached information in the device allows the user to continue using the printer What is the expected result? User should not be able to print to the printer that was removed / disabled. What happens instead? User is able to continue printing to the printer. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Apr 28 2017
There is a gap between server launch and DMserver launch. This issue should be resolved automatically next week after newest DMserver launch.
,
Apr 28 2017
,
Apr 28 2017
Disabling is a concept on server side and has nothing to do with client.
,
Apr 28 2017
Also, the policy refresh mentioned in Comment 1 is another possible cause for removed printers. We need to force refresh the policy if we want to see policy change immediately. DMserver launch should only affect disabled printers.
,
Apr 28 2017
zhanlu@, I'm pretty sure the problem is that the printers from policy are being cached somewhere on the client. Is this a failure you'd expect to see with some kind of version mismatch in the management infrastructure?
,
Apr 28 2017
,
Apr 28 2017
Ah, if you cache it, it might be one cause. snambiar@, could you post the up-to-date policy? If the policy does not contain the printer but the printer still works, it is not server side issue.
,
May 1 2017
@zhanlu / @weifangsun - Policy was refreshed. Checked that... reloaded a few times to ensure that. Printer still worked. As @skau pointed out, think caching is the likely reason.
,
May 10 2017
,
Aug 1 2017
,
Jan 22 2018
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by weifangsun@chromium.org
, Apr 28 2017