deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-28 13:17:23 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

stub

Browse Source
This commit is contained in:
Greg Lindsay 2017-02-07 14:41:10 -08:00
parent d17d1b7d3b
commit 1b14adf8ce
6 changed files with 130 additions and 77 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
windows/manage/TOC.md
View File

@ -20,6 +20,10 @@
### [Prepare servicing strategy for Windows 10 updates](waas-servicing-strategy-windows-10-updates.md)
### [Build deployment rings for Windows 10 updates](waas-deployment-rings-windows-10-updates.md)
### [Assign devices to servicing branches for Windows 10 updates](waas-servicing-branches-windows-10-updates.md)
### [Monitor Windows Updates with Update Compliance](update-compliance-monitor.md)
#### [Get started with Update Compliance](update-compliance-get-started.md)
#### [Using Update Compliance](update-compliance-using.md)
#### [Update Compliance architecture](update-compliance-architecture.md)
### [Optimize update delivery for Windows 10 updates](waas-optimize-windows-10-updates.md)
#### [Configure Delivery Optimization for Windows 10 updates](waas-delivery-optimization.md)
#### [Configure BranchCache for Windows 10 updates](waas-branchcache.md)

26
windows/manage/update-compliance-architecture.md Normal file
View File

@ -0,0 +1,26 @@
---
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
---
# Update Compliance 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.

72
windows/manage/update-compliance-get-started.md Normal file
View File

@ -0,0 +1,72 @@
---
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
 
## 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.  

25
windows/manage/update-compliance-monitor.md Normal file
View File

@ -0,0 +1,25 @@
---
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
 

79
windows/deploy/update-compliance.md → windows/manage/update-compliance-using.md
View File

@ -8,79 +8,10 @@ ms.pagetype: deploy
author: greg-lindsay
---
# Get started with Upgrade Compliance
# Using Update 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.
@ -296,10 +227,4 @@ Pause configurations for Quality Update This query provides to a chart view disp
“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.

1
windows/manage/waas-update-windows-10.md
View File

@ -34,6 +34,7 @@ Windows as a service provides a new way to think about building, deploying, and
| [Prepare servicing strategy for Windows 10 updates](waas-servicing-strategy-windows-10-updates.md) | Explains the decisions you need to make in your servicing strategy. |
| [Build deployment rings for Windows 10 updates](waas-deployment-rings-windows-10-updates.md) | Explains how to make use of servicing branches and update deferrals to manage Windows 10 updates. |
| [Assign devices to servicing branches for Windows 10 updates](waas-servicing-branches-windows-10-updates.md) | Explains how to assign devices to Current Branch (CB) or Current Branch for Business (CBB) for feature and quality updates, and how to enroll devices in Windows Insider. |
| [Monitor Windows Updates with Update Compliance](update-compliance-monitor.md) | Explains how to use Windows Analytics: Update Compliance to monitor and manage Windows Updates on devices in your organization. |
| [Optimize update delivery for Windows 10 updates](waas-optimize-windows-10-updates.md) | Explains the benefits of using Delivery Optimization or BranchCache for update distribution. |
| [Manage updates for Windows 10 Mobile Enterprise and Windows 10 IoT Mobile](waas-mobile-updates.md) | Explains updates for Windows 10 Mobile Enterprise and Windows 10 IoT Mobile. |
| [Manage updates using Windows Update for Business](waas-manage-updates-wufb.md) | Explains how to use Windows Update for Business to manage when devices receive updates directly from Windows Update. Includes walkthroughs for configuring Windows Update for Business using Group Policy and Microsoft Intune. |