Group policy settings for Desktop Analytics
Applies to: Configuration Manager (current branch)
This article details the local and group policy settings in Windows that Configuration Manager and Desktop Analytics use.
When Configuration Manager enrolls devices into Desktop Analytics, it sets Windows policies to configure the device. In most circumstances, only use Configuration Manager to configure these settings.
Configuration Manager sets Windows policies in one or both of the following registry keys:
Group policy object (GPO):
Local policy preference:
|CommercialId||Local||All Windows versions||In order for a device to show up in Desktop Analytics, configure it with your organization's Commercial ID.|
|LimitEnhancedDiagnosticDataWindowsAnalytics||GPO||Windows 10, version 1803 and later||This setting only applies when the AllowTelemetry setting is
|AllowDeviceNameInTelemetry||GPO||Windows 10, version 1803 and later||Enable devices to send the device name. The device name isn't sent to Microsoft by default. If you don't send the device name, it appears in Desktop Analytics as "Unknown". For more information, see Device name.|
|CommercialDataOptIn||Local||Windows 8.1 and earlier||Desktop Analytics requires a value of
|RequestAllAppraiserVersions||Both||Windows 8.1 and earlier||Desktop Analytics requires a value of
|DisableEnterpriseAuthProxy||GPO||All Windows versions||If your environment requires a user-authenticated proxy with Windows Integrated Authentication for internet access, Desktop Analytics requires a value of
In most circumstances, only use Configuration Manager to configure these settings. Don't also apply these settings in domain group policy objects. For more information, see Conflict resolution.
Settings from Upgrade Readiness
Windows Analytics also set the following policies through the Upgrade Readiness script:
If you ran the Upgrade Readiness onboarding script on a device, these policy settings may still exist. Don't use the legacy script. Before you enroll the device to Desktop Analytics, remove these previous policy settings.
Group policy settings
In general, use Configuration Manager collections to target Desktop Analytics settings and enrollment. Use direct membership or queries to include or exclude devices from the collection. For more information, see How to create collections.
Configuration Manager configures commercial ID and diagnostic data settings on your target collection. If you need to configure different diagnostic data settings for different group of devices, use group policy settings to override Configuration Manager settings. For example, you need to set Optional (limited) level for some devices and Required for others. Some devices may have different proxy server authentication settings.
The relevant group policy settings are at the following path: Computer Configuration > Administrative Templates > Windows Components > Data Collection and Preview Builds.
Group policy settings only modify registry settings in the following key:
When you use group policy settings to enable complex scenarios, pay special attention to policy settings that can cause configuration conflicts. Configuration Manager only configures Windows settings if the value doesn't already exist. Group policy settings take precedence over Configuration Manager settings, so certain group policy configurations could cause issues with Desktop Analytics.
Group policy settings that could conflict with Configuration Manager settings for Desktop Analytics
The group policy settings in the following table have the greatest potential to cause conflict with the Windows settings that Configuration Manager sets on devices it enrolls to Desktop Analytics:
|Display name||Registry value||Effect on devices enrolled in Desktop Analytics|
|Configure the Commercial ID||CommercialId||If you set this policy to a different value, it overrides the Commercial ID set by Configuration Manager. If it's not the same ID, configured devices may not appear in Desktop Analytics.|
|Allow telemetry||AllowTelemetry||If you set this policy to a different value, it overrides the global diagnostic data level that you set in Configuration Manager for the target collection.|
|Limit Enhanced diagnostic data to the minimum required by Windows Analytics||LimitEnhancedDiagnosticDataWindowsAnalytics||This policy is dependent upon the prior AllowTelemetry setting. Depending upon the level you set in Configuration Manager or with group policy, this policy can change the diagnostic data level on the device to Enhanced or Enhanced (Limited). This policy only applies if AllowTelemetry is set to
|Allow device name to be sent in Windows diagnostic data||AllowDeviceNameInTelemetry||If you opt-in to send device names in Configuration Manager, you can override it by configuring this policy to Disabled. When you disable this setting, device names appear as "Unknown" in Desktop Analytics. For more information, see Device name.|
|Configure Authenticated Proxy usage for the Connected User Experience and Telemetry service||DisableEnterpriseAuthProxy||If you configure Configuration Manager devices to use user-authenticated proxy (
The legacy policy Configure Connected User Experiences and Telemetry (TelemetryProxy) allows Windows to forward diagnostic data to a dedicated proxy, instead of using the user (WinINET) or device (WinHTTP) proxy. Some Windows components don't support this policy. If you use this policy, it may cause data quality issues in Desktop Analytics.
Behavior of disabled settings
If you configure these group policy settings to Disabled, it has different effects on system behavior.
When you disable the CommercialId policy, Windows removes the registry value. The Configuration Manager setting for the commercial ID, which is set in the local policy registry path, then applies to the device.
For policies that Configuration Manager sets in the same registry location as group policy, when you disable the setting in group policy, Windows removes the registry value. Configuration Manager will set it again on its next policy processing cycle, and then Windows will remove it on the next group policy refresh. This constant change in configuration may cause undesired behaviors with Desktop Analytics.
- If you set these group policy settings to Not configured, Windows removes the value once but doesn't continue to remove it. This configuration lets Configuration Manager apply its values as expected.
Group policy settings to customize the user experience
These group policy settings aren't required by Configuration Manager or Desktop Analytics. You can configure them in group policy to configure your users' experience with Windows diagnostic data.
|Display name||Registry value||Effect on devices enrolled in Desktop Analytics|
|Configure telemetry opt-in change notifications||DisableTelemetryOptInChangeNotification||Starting in Windows 10, version 1803, Windows notifies users when the diagnostic data level changes. Use this policy to disable notifications.|
|Configure telemetry opt-in setting user interface||DisableTelemetryOptInSettingsUx||When you configure the diagnostic data level, you set the upper boundary for the device. Starting in Windows 10, version 1803, users can set a lower level. Use this policy to prevent users from changing the diagnostic level. For more information, see Configure Windows diagnostic data in your organization.|
|Disable deleting diagnostic data||DisableDeviceDelete||Starting in Windows 10, version 1809, users can delete diagnostic data from the Diagnostic & feedback settings page. Use this policy to prevent the deletion of diagnostic data that Microsoft collects from the device.|
|Disable diagnostic data viewer||DisableDiagnosticDataViewer||Starting in Windows 10, version 1809, users can enable and open the Diagnostic Data Viewer from the Diagnostic & feedback settings page. Use this policy to disable the Diagnostic Data Viewer in Windows settings, and prevent it from showing diagnostic data that Microsoft collects from the device.|