Skip to content
notifications
D
Organisation chevron_right Update policy

conveyor_beltUpdate policy

Set-and-forget: who tests first, how the fleet follows, and how strict review is. Day-to-day rollouts live under Updates.

1Test group (IT's own devices)

These devices always receive every update first, on real hardware, with a manual sign-off before the fleet follows. Usually IT's own machines.

2Rollout ladder

How the rest of the fleet follows after the test wave: in waves, each a share of the fleet. Groups are assigned whole, smallest first, so actual shares approximate the numbers you set.

1 to 5 waves, adding up to exactly 100% - e.g. "10, 30, 60" or "25, 25, 25, 25". Each wave soaks before the next starts.

Current plan

Wave Groups devices Share
Test ict-test 1 —
First office kantoor-a 10 38%
The rest how_to_regManual sign-off kantoor-b 16 61%

Current plan. Saving derives it anew from the test group; the advanced ladder below overrides it entirely.

3Maintenance window

Per group: the hours a device may fetch and switch to an update (HH:MM-HH:MM, overnight allowed). Empty means always. The rollout still decides WHAT and WHEN a wave releases - this only shapes the hour of the switch.

balie always
depot always
ict-test always
kantoor-a always
kantoor-b always
zaanstad always

Governance

How strict review is before a change takes effect.

tune Advanced: hand-authored wave ladder

Ordered waves: test waves first, then rollout phases. Each wave soaks and must be healthy before the next; a manual-gate wave waits for your approval. Saving replaces the whole plan.

0Wave 0 — Test
1Wave 1 — First office
2Wave 2 — The rest
add_circleAdd a wave

To add a wave, choose a group in the dashed row and Save. Leave soak and healthy empty for sensible defaults; a wave without a group is dropped on save.