Hi all,

Is there any new information on this issue. Can we gather something else through the technical case to help the investigation?

Thanks!

@derat, can you help triage?

Why did this sit around for 3+ months? :-(

The screenshot at https://drive.google.com/corp/drive/folders/0B6fESMmJITTNZUlqQk1IX0RiUEk suggests that only the idle delay (in this case, for the action "suspend") is being set. The log message that you quoted states the same thing:

ac_dim=7m ac_screen_off=8m ac_lock=8m10s ac_idle_warn=0s ac_idle=1h battery_dim=5m battery_screen_off=6m battery_lock=6m10s battery_idle_warn=0s battery_idle=1h

ac_idle and battery_idle are 1h, but ac_lock and battery_lock are 8m10s and 6m10s, respectively.

The policy should set the lock (and probably dim and screen-off) delays as well:

https://www.chromium.org/administrators/policy-list-3#ScreenLockDelays
https://www.chromium.org/administrators/policy-list-3#PowerManagementIdleSettings

I assume that was an accidental reassignment. The system appears to be behaving as expected per the policy in the screenshot.

@derat,  perhaps the customer (and myself) are confused on this policy...

If ac_dim=7m ac_screen_off=8m ac_lock=8m10s...  why even have a longer ac_idle via policy if the screen will dim, shut off, or lock earlier anyway?  I guess the question is, what exactly does 'idle' policy do?

I believe the customer's intention was to keep the screen on for an amount set in policy.

To add context..   in a school setting where chromebooks are used during class, teachers don't want their students logging in, for example, 6 times during a 60 minute class so the admin in this case intended to set this policy for 1 hour to avoid that.

The idle delay is the amount of time before the idle action (suspend, by default) is taken. I don't work on the enterprise side of things, but the way these policies interact is documented in the links that I supplied in #5. If the documentation is unclear, please take it up with the enterprise team -- I'm happy to help if they have any questions.

If the admin wants their Chromebooks to stay on and unlocked with the screen undimmed for 60 minutes even if nobody interacts with them, they should set the screen-dim, screen-off, screen-lock, and idle delays to 60 minutes.

Agreed. This needs more triaging. 

Yehuda: Can you check which exact policy is being set using chrome://policy and confirm what @derat said. If the documentation in admin console is not consistent then its a separate bug for buganizer.

Agreed as well.

From the ChromeOS standpoint, this is not a bug and working as intended.

From the CPanel side, it appears that we only expose the user configurable 'idle delay' time setting and not screen-dim, screen-off, screen-lock.

See: https://screenshot.googleplex.com/nPnh6rxA9OJ.png

chrome://policy > PowerManagementIdleSettings (found on the device - set via CPanel) only modifies the idle settings and does not change the values for screen-dim, screen-off, screen-lock.

See: https://screenshot.googleplex.com/SRFVubt07Yq.png

This probably should be classified as a Feature Request to either:
 a) expose user configurable screen-dim, screen-off, screen-lock delay times in CPanel settings (same as Idle Delay time)   -or-
 b) change all the values of screen-dim, screen-off, screen-lock when Idle delay time is set.

Hello all, thank you for working on this. I am the Administrator at New Milford Public Schools, where this issue is occurring.

In the Admin console, we have the policy set to put the devices to sleep after 60 minutes. However, the devices are going to sleep after 10 minutes.

If your conclusion is that the policy is acting as intended, I will need some type of walkthrough on what settings need to be applied in Admin console for the devices to go to sleep after 60 minutes, instead of 10

Pardon my response. I understand what you are saying now. We currently do not have that option in the Admin console.

So will this Feature Request be submitted? Or will have have to do something else for that to happen?

Its a reasonable FR. 
- Since this is an admin policy FR, this is tracked differently using a different tracker.
- Yehuda can you take care of this and close this bug.

dileonej, appreciate for your input here.

I will go ahead and file a formal Feature Request to expose these items in the Admin Console and reach out once we have an ETA.

Thanks!

The feature request has been filed internally - (reference #34513906)

dileonej@, we will update you via the support case when we have a solid ETA for you.