New issue
Advanced search Search tips

Issue 892693 link

Starred by 2 users
Status: Assigned
Owner:
gan...@chromium.org
Cc:
grt@chromium.org
goanuj@google.com
sorin@chromium.org
georgesak@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Google Update Policy Setting "Time period in each day to suppress auto-update check"

Reported by niroshan...@kp.org, Oct 5 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36

Steps to reproduce the problem:
1. When "Time period in each day to suppress auto-update check" setting allow you to configure how many minutes to suppress update checks.
2. In "GoogleUpdate.admx" file, "UpdatesSuppressedDurationMin" has a maxValue="720".
3. I want to enable this policy setting with a starting hour value of 05:00 and a duration of 960mins (16hrs). Our organization doesn't perform software updates between 05:00 through 21:00 (16hours).

What is the expected behavior?
The policy does not allow me to set 960mins

What went wrong?
Google Update ADMX has a max value of 720 set for "UpdatesSuppressedDurationMin". This disallows my change to 960mins. 

Did this work before? No 

Chrome version: 69.0.3497.100  Channel: stable
OS Version: 10.0
Flash Version: 

Can you also make this ADMX friendly for UMA-URI with MS Intune? The current definition for "Pol_UpdateCheckSuppressedPeriod" makes it difficult to create an OMA-URI.

Comment 1 by niroshan...@kp.org, Oct 5 

At present this setting is not used. Instead, we have had "Auto-update check period override" enabled with a value of "1380" since 2016. At the time it helped us manage bandwidth constraints during business hours. However, I think  "Time period in each day to suppress auto-update check" setting can replace  "Auto-update check period override" as the former provides better control over update time period and not impact bandwidth during business hours. 
Bottom line: This request in No way blocks nor risks Chrome adoption. If this change is not made then we will continue to use the existing setting for Google Update policies.

Comment 2 by pastarmovj@chromium.org, Oct 8

Cc: sorin@chromium.org
Labels: Enterprise-Triaged
Owner: grt@chromium.org
Greg, Sorin, can you please take a look at this request?

Comment 3 by grt@chromium.org, Oct 8

Cc: georgesak@chromium.org grt@chromium.org
Owner: gan...@chromium.org
Status: Assigned (was: Unconfirmed)
It looks like the 12h cap is part of the original design. Assigning to Ganesh to comment on this request.

Comment 4 by goanuj@google.com, Jan 9

Cc: goanuj@google.com
Labels: OS-Linux OS-Mac

Comment 5 by grt@chromium.org, Jan 9

Labels: -OS-Linux
Removing OS-Linux since this is a policy for the updater, and we don't use an updater on Linux.

Comment 6 by gan...@chromium.org, Jan 10 

We thought that 12 hours was a reasonable setting at the time. We could reconsider of course.

Comment 7 by niroshan...@kp.org, Jan 10 

We have a general policy not to update software from 5AM-9PM PST (business hours for various facilities located across the US: from Eastern to Hawaii timezones). Thanks for considering this request.
►

Sign in to add a comment