stub topic

windows/deploy/update-compliance.md

@@ -0,0 +1,337 @@
+---
+title: Get started with Update Compliance (Windows 10)
+description: Explains how to get started with Update Compliance.
+ms.prod: w10
+ms.mktglfcycl: deploy
+ms.sitesec: library
+ms.pagetype: deploy
+author: greg-lindsay
+---
+
+# Get started with Upgrade Compliance
+
+## Introduction
+
+With Windows 10, organizations need to change the way they approach monitoring and deploying updates. Update Compliance is a powerful set of tools that enable organizations to monitor and track all important aspects of Microsoft’s new servicing strategy: Windows as a Service.  Update Compliance is a solution built within Operations Management Suite (OMS), a cloud-based monitoring and automation service which has a flexible servicing subscription based off data usage/retention.
+Update Compliance uses the Windows telemetry that is part of all Windows 10 devices. It collects system data including update installation progress, Windows Update for Business (WUfB) configuration data, and other update-specific information, and then sends this data privately to a secure cloud to be stored for analysis and usage within the solution. 
+The main highlights of Update Compliance are:
+•	An overview of your organization’s devices that just works
+•	Dedicated drill-downs for devices that might need attention
+•	An inventory of devices, including the version of Windows they are running and their update status
+•	An overview of WUfB deferral configurations (Windows 10 Anniversary Update [1607] and later)
+•	Powerful built-in Log Analytics to create useful custom queries
+•	Cloud-connected access utilizing Windows 10 telemetry means no need for new complex, customized infrastructure
+ 
+## Update Compliance
+
+This topic explains the necessary steps to set up and prepare your environment for Windows Analytics: Update Compliance. The steps are broken down into sections that follow the recommended setup process:
+1.	Ensuring you meet the prerequisites
+2.	Adding Update Compliance to Microsoft Operations Management Suite
+3.	Deploying your Commercial ID to your organization’s devices
+
+Update Compliance Prerequisites
+There are a few prerequisites for getting the most out of Update Compliance. 
+1)	Update Compliance is only compatible with Windows 10 devices – currently, the solution is only meant to be used with desktop devices (Windows 10 workstations and laptops). 
+2)	The solution requires Windows 10 telemetry to be enabled on all devices that are intended to be seen by the solution. These devices must have at least the basic level of telemetry enabled. To learn more about Windows telemetry, read this article on configuring Windows telemetry in your organization. 
+3)	The telemetry of your organization’s Windows devices must make it to Microsoft. Microsoft has specified endpoints for different aspects of telemetry, which must be whitelisted by your organization so the data can make it to Microsoft. The following table was taken from the article on telemetry endpoints and summarizes what each endpoint is used for:
+Service	Endpoint
+Connected User Experience and Telemetry component	v10.vortex-win.data.microsoft.com
+settings-win.data.microsoft.com
+Windows Error Reporting	watson.telemetry.microsoft.com
+Online Crash Analysis	oca.telemetry.microsoft.com
+
+
+Add Update Compliance to Microsoft Operations Management Suite
+Update Compliance is offered as a solution in the Microsoft Operations Management Suite (OMS), a collection of cloud-based servicing for monitoring and automating your on-premises and cloud environments. For more information about OMS, see Operations Management Suite overview. 
+
+If you are already using OMS, you’ll find Update Compliance in the Solutions Gallery. Select the Update Compliance tile in the gallery and then click Add on the solution's details page. Update Compliance is now visible in your workspace.
+
+If you are not yet using OMS:
+
+
+1.	Go to Operations Management Suite’s page on Microsoft.com and click Sign in.
+
+
+
+2.	Sign in to Operations Management Suite (OMS). You can use either a Microsoft Account or a Work or School account to create a workspace. If your company is already using Azure Active Directory (Azure AD), use a Work or School account when you sign in to OMS. Using a Work or School account allows you to use identities from your Azure AD to manage permissions in OMS.
+
+
+3.	Create a new OMS workspace. 
+
+4.	Enter a name for the workspace, select the workspace region, and provide the email address that you want associated with this workspace. Select Create.
+
+
+5.	If your organization already has an Azure subscription, you can link it to your workspace. Note that you may need to request access from your organization’s Azure administrator. If your organization does not have an Azure subscription, create a new one or select the default OMS Azure subscription from the list. If you do not yet have an Azure subscription, follow this guide to create and link an Azure subscription to an OMS workspace.
+
+
+6.	To add the Update Compliance solution to your workspace, go to the Solutions Gallery. 
+
+7.	Select the Update Compliance tile in the gallery and then select Add on the solution’s details page. Note that you may need to scroll to find Update Compliance. The solution is now visible on your workspace. 
+
+8.	Click the Update Compliance tile to configure the solution. The Settings Dashboard opens.
+
+9.	Click “Subscribe” to subscribe to OMS Update Compliance. You will then need to distribute your Commercial ID across all your organization’s devices. More information on the Commercial ID is provided below.
+
+
+After you are subscribed to OMS Update Compliance and your devices have a Commercial ID, you will begin receiving data. It will typically take 24 hours for the first data to begin appearing. The following section explains how to deploy your Commercial ID to your Windows 10 devices.
+
+
+ 
+Deploy your Commercial ID to your Windows 10 devices
+For your devices to show up in Windows Analytics: Update Compliance, they must be configured with your organization’s Commercial ID. This is so that Microsoft knows that a given device is a member of your organization and to feed that device’s data back to you. There are two primary methods for widespread deployment of your Commercial ID: using Microsoft’s Group Policy (GP) and using Microsoft Mobile Device Management (MDM). 
+
+Using Microsoft Group Policy (GP)
+Deploying your Commercial ID using GP can be accomplished through Microsoft Group Policy Management Console (GPMC), or through an individual device’s Local Group Policy Editor.
+1)	From the user interface, navigate to Computer Configuration > Administrative Templates > Windows Components > Data Collection and Preview Builds
+2)	Double-click Commercial ID
+3)	In the Options box, provide the Commercial ID GUID provided to you, and then click OK.
+
+Using Microsoft Mobile Device Management (MDM)
+Microsoft’s Mobile Device Management can be used to deploy your Commercial ID to your organization’s devices. The Commercial ID is listed under Provider/ProviderID/CommercialID. More information on deployment through MDM can be found here.  
+Use Update Compliance to monitor Windows Updates
+This section details how to use Update Compliance to monitor update compliance and troubleshoot update failures across Windows 10 devices.
+Based on telemetry gathered from user devices, Update Compliance forms an all-up view of your organization, allowing you to maintain a high-level perspective on the progress and status of updates across all your organization’s devices.
+The Update Compliance workflow can be used to quickly identify which devices require attention. It can be used to view and track deployment compliance targets for updates, and it can be used to quickly assess the distribution of Windows 10 devices in your organization.
+Information is refreshed daily so that update progress can be monitored. Changes will be displayed about 24 hours after their occurrence, so you always have a recent snapshot of your devices.
+In OMS, aspects to a given solution's dashboard are typically divided into blades. Blades are a slice of information, typically with a summarization tile and an enumeration of the data that makes up that data. All data is presented through queries. Perspectives are also possible, wherein a given query has a unique view designed to display custom data. The terminology of blades, tiles, and perspectives will be used in the sections that follow. 
+Within Update Compliance, we have these primary blades: 
+1.	OS Update Overview
+2.	Overall Quality Update Status
+3.	Latest and Previous Security Update Status
+4.	Overall Feature Update Status
+5.	CB, CBB, LTSB Deployment Status
+6.	List of Queries
+
+ 
+
+OS Update Overview
+The first blade of OMS Update Compliance is the General OS Update Overview blade. This blade is divided into three sections: Device Summary, Needs Attention Summary, and Device Update Summary.
+
+The Device Summary displays the total number of devices in your organization. These devices have the commercial ID configured, telemetry enabled, and have sent telemetry to Microsoft within the last 28 days. The tile also shows the devices that Need Attention. 
+ 
+Needs Attention Summary
+The Needs Attention Summary summarizes the devices that need attention. Devices that need attention are a subset of your total devices. There are multiple reasons why a device may need attention, so these reasons are categorized and summarized in this tile. This tile is interactive. The user will be taken to a table view showing details about the given device counts. 
+
+Needs Attention	Definition
+
+Out of Support 	Total number of devices that are no longer receiving servicing updates
+Update failed	When a device has reported a failure at some stage in its update deployment process, it will report that the Update Failed. You can click on this to see the full set of devices with more details about the stage at which a failure was reported, when the device reported a failure, and other data.
+
+Missing 2+ Security Updates
+	Total number of devices that are missing two or more security updates
+Update Progress Stalled	Total number of devices where an update installation has been “in progress” for more than 7 days
+
+Needs Attention Categories
+ 
+Update Status Summary
+The update status summary summarizes your organization's devices per Microsoft's new terminology for identifying the status of your device as it fits into the Windows 10 Windows as a Service (WaaS) model. For more information about WaaS, see Microsoft’s overview article on WaaS. This is broken down into Current, Up-to-date, and Not up-to-date. 
+
+Update Status	Definition
+Current and Up-to-date	A device that is current is on the latest and greatest Microsoft offers. It is on the very newest feature update (ex. The Windows Anniversary Update, RS1), on the very latest quality update for its servicing branch.
+Up-to-date	A device that is up-to-date is on the latest quality update for its servicing option (CB, CBB, LTSB), and the device is running an OS that is supported by Microsoft.
+Not up-to-date	A device does not have the latest quality update for its servicing option.  
+
+ 
+Overall Quality Update Status
+OS Quality Update Status is the second blade in Update Compliance. It has a donut data tile and lists the breakdown of the Up-to-date status of devices pivoted on OS version. 
+
+The donut tile offers a summary of all devices in your organization, divided into Up-to-date and Not up-to-date. Recall that devices that are current are also up-to-date.
+
+The list view contains the breakdown of Up-to-date, Not up-to-date, and Update failed -- all pivoted on OS version (e.g., 1507, 1511, 1607). Clicking on any of the rows of this list view will display the OS Quality Update Summary Perspective for that OS version. 
+ 
+ 
+Latest and Previous Security Update Status
+
+We know that security updates are extremely important to your organization, so in addition to an overall view of Quality Updates, we surface deployment status for the latest two security updates specifically, for each supported OS Build Microsoft offers. 
+
+For the latest security update, we show a doughnut chart for the counts – across all OS Builds – how many are installed, in progress/deferred, update failed, or have an unknown status relative to that update. Then, in the two table views below the doughnut, we offer that same breakdown for each OS Build Microsoft supports. Refer to the following definitions for clarifications on what each means.
+Term	Definition
+OS Build	The OS Build + Revision for the OS Version. The build + revision is a one-to-one mapping of the given security update in this context. 
+Version	The OS Version that the OS Build corresponds to.
+Installed	The count of devices that have the given security update installed. In the case that the latest security update is not latest quality update (that is, an update has since released but it did not contain any security fixes), then devices that are on a newer update will also be counted. 
+
+For the Previous security update, a device will show as “Installed” until it has at least installed the Latest security update. 
+In Progress or Deferred	The count of devices that are either currently in the process of installing the given security update, or are deferring the install as per their WUFB policy. 
+
+Note: All devices in this category for Previous Security Update Status are missing 2 or more security updates, and so will qualify as needing attention. 
+Update Failed	The count of devices that were In Progress for the given security update, but failed at some point in the process. They will no longer be shown as “In Progress or deferred” in this case, and only be counted as “Update failed”.
+Status Unknown	If a device should be, in some way, progressing toward this security update, but it’s status cannot be inferred, it will count as “Status Unknown”. Devices not using Windows Update are the most likely devices to fall into this category. 
+
+
+ 
+
+Overall Feature Update Status
+Windows 10 has two main update types: Quality and Feature updates. The third blade in Update Compliance provides the most essential data about your organization’s devices for feature updates. 
+
+Microsoft has developed terms to help specify the state of a given device for how it fits into the Windows as a Service (WaaS) model. There are three update states for a device: Current, Up-to-date, and Not up-to-date. Refer to the Update Status Summary section for definitions of these terms. 
+
+This blade focuses around whether your devices are Current or not. 
+The devices are broken down by their OS Version (e.g., 1607), with a count as to how many are Current, how many are Not Current, and how many have Update Failures. Clicking on any of these will allow you to view all those devices, as well as select the “Update Deployment Status” perspective, shown and explained below. 
+CB, CBB, LTSB Deployment Status
+Following the overview of with respect to how Current your organization’s devices are, there are three tables that show feature update deployment for all devices. The devices are split up by which branch they are on, as this directly impacts whether they are supported (for example, 1607 may be supported under CBB, but not under CB). This allows you a quick glance at how deployment is progressing across your organization with respect to feature updates.
+
+
+The three tables break down devices by Feature update. For each OS version, the following columns provide counts of the various states they can be in:
+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. 
+
+ 
+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)”.
+ 
+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. What follows is a table of all the last reported states of 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 “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. Devices that are not managed using Windows Update (Windows Update for Business or otherwise) will not have detailed deployment information. 
+Here listed are all states a device may report: 
+
+Detailed Deployment State	Description
+Update deferred	The WUfB policy of the device dictates the update is deferred.
+PreDownloadTasksPassed	The device has finished all tasks necessary prior to downloading the update.
+DownloadStarted	The update has begun downloading on the device.
+DownloadSucceeded	The device has successfully downloaded the update.
+PreInstallTasksPassed	The device has downloaded the update successfully, and successfully passed all checks prior to beginning installation of the update.
+InstallStarted	The device has begun installing the update.
+RebootRequired	The device has finished installing the update, and a reboot is required before the update can be completed.
+RebootPending	The device is pending a scheduled reboot before the update can be completed.
+RebootInitiated	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. 
+Detailed Deployment Status categories
+
+
+
+
+ 
+Feature Update Perspective
+
+Like Quality Updates, the Feature Update Deployment Status perspective is a breakdown of information most essential to the user. 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 above. 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. 
+
+
+
+
+
+ 
+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. 
+Feature Update Deferral Configuration
+
+This blade shows all deferral configurations for the devices on the given build. 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 focused 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. 
+The 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.
+Deployment Status categories
+ 
+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. 
+Here listed are all states a device may report: 
+
+Detailed Deployment State	Description
+Update deferred	The WUfB policy of the device dictates the update is deferred.
+PreDownloadTasksPassed	The device has finished all tasks necessary prior to downloading the update.
+DownloadStarted	The update has begun downloading on the device.
+DownloadSucceeded	The device has successfully downloaded the update.
+PreInstallTasksPassed	The device has downloaded the update successfully, and successfully passed all checks prior to beginning installation of the update.
+InstallStarted	The device has begun installing the update.
+RebootRequired	The device has finished installing the update, and a reboot is required before the update can be completed.
+RebootPending	The device is pending a scheduled reboot before the update can be completed.
+RebootInitiated	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. 
+Detailed Deployment Status categories 
+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. 
+
+
+The following are the ‘Common queries’, with a description of the data provided:
+
+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	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.
+
+
+
+Appendix
+Architecture
+
+The following diagram summarizes the general flow of data between your devices and Update Compliance.
+
+After enabling Windows telemetry on your Windows 10 devices and ensuring that they are assigned your Commercial ID, (1) user computers send computer, application and driver telemetry data to a secure Microsoft data center through the Microsoft Data Management Service (2). After you configure Update Compliance, telemetry data is analyzed by the Update Compliance Service (3) and pushed to your OMS workspace (4). You can then use the Update Compliance solution (5) to view Update compliance, track update deployment progress and troubleshoot matters that need your attention. 
+