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

This commit is contained in:
jdeckerMS 2017-02-15 07:01:46 -08:00
commit 2335cacf34
2 changed files with 16 additions and 3 deletions

View File

@ -26,8 +26,8 @@ This section addresses issues that might arise as you use the Windows Defender A
If you encounter a server error when trying to access the service, youll need to change your browser cookie settings. If you encounter a server error when trying to access the service, youll need to change your browser cookie settings.
Configure your browser to allow cookies. Configure your browser to allow cookies.
### Data is missing on the portal ### Elements or data missing on the portal
If data is missing on the Windows Defender ATP portal its possible that proxy settings are blocking it. If some UI elements or data is missing on the Windows Defender ATP portal its possible that proxy settings are blocking it.
Make sure that `*.securitycenter.windows.com` is included the proxy whitelist. Make sure that `*.securitycenter.windows.com` is included the proxy whitelist.

View File

@ -109,7 +109,20 @@ In order for your devices to show up in Windows Analytics: Update Compliance, th
3. In the **Options** box, under **Commercial Id**, type the Commercial ID GUID, and then click **OK**.<P> 3. In the **Options** box, under **Commercial Id**, type the Commercial ID GUID, and then click **OK**.<P>
- Using Microsoft Mobile Device Management (MDM)<BR><BR> - Using Microsoft Mobile Device Management (MDM)<BR><BR>
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). 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).
For information on how to use MDM configuration CSPs, see [Introduction to configuration service providers (CSPs) for IT pros](https://technet.microsoft.com/en-us/itpro/windows/manage/how-it-pros-can-use-configuration-service-providers).
When using the Intune console, you can use the OMA-URI settings of a [custom policy](https://go.microsoft.com/fwlink/p/?LinkID=616316) to configure the commercial ID. The OMA-URI (case sensitive) path for configuring the commerical ID is: <PRE>./Vendor/MSFT/DMClient/Provider/ProviderID/CommercialID</PRE>
For example, you can use the following values in **Add or edit OMA-URI Setting**:
**Setting Name**: Windows Analytics Commercial ID<BR>
**Setting Description**: Configuring commercial id for Windows Analytics solutions<BR>
**Data Type**: String<BR>
**OMA-URI (case sensitive)**: ./Vendor/MSFT/DMClient/Provider/ProviderID/CommercialID<BR>
**Value**: \<Use the GUID shown on the Windows Telemetry tab in your OMS workspace\><BR>
## Related topics ## Related topics