Merge remote-tracking branch 'refs/remotes/origin/master' into atp-FEB

This commit is contained in:
Joey Caparas
2017-02-09 17:33:33 -08:00
3 changed files with 11 additions and 1 deletions

View File

@ -112,3 +112,6 @@ In order for your devices to show up in Windows Analytics: Update Compliance, th
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).
## Related topics
[Use Update Compliance to monitor Windows Updates](update-compliance-using.md)

View File

@ -50,4 +50,7 @@ These steps are illustrated in following diagram:
>This process assumes that Windows telemetry is enabled and devices are assigned your Commercial ID.
## Related topics
[Get started with Update Compliance](update-compliance-get-started.md)<BR>
[Use Update Compliance to monitor Windows Updates](update-compliance-using.md)

View File

@ -348,3 +348,7 @@ OS Distribution for the devices This query provides a chart view displaying the
<TR><TD>Deferral configurations for Quality Update<TD>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.<BR><BR>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.
<TR><TD>Pause configurations for Quality Update<TD>This query provides to a chart view displaying the breakdown of devices that are either paused, or not paused for quality updates.<BR><BR>**Not configured** means the device is not paused. **Paused** means it is currently paused.
</TABLE>
## Related topics
[Get started with Update Compliance](update-compliance-get-started.md)