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

s

Browse Source
This commit is contained in:
Greg Lindsay 2017-02-07 16:15:18 -08:00
parent a6f5d9c28c
commit fd86eb44fc
3 changed files with 31 additions and 28 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
windows/manage/update-compliance-architecture.md
View File

@ -1,6 +1,6 @@
---
title: Get started with Update Compliance (Windows 10)
description: Explains how to get started with Update Compliance.
title: Update Compliance Architecture (Windows 10)
description: Update Compliance workflow
ms.prod: w10
ms.mktglfcycl: deploy
ms.sitesec: library

45
windows/manage/update-compliance-get-started.md
View File

@ -1,6 +1,6 @@
---
title: Get started with Update Compliance (Windows 10)
description: Explains how to get started with Update Compliance.
description: Explains how to configure Update Compliance.
ms.prod: w10
ms.mktglfcycl: deploy
ms.sitesec: library
@ -9,27 +9,31 @@ 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:
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
## 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
1. Update Compliance is currently only compatible with Windows 10 devices. The solution is intended to be used with desktop devices (Windows 10 workstations and laptops).
2. The solution requires that Windows 10 telemetry is enabled on all devices that are intended to be displayed in 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:
<TABLE BORDER=3>
<TR><TH>Service<TH>Endpoint
<TR><TD>Connected User Experience and Telemetry component <TD>v10.vortex-win.data.microsoft.com
<BR>settings-win.data.microsoft.com
<TR><TD>Windows Error Reporting <TD>watson.telemetry.microsoft.com
<TR><TD>Online Crash Analysis <TD>oca.telemetry.microsoft.com
</TABLE>
## Add Update Compliance to Microsoft Operations Management Suite
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.
@ -57,16 +61,17 @@ If you are not yet using OMS:
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
## 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)
- 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.
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)
- 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.  

10
windows/manage/update-compliance-using.md
View File

@ -1,6 +1,6 @@
---
title: Get started with Update Compliance (Windows 10)
description: Explains how to get started with Update Compliance.
title: Using Update Compliance (Windows 10)
description: Explains how to begin usihg Update Compliance.
ms.prod: w10
ms.mktglfcycl: deploy
ms.sitesec: library
@ -8,9 +8,7 @@ ms.pagetype: deploy
author: greg-lindsay
---
# Using Update Compliance
Use Update Compliance to monitor Windows Updates
# 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.
@ -25,7 +23,7 @@ Within Update Compliance, we have these primary blades:
5. CB, CBB, LTSB Deployment Status
6. List of Queries
OS Update Overview
## 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.