mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 18:33:43 +00:00
Merge branch 'rs4' of https://cpubwin.visualstudio.com/_git/it-client into DOupdates
This commit is contained in:
jaimeo
@ -13,6 +13,10 @@ ms.date: 03/27/2018
|
||||
# Delivery Optimization in Update Compliance
|
||||
The Update Compliance solution of Windows Analytics provides you with information about your Delivery Optimization configuration, including the observed bandwidth savings across all devices that used peer-to-peer distribution over the past 28 days.
|
||||
|
||||
>[!Note]
|
||||
>Delivery Optimization Status is currently in development. See the [Known Issues](#known-issues) section for issues we are aware of and potential workarounds.
|
||||
|
||||
|
||||
## Delivery Optimization Status
|
||||
|
||||
The Delivery Optimization Status section includes three blades:
|
||||
@ -40,3 +44,8 @@ The download sources that could be included are:
|
||||
- Group Bytes: Bytes downloaded from Group Peers which are other devices that belong to the same Group (available when the “Group” download mode is used)
|
||||
- HTTP Bytes: Non-peer bytes. The HTTP download source can be Microsoft Servers, Windows Update Servers, a WSUS server or an SCCM Distribution Point for Express Updates.
|
||||
|
||||
## Known Issues
|
||||
Delivery Optimization is currently in development. The following issues are known:
|
||||
|
||||
- DO Download Mode is not accurately portrayed in the Device Configuration blade. There is no workaround at this time.
|
||||
|
||||
|
||||
@ -8,12 +8,12 @@ ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
author: jaimeo
|
||||
ms.author: jaimeo
|
||||
ms.date: 04/03/2018
|
||||
ms.date: 04/05/2018
|
||||
---
|
||||
|
||||
# Frequently asked questions and troubleshooting Windows Analytics
|
||||
|
||||
This topic compiles the most common issues encountered with configuring and using Windows Analytics, as well as general questions.
|
||||
This topic compiles the most common issues encountered with configuring and using Windows Analytics, as well as general questions. This FAQ, along with the [Windows Analytics Technical Community](https://techcommunity.microsoft.com/t5/Windows-Analytics/ct-p/WindowsAnalytics), are recommended resources to consult before contacting Microsoft support.
|
||||
|
||||
## Troubleshooting common problems
|
||||
|
||||
@ -219,46 +219,6 @@ Beyond the cost of Windows operating system licenses, there is no additional cos
|
||||
Note that different Azure Log Analytics plans have different data retention periods, and the Windows Analytics solutions inherit the workspace's data retention policy. So, for example, if your workspace is on the free plan then Windows Analytics will retain the last week's worth of "daily snapshots" that are collected in the workspace.
|
||||
|
||||
|
||||
### How does Windows Analytics support privacy?
|
||||
|
||||
Windows Analytics is fully committed to privacy, centering on these tenets:
|
||||
|
||||
- **Transparency:** We fully document the Windows Analytics diagnostic events (see the links for additional information) so you can review them with your company’s security and compliance teams. The Diagnostic Data Viewer lets you see diagnostic data sent from a given device (see [Diagnostic Data Viewer Overview](https://docs.microsoft.com/windows/configuration/diagnostic-data-viewer-overview) for details).
|
||||
- **Control:** You ultimately control the level of diagnostic data you wish to share. In Windows 10 1709 we added a new policy to Limit enhanced diagnostic data to the minimum required by Windows Analytics
|
||||
- **Security:** Your data is protected with strong security and encryption
|
||||
- **Trust:** Windows Analytics supports the Microsoft Online Service Terms
|
||||
|
||||
The following illustration shows how diagnostic data flows from individual devices through the Diagnostic Data Service, Azure Log Analytics storage, and to your Log Analytics workspace:
|
||||
|
||||
[](images/WA-data-flow-v1.png)
|
||||
|
||||
The data flow sequence is as follows:
|
||||
|
||||
1. Diagnostic data is sent from devices to the Microsoft Diagnostic Data Management service, which is hosted in the US.
|
||||
2. An IT administrator creates an Azure Log Analytics workspace. The administrator chooses the location, copies the Commercial ID (which identifies that workspace), and then pushes Commercial ID to devices they want to monitor. This is the mechanism that specifies which devices appear in which workspaces.
|
||||
3. Each day Microsoft produces a "snapshot" of IT-focused insights for each workspace in the Diagnostic Data Management service.
|
||||
4. These snapshots are copied to transient storage which is used only by Windows Analytics (also hosted in US data centers) where they are segregated by Commercial ID.
|
||||
5. The snapshots are then copied to the appropriate Azure Log Analytics workspace.
|
||||
6. If the IT administrator is using the Upgrade Readiness solution, user input from the IT administrator (specifically, the target operating system release and the importance and upgrade readiness per app) is stored in the Windows Analytics Azure Storage. (Upgrade Readiness is the only Windows Analytics solution that takes such user input.)
|
||||
|
||||
|
||||
See these topics for additional background information about related privacy issues:
|
||||
|
||||
- [Configure Windows diagnostic data in your organization](https://docs.microsoft.com/windows/configuration/configure-windows-diagnostic-data-in-your-organization)
|
||||
- [Windows 7, Windows 8, and Windows 8.1 Appraiser Telemetry Events, and Fields](https://go.microsoft.com/fwlink/?LinkID=822965) (link downloads a PDF file)
|
||||
- [Windows 10, version 1703 basic level Windows diagnostic events and fields](https://docs.microsoft.com/windows/configuration/basic-level-windows-diagnostic-events-and-fields-1703)
|
||||
- [Windows 10, version 1709 enhanced diagnostic data events and fields used by Windows Analytics](https://docs.microsoft.com/windows/configuration/enhanced-diagnostic-data-windows-analytics-events-and-fields)
|
||||
- [Diagnostic Data Viewer Overview](https://docs.microsoft.com/windows/configuration/diagnostic-data-viewer-overview)
|
||||
- [Licensing Terms and Documentation](https://www.microsoftvolumelicensing.com/DocumentSearch.aspx?Mode=3&DocumentTypeId=31)
|
||||
- [Learn about security and privacy at Microsoft datacenters](http://www.microsoft.com/datacenters)
|
||||
- [Confidence in the trusted cloud](https://azure.microsoft.com/en-us/support/trust-center/)
|
||||
|
||||
### Can Windows Analytics be used without a direct client connection to the Microsoft Data Management Service?
|
||||
No, the entire service is powered by Windows diagnostic data, which requires that devices have this direct connectivity.
|
||||
|
||||
### Can I choose the data center location?
|
||||
Yes for Azure Log Analytics, but no for the Microsoft Data Management Service (which is hosted in the US).
|
||||
|
||||
### Why do SCCM and Upgrade Readiness show different counts of devices that are ready to upgrade?
|
||||
System Center Configuration Manager (SCCM) considers a device ready to upgrade if *no installed app* has an upgrade decision of “not ready” (that is, they are all "ready" or "in progress"), while Upgrade Readiness considers a device ready to upgrade only if *all* installed apps are marked “ready”.
|
||||
|
||||
|
||||
@ -127,7 +127,6 @@ Use a software distribution system such as System Center Configuration Manager t
|
||||
|
||||
### Distributing policies at scale
|
||||
There are a number of policies that can be centrally managed to control Windows Analytics device configuration. All of these policies have *preference* registry key equivalents that can be set by using the deployment script. Policy settings override preference settings if both are set.
|
||||
|
||||
>[!NOTE]
|
||||
>You can only set the diagnostic data level to Enhanced by using policy. For example, this is necessary for using Device Health.
|
||||
|
||||
@ -155,4 +154,10 @@ For more information about Internet Explorer Security Zones, see [About URL Secu
|
||||
|
||||
### Distribution at scale without using the deployment script
|
||||
|
||||
We recommend using the deployment script to configure devices. However if this is not an option, you can still manage settings by policy as described in the previous section. However, if you don't run the deployment script, you might have to wait a long time (possibly weeks) before devices send the initial full inventory scan.
|
||||
We recommend using the deployment script to configure devices. However if this is not an option, you can still manage settings by policy as described in the previous section. However, if you don't run the deployment script, you won't benefit from its error checking, and you might have to wait a long time (possibly weeks) before devices send the initial full inventory scan.
|
||||
|
||||
Note that it is possible to intiate a full inventory scan on a device by calling these commands:
|
||||
- CompatTelRunner.exe -m:generaltel.dll -f:DoCensusRun
|
||||
- CompatTelRunner.exe -m:appraiser.dll -f:DoScheduledTelemetryRun ent
|
||||
|
||||
For details on how to run these and how to check results, see the deployment script.
|
||||
|
||||
52
windows/deployment/update/windows-analytics-privacy.md
Normal file
52
windows/deployment/update/windows-analytics-privacy.md
Normal file
@ -0,0 +1,52 @@
|
||||
---
|
||||
title: Windows Analytics and privacy
|
||||
description: How Windows Analytics uses data
|
||||
keywords: windows analytics, oms, privacy, data, diagnostic, operations management suite, prerequisites, requirements, updates, upgrades, log analytics, health, FAQ, problems, troubleshooting, error
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
author: jaimeo
|
||||
ms.author: jaimeo
|
||||
ms.date: 04/05/2018
|
||||
---
|
||||
|
||||
# Windows Analytics and privacy
|
||||
|
||||
Windows Analytics is fully committed to privacy, centering on these tenets:
|
||||
|
||||
- **Transparency:** We fully document the Windows Analytics diagnostic events (see the links for additional information) so you can review them with your company’s security and compliance teams. The Diagnostic Data Viewer lets you see diagnostic data sent from a given device (see [Diagnostic Data Viewer Overview](https://docs.microsoft.com/windows/configuration/diagnostic-data-viewer-overview) for details).
|
||||
- **Control:** You ultimately control the level of diagnostic data you wish to share. In Windows 10 1709 we added a new policy to Limit enhanced diagnostic data to the minimum required by Windows Analytics
|
||||
- **Security:** Your data is protected with strong security and encryption
|
||||
- **Trust:** Windows Analytics supports the Microsoft Online Service Terms
|
||||
|
||||
The following illustration shows how diagnostic data flows from individual devices through the Diagnostic Data Service, Azure Log Analytics storage, and to your Log Analytics workspace:
|
||||
|
||||
[](images/WA-data-flow-v1.png)
|
||||
|
||||
The data flow sequence is as follows:
|
||||
|
||||
1. Diagnostic data is sent from devices to the Microsoft Diagnostic Data Management service, which is hosted in the US.
|
||||
2. An IT administrator creates an Azure Log Analytics workspace. The administrator chooses the location, copies the Commercial ID (which identifies that workspace), and then pushes Commercial ID to devices they want to monitor. This is the mechanism that specifies which devices appear in which workspaces.
|
||||
3. Each day Microsoft produces a "snapshot" of IT-focused insights for each workspace in the Diagnostic Data Management service.
|
||||
4. These snapshots are copied to transient storage which is used only by Windows Analytics (also hosted in US data centers) where they are segregated by Commercial ID.
|
||||
5. The snapshots are then copied to the appropriate Azure Log Analytics workspace.
|
||||
6. If the IT administrator is using the Upgrade Readiness solution, user input from the IT administrator (specifically, the target operating system release and the importance and upgrade readiness per app) is stored in the Windows Analytics Azure Storage. (Upgrade Readiness is the only Windows Analytics solution that takes such user input.)
|
||||
|
||||
|
||||
See these topics for additional background information about related privacy issues:
|
||||
|
||||
- [Configure Windows diagnostic data in your organization](https://docs.microsoft.com/windows/configuration/configure-windows-diagnostic-data-in-your-organization)
|
||||
- [Windows 7, Windows 8, and Windows 8.1 Appraiser Telemetry Events, and Fields](https://go.microsoft.com/fwlink/?LinkID=822965) (link downloads a PDF file)
|
||||
- [Windows 10, version 1703 basic level Windows diagnostic events and fields](https://docs.microsoft.com/windows/configuration/basic-level-windows-diagnostic-events-and-fields-1703)
|
||||
- [Windows 10, version 1709 enhanced diagnostic data events and fields used by Windows Analytics](https://docs.microsoft.com/windows/configuration/enhanced-diagnostic-data-windows-analytics-events-and-fields)
|
||||
- [Diagnostic Data Viewer Overview](https://docs.microsoft.com/windows/configuration/diagnostic-data-viewer-overview)
|
||||
- [Licensing Terms and Documentation](https://www.microsoftvolumelicensing.com/DocumentSearch.aspx?Mode=3&DocumentTypeId=31)
|
||||
- [Learn about security and privacy at Microsoft datacenters](http://www.microsoft.com/datacenters)
|
||||
- [Confidence in the trusted cloud](https://azure.microsoft.com/en-us/support/trust-center/)
|
||||
|
||||
### Can Windows Analytics be used without a direct client connection to the Microsoft Data Management Service?
|
||||
No, the entire service is powered by Windows diagnostic data, which requires that devices have this direct connectivity.
|
||||
|
||||
### Can I choose the data center location?
|
||||
Yes for Azure Log Analytics, but no for the Microsoft Data Management Service (which is hosted in the US).
|
||||
Reference in New Issue
Block a user