Skip to main content

Overview

The Overview section provides an interactive, visual summary of update rollout status across deployment rings. It uses ring-based pie charts to help administrators quickly assess update adoption and device coverage. By default, up to five charts can be displayed at a time. Administrators can use the chart filter to select or deselect rings as needed. If custom rings are configured, one of the existing charts must be deselected to display the custom ring chart.

Default Ring Charts​

The following charts are available by default:

  • Canary Ring: Displays devices that receive updates immediately on release day with no deferral. This ring is typically used for early validation and testing.

  • Early Adopters Ring: Displays devices that receive updates after a 7-day deferral period, allowing limited rollout after initial validation.

  • Broad Rollout Ring: Displays devices that receive updates after a 15-day deferral period, enabling wider deployment once updates are deemed stable.

  • General Availability Ring: Displays devices that receive updates after a 30-day deferral period, representing full-scale deployment across the organization.

  • Devices With No Ring Assigned: Displays all devices that are not currently assigned to any update ring, or whose ring assignment is pending or has failed. Unlike other charts, this chart reflects ring assignment status rather than update installation status.

Chart Status and Update Lifecycle​

All default and custom ring charts display device update status using the following states:

  • Installed – The update has been successfully installed on the device.

  • Pending – The update is approved for the device and is awaiting installation.

  • Failed – The update installation failed on the device.

The Devices With No Ring Assigned chart uses a different set of status values to reflect ring assignment state:

  • Not Assigned – Devices that are not associated with any update ring.

  • Pending – Devices for which ring assignment is in progress.

  • Failed – Devices where ring assignment failed.

Update Flow Across Rings​

When devices are assigned to the Canary Ring and a new Patch Tuesday release becomes available for the selected month:

  • All assigned devices immediately transition to the Pending state.
  • As updates are deployed:
    • Devices move from Pending to Installed upon successful installation.
    • Devices move to Failed if the installation does not complete successfully.
note

For the Early Adopters, Broad Rollout, General Availability, and any custom rings, devices may not immediately appear as Pending even when a Patch Tuesday release is available. This is expected behavior, as these rings follow their configured deferral periods. Devices in these rings remain in an awaiting scheduled installation state until their deferral window elapses.

Devices With No Ring Assigned​

The Devices With No Ring Assigned chart provides administrators with a consolidated, high-level view of devices that are not part of any update strategy. The Not Assigned status highlights devices that have no ring configuration applied, enabling administrators to quickly identify unmanaged or overlooked endpoints and take corrective action.

Interactive Chart Behavior​

All charts in the Overview section are interactive. Clicking on any chart against any category (Installed, Pending, Failed) opens a detailed view that displays a device-level table with the following columns:

  • Device Name
  • Device Model
  • Device Architecture
  • Device Group
  • Status (status of the ring)

The table also provides the following controls:

  • Month Filter Dropdown – Allows selection from the latest three months of Patch Tuesday releases (Filter affects all the default and custom charts except Device with No Ring Assigned)

  • Search – Enables quick filtering of devices by keyword

  • Refresh – Reloads the latest device and update status

note

The Devices With No Ring Assigned chart does not include the month filter dropdown, as it represents ring assignment state rather than update release data.