Chrome devices not receiving policy update changes in timely manner |
||||
Issue descriptionChrome OS Version: around m64 Chrome OS Platform: Network info: WiFi My customer is having issues lately with updating policies and having them refreshed in a timely manner. The problem is intermittent but becoming more frequent over the past few weeks / months. They often repurpose chromebooks from one use case to another (e.g., from public session to kiosk mode) and often when doing so, the policy changes won't be reflected on the device for several hours. The chrome://policy indicates that the device has been refreshed, but the device doesn't change behavior. This often varies from device to device. Applying a single policy change to multiple devices will result in some of the devices updating immediately and some over the course of several hours. Steps To Reproduce: It happen intermittently, but one scenario is described above. (1) (2) (3) Expected Result: Policy updates made in the admin console are reflected in the Chrome device within a minute or so. Actual Result: For some devices it won't update for several hours. How frequently does this problem reproduce? (Always, sometimes, hard to reproduce?) Intermittently, becoming more frequent over the past few weeks. What is the impact to the user, and is there a workaround? If so, what is it? User can't confidently change policy and immediate use the device. May have to update the policy and then let the device sit idle for several hours before using.
,
Jun 11 2018
Pete, could you provide more details about the environment? Devices, OS version? Also, it's not clear for me whether chrome://policy page shows already new policy or the old one, but as it was just updated? Please, note that transition from public session into kiosk mode won't happen immediately after receiving new policy - the existing session should first be finished, or even better is to reboot the device.
,
Jun 12 2018
if this is ChromeOS specific bug, please open it in buganizer. Enterprise>Device component.
,
Jun 12 2018
We (Chrome OS Enterprise team) track our bugs here on Chromium bug tracker under Enterprise component. I hear about Enterprise>Device component on buganizer for the first time.
,
Jun 12 2018
sorry for misleading. I thought this is same as ChromeOS DMServer bug (ken's team). Please ignore my comment in C#3. |
||||
►
Sign in to add a comment |
||||
Comment 1 by ljusten@chromium.org
, Jun 8 2018Owner: poromov@chromium.org
Status: Assigned (was: Unconfirmed)