The staging schedule for applying a new update

This policy defines a list of percentages that will define the fraction of Google Chrome OS devices in the OU to update per day starting from the day the update is first discovered. The discovery time is later than the update published time, since it could be a while after the update publishing until the device checks for updates.

Each (day, percentage) pair contains which percentage of the fleet has to be updated by the given number of days since the update has been discovered. For example, if we have the pairs [(4, 40), (10, 70), (15, 100)], then 40% of the fleet should have been updated 4 days after seeing the update. 70% should be updated after 10 days, and so on.

If there is a value defined for this policy, updates will ignore the DeviceUpdateScatterFactor policy and follow this policy instead.

If this list is empty, there will be no staging and updates will be applied according to other device policies.

This policy does not apply for channel switches.
See https://cloud.google.com/docs/chrome-enterprise/policies/?policy=DeviceUpdateStagingSchedule for more information about schema and formatting.

Example value:

[
{
"days": 7,
"percentage": 50
},
{
"days": 10,
"percentage": 100
}
]

Supported on: At least Microsoft Windows 7 or Windows Server 2008 family

The staging schedule for applying a new update (The single-line field is deprecated and will be removed in the future. Please start using the multi-line textbox below.)

Registry HiveHKEY_LOCAL_MACHINE
Registry PathSoftware\Policies\Google\ChromeOS
Value NameDeviceUpdateStagingSchedule
Value TypeREG_SZ
Default Value


Registry HiveHKEY_LOCAL_MACHINE
Registry PathSoftware\Policies\Google\ChromeOS
Value NameDeviceUpdateStagingSchedule
Value TypeREG_MULTI_SZ
Default Value

chromeos.admx

Administrative Templates (Computers)

Administrative Templates (Users)