How to enroll devices in Desktop Analytics
When you connect Configuration Manager to Desktop Analytics, you configure settings to enroll devices to Desktop Analytics. You can change these settings at any time. Also make sure the devices are up to date.
There are two types of updates that you need to apply for the best experience with Desktop Analytics:
The compatibility component (Appraiser) runs diagnostics on the Windows device to evaluate its compatibility status with the latest versions of the Windows 10.
Microsoft regularly increments the updates for this component, but the associated KB number doesn't change. Make sure that you always have the latest version of the update.
Restart devices after you install the compatibility updates for the first time.
Use Configuration Manager to automatically install the latest version of these updates. For more information, see Deploy software updates.
There's a related optional update, KB 3150513. This update provides updated configuration and definitions for older compatibility updates. For more information, see Latest compatibility definition update for Windows.
Windows 10 includes the compatibility component. To get the latest compatibility update, install the latest Windows 10 cumulative update.
Download the update: KB 2976978
Runs diagnostics on the Windows 8.1 systems that participate in the Windows Customer Experience Improvement Program. These diagnostics help determine whether you might have compatibility issues when upgrading to Windows 10.
For more information, see Compatibility update for keeping Windows up-to-date in Windows 8.1.
Windows 7 with Service Pack 1
Download the update: KB 2952664
Runs diagnostics on the Windows 7 with Service Pack 1 (SP1) systems that participate in the Windows Customer Experience Improvement Program. These diagnostics help determine whether you might have compatibility issues when upgrading to Windows 10.
For more information, see Compatibility update for keeping Windows up-to-date in Windows 7.
Connected User Experiences and Telemetry service
With Windows diagnostic data enabled, the Connected User Experience and Telemetry service (DiagTrack) collects system, application, and driver data. Microsoft analyzes this data, and shares it back to you via Desktop Analytics.
For the best experience, install the following updates depending upon the OS version.
When you install these updates, expect the following behaviors:
- Devices that you enroll to Desktop Analytics show up in the service in less than an hour
- Devices quickly report the status on Windows feature and quality updates
Without these updates, these processes can take over 48 hours for a device to report to Desktop Analytics.
Install the latest Windows 10 cumulative update.
Install the October 2018 monthly rollup, KB4462926
Install the October 2018 monthly rollup, KB4462923
The Desktop Analytics service has no agents to install. Device enrollment requires configuring settings on the devices you want it to monitor. These settings control to which Desktop Analytics instance the device should send its data, and other configuration options.
If you're already using Windows Analytics, use that same workspace for Desktop Analytics. You need to reenroll devices to Desktop Analytics that you previously enrolled in Windows Analytics.
You can only have one Desktop Analytics workspace per Azure AD tenant. Devices can only send diagnostic data to one workspace.
Configuration Manager provides an integrated experience for managing and deploying these settings to clients. For the best experience, use Configuration Manager.
When you connect Configuration Manager to Desktop Analytics, you configure the settings to enroll devices. For more information, see How to connect Configuration Manager with Desktop Analytics.
To change these settings, use the following procedure:
In the Configuration Manager console, go to the Administration workspace, expand Cloud Services, and select the Azure Services node. Select the connection to Desktop Analytics, and choose Properties in the ribbon.
On the Diagnostic Data page, make changes as needed to the following settings:
Commercial ID: this value should automatically populate with your organization's ID. If it doesn't, make sure your proxy server is configured to allow all required endpoints before continuing. Alternatively, retrieve your Commercial ID manually from the Desktop Analytics portal.
Windows 10 diagnostic data level: For more information, see Diagnostic data levels.
Allow Device Name in diagnostic data: For more information, see Device name.
When you make changes to this page, the Available functionality page shows a preview of the Desktop Analytics functionality with the selected diagnostic data settings.
On the Desktop Analytics Connection page, make changes as needed to the following settings:
Display name: The Desktop Analytics portal displays this Configuration Manager connection using this name.
Target collection: This collection includes all devices that Configuration Manager configures with your commercial ID and diagnostic data settings. It's the full set of devices that Configuration Manager connects to the Desktop Analytics service.
Devices in the target collection use a user-authenticated proxy for outbound communication: By default, this value is No. If needed in your environment, set to Yes. For more information, see Proxy server authentication.
Select specific collections to synchronize with Desktop Analytics: Select Add to include additional collections from your Target collection hierarchy. These collections are available in the Desktop Analytics portal for grouping with deployment plans. Make sure to include pilot and pilot exclusion collections.
These collections continue to sync as their membership changes. For example, your deployment plan uses a collection with a Windows 7 membership rule. As those devices upgrade to Windows 10, and Configuration Manager evaluates the collection membership, those devices drop out of the collection and deployment plan.
Configuration Manager sets Windows policies in one or both of the following registry keys:
Local Policy preference:
|CommercialId||Local Policy||Applies to Windows 7, Windows 8.1, and Windows 10: In order for a device to show up in Desktop Analytics, configure it with your organization’s Commercial ID.|
|AllowTelemetry||GPO||Applies to Windows 10: Set
|LimitEnhancedDiagnosticDataWindowsAnalytics||GPO||Applies to Windows 10, version 1803 and later: This setting only applies when the AllowTelemetry setting is
|AllowDeviceNameInTelemetry||GPO||Applies to Windows 10, version 1803 and later: A separate opt-in is required to enable devices to continue to send the device name.
Note: 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". This behavior can make it difficult to identify and assess devices. For more information, see Device name.
|CommercialDataOptIn||Local Policy||Applies to Windows 7 and Windows 8.1: A value of
|RequestAllAppraiserVersions||Both||Applies to Windows 7 and Windows 8.1: A value of
|DisableEnterpriseAuthProxy||GPO||Applies to all Windows versions: 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.
Starting in Windows 10, version 1803, the device name is no longer collected by default. Collecting the device name with the diagnostic data requires a separate opt-in. Without the device name, it's more difficult for you to identify what devices require attention while evaluating an upgrade to a new version of Windows.
If you don't send the device name, it appears in Desktop Analytics as "Unknown".
There's an option in the Configuration Manager settings for Desktop Analytics to configure this option: Allow Device Name in diagnostic data. This Configuration Manager setting controls the Windows policy setting, AllowDeviceNameInTelemetry.
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 only configures the Windows settings if a value doesn't already exist. If you need to configure different settings for a unique group of devices, you can use group policy.
View these settings in the group policy editor at the following path: Computer Configuration > Administrative Templates > Windows Components > Data Collection and Preview Builds. Settings targeted by group policy take precedence over Configuration Manager settings.
If you target Configuration Manager clients with both Windows Analytics and Desktop Analytics settings, the settings for Desktop Analytics take precedence.
When you configure the diagnostic data level, you set the upper boundary for the device. By default in Windows 10, version 1803 and later, users can choose to set a lower level. You can control this behavior using the group policy setting, Configure telemetry opt-in setting user interface. For more information, see Configure Windows diagnostic data in your organization.
Advance to the next article to create deployment plans in Desktop Analytics.