| Deployment Status | Description
|
| Feature Update | A concatenation of servicing branch (CB, CBB, LTSB) and OS Version (e.g., 1607)
|
| Installed | The number of devices that have reported to be on the given servicing train and feature update.
|
| In progress | The number of devices that have reported to be at some stage in the installation process for the given feature update.
Example: Device X running CB 1507 could be installing CB 1607. In this example, X would count as both **Installed** for **CB 1507** and **In Progress** for **CB 1607**.
|
| Scheduled next 7 days | The total number of devices that are set to have a deferral period expire within 7 days, and after that deferral period expires are targeted to install the given update.
Example: Device Y running CB 1507 could be scheduled to install CB 1607 in 5 days. In this example, X would count as both **Installed** for **CB 1507** and **Scheduled next 7 days** for **CB 1607**
|
| Update Failed | The total number of devices that were **In progress** with the installation for the given feature update, but encountered a failure.
Example: Device X running CB 1507 could be installing CB 1607. X then encounters an error during installation. In this example, X would count as both **Installed** for **CB 1507** and **Update failed** for **CB 1607**, but not as **In progress** for **CB 1607**.
|
| Status Unknown | For devices not using Windows Update to get updates, some information on deployment progress cannot be known. It is possible to know the current installed Feature Update for a device, but not which devices are **In Progress**, **Scheduled next 7 days**, or devices with **Update Failed**.
Devices that Update Compliance knows belongs to your organization, but it does not know update failures or installation progress, will be counted here.
|
## Quality Update Perspective
The Quality Update Deployment Status perspective is a breakdown of the most essential data the user should know about the status of their devices with respect to being Up-to-date. The perspective shows a summary of the organization’s devices for one specific OS version, or build.
### Quality Update Build Summary
The build summary blade attempts to summarize the most important data points to the user for the given build. It is divided into two sections. The first section is a summary of devices for that build – the total number of devices, and the amount that need attention. Each row within the table below is a breakdown of why each device requires attention. The rows can be interacted with to be taken to a larger table view that shows detailed information about all the devices that meet the given criteria. See the following example:
### Quality Update Deferral Configurations
The next blade is the Deferral configuration blade, which shows the WUFB Deferral configurations for all devices that are using WUFB and are reporting to Update Compliance. If no information can be gathered from a device or it is not configured to use WUFB, it will show up as **Not configured (-1)**. See the following example:
### Quality Update Deployment Status
Under the three top-level blades is the deployment status for the newest quality update for the given build. It provides information on the revision number as well as how many days it has been since that revision has been released. See the following example:
See the following table for a description of last reported states for devices deploying that quality update.
| Deployment State | Description
|
| Update Completed | When a device has finished the update process and is on the given update, it will display here as **Update completed**.
|
| In Progress | Devices that are “in progress” installing an update will fall within this category. This category is detailed in the following blade: **Detailed Deployment Status**.
|
| Deferred | If a device’s WUfB deferral policy dictates that it is not set to receive this update, the device will show as Update deferred.
|
| Cancelled | A device will report that the update has been cancelled if the user, at some point, cancelled the update on the device.
|
| Blocked | Devices that are blocked are prevented from proceeding further with the given update. This could be because another update is paused, or some other task on the device must be performed before the update process can proceed.
|
### Quality Update Detailed Deployment Status
This blade provides more detail on the deployment process for the update in the Deployment Status blade. This blade is more of a deployment funnel for devices, enabling you to see at a more granular level how devices are progressing along in their deployment. See the following example:
>Devices that are not managed using Windows Update (Windows Update for Business or otherwise) will not have detailed deployment information.
The following table provides a list of the detailed deployment states a device can report:
| Detailed Deployment State | Description
|
| Update deferred | The WUfB policy of the device dictates the update is deferred.
|
| Pre-Download Tasks Passed | The device has finished all tasks necessary prior to downloading the update.
|
| Download Started | The update has begun downloading on the device.
|
| Download Succeeded | The device has successfully downloaded the update.
|
| Pre-Install Tasks Passed | The device has downloaded the update successfully, and successfully passed all checks prior to beginning installation of the update.
|
| Install Started | The device has begun installing the update.
|
| Reboot Required | The device has finished installing the update, and a reboot is required before the update can be completed.
|
| Reboot Pending | The device is pending a scheduled reboot before the update can be completed.
|
| Reboot Initiated | The device has reported to have initiated the reboot process for completing the update.
|
| Update completed | The device has completed installing, rebooting, and applying the update.
|
## Feature Update Perspective
Like Quality Updates, the Feature Update Deployment Status perspective is a breakdown of information most essential to an administrator. This information is viewed by clicking on a given build on the Feature Update Status blade and then navigating to the **Update Deployment Status** pane as displayed previously. In Update Compliance, a perspective is assigned to a query; the query used to generate the perspective can be altered to show other information, if desired.
Every piece of data shown in this view can be clicked; when clicked, it will alter the query to focus only on the data you need. If the perspective is not meaningful after the query is altered, you can use the other data views like the List and Table.
>After clicking on an OS version from the Feature Update Status blade, the query must fully load the results before you can select the Update Deployment Status perspective.
### Feature Update Build Summary
The Build Summary blade provides a summary for all devices on the given build. It gives a count of all devices, as well as a count of all devices that need attention. Below the counts, you can see why the devices need attention, with a count of devices that fall into each category. See the following example:
### Feature Update Deferral Configuration
This blade shows all deferral configurations for the devices on the given build. See the following example:
Deferral configurations are WUfB-specific, and are shown as days. Some useful information regarding how deferral configurations are shown:
- The devices are grouped based off what their deferral policy is set at. For feature updates, this can be up to 120 days.
- A deferral of zero days means the device has WUfB configured, but is set to not defer the update. These devices will be under “0” for the Update Deferred field.
- Devices that are not configured to use WUfB deferral policies have a “-1” for their deferral days. In this table, the devices will show up as “Not Configured (-1)”.
### Feature Update Deployment Status
As stated earlier in this section, the Feature Updates blade focuses on how Current your devices are. A device is only Current when it is on the latest feature update and quality update Microsoft offers. Thus, the Deployment Status blade displays the deployment status for devices regarding their deployment to the latest feature update. See the following example:
This blade breaks down the main states a device can be in through the deployment of a feature update. The possible states are as follows:
| Deployment State | Description
|
| Update completed | When a device has completely finished the update process and is on the given update, it will show up here as **Update completed**.
|
| Inprogress | Devices “in progress” of installing the given update will fall within this category. This category is iterated on with further granularity in the proceeding blade, “Detailed Deployment Status”.
|
| Update deferred | If a device’s WUfB deferral policy dictates that it is not set to receive this update yet, the device will show as Update deferred.
|
| Cancelled | A device will report that the update has been cancelled if the user, at some point, cancelled the update on the device.
|
| Blocked | Devices that are blocked are prevented from proceeding further with the given update. This could be because another update is paused, or some other task on the device must be performed before the update process can proceed.
|
### Feature Update Detailed Deployment Status
This blade provides more detail on the deployment process for the update in the Deployment Status blade. This blade is more of a deployment funnel for devices, enabling you to see at a more granular level how devices are progressing along in their deployment. See the following example:
The following table displays all states a device can report:
| Detailed Deployment State | Description
|
| Update deferred | The WUfB policy of the device dictates the update is deferred.
|
| Pre-Download Tasks Passed | The device has finished all tasks necessary prior to downloading the update.
|
| Download Started | The update has begun downloading on the device.
|
| Download Succeeded | The device has successfully downloaded the update.
|
| Pre-Install Tasks Passed | The device has downloaded the update successfully, and successfully passed all checks prior to beginning installation of the update.
|
| Install Started | The device has begun installing the update.
|
| Reboot Required | The device has finished installing the update, and a reboot is required before the update can be completed.
|
| Reboot Pending | The device is pending a scheduled reboot before the update can be completed.
|
| Reboot Initiated | The device has reported to have initiated the reboot process for completing the update.
|
| Update completed | The device has completed installing, rebooting, and applying the update.
|
## List of Queries
Operations Management Suite leverages its powerful Log Analytics querying to perform all data calculations. For this blade, we provide examples of queries that show useful data to the user about their organization’s devices. See the following example:
The following **Common queries** are available:
| Query Title | Description
|
| OS Security Update Status | This query provides an all-up view with respect to how many devices are on the latest security update for their OS version. The table will detail an aggregated count of the number of devices, out of the total (so count, or percent) are on the latest security update for their OS build.
|
| Update Deployment Failures | This query provides a chart view, displaying an aggregation of all devices that have reported a deployment failure for either feature or quality updates. The aggregation of the data is on the given update for which a given device has reported a deployment failure.
|
| Devices pending reboot to complete update | This query will provide a table showing all devices that are at the stage of "Reboot Pending" In the update deployment process.
This query will show devices which are in this state for both feature and quality updates; the data will be organized on precisely which update the given device(s) are pending a reboot to install.
|
| Servicing Option Distribution for the devices | This query provides a chart view that aggregates all devices seen by the solution on for each servicing option available for Windows 10 devices (CB, CBB, LTSB)
OS Distribution for the devices This query provides a chart view displaying the distribution of the different editions of Windows 10 that devices seen by the solution are running (e.g., Enterprise, Professional, Education, etc.)
|
| Deferral configurations for Feature Update | This query provides a chart view which displays a breakdown of the different Feature Update deferral configurations through WUfB that the devices seen by the solution are using.
The configuration is in days. 0 days means the device has WUfB deferrals configured, but is not set to defer feature updates. -1 means the device has no feature update deferral policies configured.
|
| Pause configurations for Feature Update | The WUfB policy
|
| Update deferred | This query provides a chart view displaying the breakdown of devices that are either paused, or not paused for feature updates.
“Not configured” means the device is not paused. “Paused” means it is currently paused.
|
| Deferral configurations for Quality Update | This query provides a chart view which displays a breakdown of the different Quality Update deferral configurations through WUfB that the devices seen by the solution are using.
The configuration is in days. 0 days means the device has WUfB deferrals configured, but is not set to defer quality updates. -1 means the device has no quality update deferral policies configured.
|
| Pause configurations for Quality Update | This query provides to a chart view displaying the breakdown of devices that are either paused, or not paused for quality updates.
**Not configured** means the device is not paused. **Paused** means it is currently paused.
|
## Related topics
[Get started with Update Compliance](update-compliance-get-started.md)