Configure Telemetry for Upgrade Readiness with Intune and SCCM – Part 3 Configuration Manager

Let us learn about Configure Telemetry for Upgrade Readiness with Intune and SCCM – Part 3 Configuration Manager. In this post, we will cover different methods to configure Telemetry

Telemetry is required for Windows Analytics solutions like Upgrade Readiness. Below are the 4 levels of Telemetry. The amount of data gathered from each telemetry level is different, as shown below.

In this blog post, we will cover different methods to configure Telemetry. You will get the latest information on Cloud PC Monitoring Health Performance Using Endpoint Analytics Intune.

This is a series of posts as listed below.

1. Define Windows 10 Upgrade Readiness Architecture with SCCM – Part 1
2. How to integrate Windows 10 Upgrade Readiness with SCCM – Part 2
3. Configure Telemetry for Upgrade Analytics/Readiness with Intune & SCCM – Part 3

Following are the contents covered in this post

• Telemetry Table
• Enable Telemetry using Upgrade Readiness Deployment Script
• Enable Telemetry using Windows 10 CSP for Intune
• Enable Telemetry using Group policy
• Enable Telemetry using SCCM Client Agent

Telemetry Table

The following is the latest information. The information given in the table is outdated.

0 – Not allowed. 1 – Allowed, except for Secondary Data Requests. 2 (default) – Allowed.

Level	Data gathered	Value
Security	Security data only	0
Basic	Security data, and basic system and quality data	1
Enhanced	Security data, basic system and quality data, and enhanced insights, and advanced reliability data	2
Full	Security data, basic system and quality data, enhanced insights and advanced reliability data, and full diagnostics data.	3

Enable Telemetry using Upgrade Readiness Deployment Script

• The script will automate the procedures necessary to enable Telemetry.
• Upgrade Readiness/Windows Analytics deployment script is available for download.
• When you run the deployment script, it initiates a full scan. The size of the initial data will be 2 MB. But there, after inventories are deltas.
• “Windows Compatibility Appraiser” Schedule task is responsible for scanning and sending Telemetry data.

• Use a software distribution system such as ConfigMgr for large scale script deployment.
• Refer blog for more details about the Proxy connectivity scenarios.
• Edit the RunConfig.bat to change values such as “LogPath”, “log mode” and “commercialIDValue”.

:: File share to store telemetry logs
set logPath=%SystemDrive%\UADiag
set logPath=%logPath:”=%SystemDrive%\UADiag\Logs

:: Commercial ID provided to you
:: Go to your OMS workspace navigate to path \Settings\Connected Sources\Windows Telemetry
:: Copy COMMERCIAL ID KEY in the above path and replace it in the line below
set commercialIDValue=0202298yuy-q283918i-82739871i8-712387yyu99-189219918yt

:: By Default, script logs to both console and log file.
:: logMode == 0 log to console only
:: logMode == 1 log to file and console
:: logMode == 2 log to file only
set logMode=1

• You can find Commercial ID Value in your OMS workspace. (Settings -> Connected Sources -> Windows Telemetry)

• Edit RunConfig.bat and Customize IE data collection. This setting helps to find IE website compatibility issues.

:: By Default script disables IE data collection
:: To enable it set AllowIEData=IEDataOptIn and set IEOptInLevel
set AllowIEData=IEDataOptIn

::IEOptInLevel=0 Internet Explorer data collection is disabled
::IEOptInLevel=1 Data collection is enabled for sites in the Local intranet + Trusted sites + Machine local zones
::IEOptInLevel=2 Data collection is enabled for sites in the Internet + Restricted sites zones
::IEOptInLevel=3 Data collection is enabled for all sites
set IEOptInLevel=1

• On proxy server or firewall, we need to whitelist Microsoft telemetry endpoints.

• Refer to Blog for more details about the URLs to be whitelisted.
• Windows Analytics/Upgrade Readiness Script creates registry values in below location.

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection

Allow Telemetry ==> 0x00000003(3)
CommercialId ==> 0202298yuy-q283918i-82739871i8-712387yyu99-189219918yt

0 – Not allowed.
1 – Allowed, except for Secondary Data Requests.
2 (default) – Allowed.

Enable Telemetry using Windows 10 CSP for Intune

• Use device management tools like Standalone Intune/Hybrid Intune to deploy below OMA-URI configuration to enable telemetry. More details on Policy CSP and System/AllowTelemetry.

OMA-URI -> ./Vendor/MSFT/Policy/Config/System/AllowTelemetry
Data Type -> Integer
Value -> 3 (this is the value for FULL)

• Use below OMA-URI to configure CommercialID. The following document shows the DMClient configuration service provider in tree format.

OMA-URI – /Vendor/MSFT/DMClient/Provider/ProviderID/CommercialID
Data type – String
Value – 0202298yuy-q283918i-82739871i8-712387yyu99-189219918yt

Enable Telemetry using Group policy

• Navigate to the below Group Policy setting to configure Telemetry and commercial ID.

Policies –> Administrative Template: Policy Definition: Windows Components:
Data Collection and Preview Builds

Allow Telemetry ==> Enabled
Configure the Commercial ID ==> Enabled
Configure Connected User Experiences and Telemetry ==> Not Configured

• GPO creates the below registry on the end user computer.

 Enable Telemetry using SCCM Client Agent

• “Windows Analytics” client agent setting is available from SCCM 1706 onwards

Create NEW – Client Settings – Windows Analytics
Custom Device Settings:-
Manage Windows Telemetry settings with Configuration Manager –> YES
Commercial ID Key –> 0202298yuy-q283918i-82739871i8-712387yyu99-189219918yt
Windows 10 Telemetry –> Full (Depends on your requirement)

• SCCM client agent setting creates below registry on end-user computer.

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection

Allow Telemetry ==> 0x00000003(3)
CommercialId ==> 0202298yuy-q283918i-82739871i8-712387yyu99-189219918yt

References

1. Windows 10 Telemetry CSP

Author

Vimal has more than 10 years of experience in SCCM device management solutions. His main focus is on Device Management technologies like Microsoft Intune, ConfigMgr (SCCM), OS Deployment, and Patch Management. He writes about the technologies like SCCM, Windows 10, Microsoft Intune, and MDT.