This commit is contained in:
Greg Lindsay
2017-02-08 16:11:56 -08:00
parent e9ba9b7cc7
commit 4d2edb7641
10 changed files with 38 additions and 18 deletions

Binary file not shown.

After

Width:  |  Height:  |  Size: 9.4 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 11 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 50 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 30 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 51 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 29 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 11 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 47 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 47 KiB

View File

@ -40,37 +40,57 @@ If you are already using OMS, youll find Update Compliance in the Solutions G
If you are not yet using OMS, use the following steps to subscribe to OMS Update Compliance:
<TABLE>
<TR><TH>Step<TH>Procedure<TH>Example (click image to view)
<TR><TD VALIGN=top>1<TD VALIGN=top>Go to [Operations Management Suites page](https://www.microsoft.com/en-us/cloud-platform/operations-management-suite) on Microsoft.com and click **Sign in**.<TD><A HREF="images/uc-02.png" onClick="MyWindow=window.open('images/uc-02.png','MyWindow',resizable=yes); return false;"><img src="images/uc-02.png" width="213"></A>
</TABLE>
1. Go to [Operations Management Suites page](https://www.microsoft.com/en-us/cloud-platform/operations-management-suite) on Microsoft.com and click **Sign in**.
<A HREF="images/uc-02.png"><img src="images/uc-02a.png"></A>
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.
<A HREF="images/uc-03.png"><img src="images/uc-03a.png"></A>
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.
<A HREF="images/uc-04.png"><img src="images/uc-04a.png"></A>
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**.
<A HREF="images/uc-05.png"><img src="images/uc-05a.png"></A>
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 organizations 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 solutions 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 organizations devices. More information on the Commercial ID is provided below.
<A HREF="images/uc-06.png"><img src="images/uc-06a.png"></A>
6. To add the Update Compliance solution to your workspace, go to the Solutions Gallery.
<A HREF="images/uc-07.png"><img src="images/uc-07a.png"></A>
7. Select the **Update Compliance** tile in the gallery and then select **Add** on the solutions details page. Note that you may need to scroll to find **Update Compliance**. The solution is now visible on your workspace.
<A HREF="images/uc-08.png"><img src="images/uc-08a.png"></A>
8. Click the **Update Compliance** tile to configure the solution. The **Settings Dashboard** opens.
<A HREF="images/uc-09.png"><img src="images/uc-09a.png"></A>
9. Click **Subscribe** to subscribe to OMS Update Compliance. You will then need to distribute your Commercial ID across all your organizations devices. More information on the Commercial ID is provided below.
<A HREF="images/uc-10.png"><img src="images/uc-10a.png"></A>
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.
>You can unsubscribe from the Update Compliance solution if you no longer want to monitor your organizations devices. User device data will continue to be shared with Microsoft while the opt-in keys are set on user devices and the proxy allows traffic.
## 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 organizations Commercial ID. This is so that Microsoft knows that a given device is a member of your organization and to feed that devices data back to you. There are two primary methods for widespread deployment of your Commercial ID: using Microsofts Group Policy (GP) and using Microsoft Mobile Device Management (MDM).
In order for your devices to show up in Windows Analytics: Update Compliance, they must be configured with your organizations Commercial ID. This is so that Microsoft knows that a given device is a member of your organization and to feed that devices data back to you. There are two primary methods for widespread deployment of your Commercial ID: Group Policy and 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 devices 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 Group Policy
Deploying your Commercial ID using Group Policy can be accomplished by configuring domain Group Policy Objects with the Group Policy Management Editor, or by configuring local Group Policy with the Local Group Policy Editor.
1. In the console tree, navigate to **Computer Configuration** > **Administrative Templates** > **Windows Components** > **Data Collection and Preview Builds**
2. Double-click **Configure the Commercial ID**
3. In the **Options** box, under **Commercial Id**, type the Commercial ID GUID, and then click **OK**.
- Using Microsoft Mobile Device Management (MDM)
Microsofts Mobile Device Management can be used to deploy your Commercial ID to your organizations devices. The Commercial ID is listed under Provider/ProviderID/CommercialID. More information on deployment through MDM can be found here.
Microsofts Mobile Device Management can be used to deploy your Commercial ID to your organizations devices. The Commercial ID is listed under **Provider/ProviderID/CommercialID**. More information on deployment using MDM can be found [here](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/dmclient-csp).