mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-16 02:43:43 +00:00
edits for diag data wufbr
This commit is contained in:
@ -7,7 +7,7 @@ author: mestew
|
||||
ms.author: mstewart
|
||||
ms.localizationpriority: medium
|
||||
ms.topic: article
|
||||
ms.date: 12/22/2022
|
||||
ms.date: 03/08/2023
|
||||
ms.technology: itpro-updates
|
||||
---
|
||||
|
||||
@ -22,7 +22,8 @@ This article is targeted at configuring devices enrolled to [Microsoft Intune](/
|
||||
1. Wait for data to populate. The length of this process depends on the computer being on, connected to the internet, and correctly configured. Some data types take longer to appear than others. For more information, see [Use Windows Update for Business reports](wufb-reports-use.md).
|
||||
|
||||
> [!TIP]
|
||||
> If you need to troubleshoot client enrollment, consider deploying the [configuration script](#deploy-the-configuration-script) as a Win32 app to a few devices and reviewing the logs it creates. Additional checks are performed with the script to ensure devices are correctly configured.
|
||||
> - If you need to troubleshoot client enrollment, consider deploying the [configuration script](#deploy-the-configuration-script) as a Win32 app to a few devices and reviewing the logs it creates. Additional checks are performed with the script to ensure devices are correctly configured.
|
||||
> - Intune provides compliance reports and they have their own prerequisites for use. The number of devices that appear in the Intune reports may also vary from the Windows Update for Business reports. For more information, see [Intune compliance reports for updates](/mem/intune/protect/compliance-reports).
|
||||
|
||||
## Create a configuration profile
|
||||
|
||||
@ -34,23 +35,30 @@ Create a configuration profile that will set the required policies for Windows U
|
||||
|
||||
1. In the [Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431), go to **Devices** > **Windows** > **Configuration profiles**.
|
||||
1. On the **Configuration profiles** view, select **Create profile**.
|
||||
1. Select **Platform**="Windows 10 and later" and **Profile type**="Settings Catalog", and then select **Create**.
|
||||
1. You're now on the Configuration profile creation screen. On the **Basics** tab, give a **Name** and **Description**.
|
||||
1. On the **Configuration settings** page, you'll be adding multiple settings from the **System** category. Using the **Settings picker**, select the **System** category, then add the following settings and values:
|
||||
1. Required settings for Windows Update for Business reports:
|
||||
- **Setting**: Allow Commercial Data Pipeline
|
||||
- **Value**: Enabled
|
||||
- **Setting**: Allow Telemetry
|
||||
- **Value**: Basic (*Basic is the minimum value, but it can be safely set to a higher value*)
|
||||
- **Setting**: Allow Update Compliance Processing
|
||||
- **Value**: Enabled
|
||||
1. Recommended settings, but not required:
|
||||
- **Setting**: Configure Telemetry Opt In Settings Ux
|
||||
- **Value**: Disabled (*By turning this setting on you are disabling the ability for a user to potentially override the diagnostic data level of devices such that data won't be available for those devices in Windows Update for Business reports*)
|
||||
- **Setting**: Configure Telemetry Opt In Change Notification
|
||||
- **Value**: Disabled (*By turning this setting on you are disabling notifications of diagnostic data changes*)
|
||||
- **Setting**: Allow device name to be sent in Windows diagnostic data (*If this policy is disabled, the device name won't be sent and won't be visible in Windows Update for Business reports*)
|
||||
1. Select the following options, then select **Create**:
|
||||
- **Platform**: Windows 10 and later
|
||||
- **Profile type**: Settings Catalog
|
||||
1. You're now on the Configuration profile creation page. On the **Basics** tab, provide a **Name** and **Description** for the profile.
|
||||
1. On the **Configuration settings** page, you'll add multiple settings from the **System** category. Using the **Settings picker**, select the **System** category.
|
||||
1. Add the following required settings and values the **System** category:
|
||||
- **Setting**: Allow Telemetry
|
||||
- **Value**: Basic
|
||||
- Basic is the minimum value, but it can be safely set to a higher values
|
||||
|
||||
1. Add the following recommended settings and values from the **System** category:
|
||||
> [!Note]
|
||||
> These settings aren't required, but they're recommended to ensure that users of the device cannot override the diagnostic data level of the device.
|
||||
- **Setting**: Configure Telemetry Opt In Settings Ux
|
||||
- **Value**: Disabled
|
||||
- By turning this setting on you are disabling the ability for a user to potentially override the diagnostic data level of devices such that data won't be available for those devices in Windows Update for Business reports
|
||||
|
||||
- **Setting**: Configure Telemetry Opt In Change Notification
|
||||
- **Value**: Disabled
|
||||
- By turning this setting on you are disabling notifications of diagnostic data changes
|
||||
|
||||
- **Setting**: Allow device name to be sent in Windows diagnostic data
|
||||
- **Value**: Allowed
|
||||
- If this policy is disabled, the device name won't be sent and won't be visible in Windows Update for Business reports
|
||||
|
||||
1. Continue through the next set of tabs **Scope tags**, **Assignments**, and **Applicability Rules** to assign the configuration profile to devices you wish to enroll.
|
||||
1. Review the settings and then select **Create**.
|
||||
@ -64,37 +72,36 @@ Create a configuration profile that will set the required policies for Windows U
|
||||
1. You're now on the Configuration profile creation screen. On the **Basics** tab, give a **Name** and **Description**.
|
||||
1. On the **Configuration settings** page, you'll be adding multiple OMA-URI Settings that correspond to the policies described in [Manually configuring devices for Windows Update for Business reports](wufb-reports-configuration-manual.md).
|
||||
|
||||
1. Add a setting to **Allow commercial data pipeline**; this policy is required for Windows Update for Business reports:
|
||||
- **Name**: Allow commercial data pipeline
|
||||
- **Description**: Configures Microsoft to be the processor of the Windows diagnostic data collected from an Azure Active Directory-joined device.
|
||||
- **OMA-URI**: `./Vendor/MSFT/Policy/Config/System/AllowCommercialDataPipeline`
|
||||
- **Data type**: Integer
|
||||
- **Value**: 1
|
||||
**Required settings**:
|
||||
|
||||
1. Add a setting configuring the **Windows Diagnostic Data level** for devices:
|
||||
- **Name**: Allow Telemetry
|
||||
- **Description**: Sets the maximum allowed diagnostic data to be sent to Microsoft, required for Windows Update for Business reports.
|
||||
- **OMA-URI**: `./Vendor/MSFT/Policy/Config/System/AllowTelemetry`
|
||||
- **Data type**: Integer
|
||||
- **Value**: 1 (*1 is the minimum value meaning basic, but it can be safely set to a higher value*).
|
||||
1. Add a setting to **Allow Update Compliance processing**; this policy is required for Windows Update for Business reports:
|
||||
- **Name**: Allow Update Compliance Processing
|
||||
- **Description**: Opts device data into Update Compliance processing. Required to see data.
|
||||
- **OMA-URI**: `./Vendor/MSFT/Policy/Config/System/AllowUpdateComplianceProcessing`
|
||||
- **Data type**: Integer
|
||||
- **Value**: 16
|
||||
1. (*Recommended, but not required*) Add settings for **disabling devices' Diagnostic Data opt-in settings interface**. If these aren't disabled, users of each device can potentially override the diagnostic data level of devices such that data won't be available for those devices in Windows Update for Business reports:
|
||||
- **Value**: 1
|
||||
- *1 is the minimum value meaning basic, but it can be safely set to a higher value.*
|
||||
|
||||
**Recommended settings, but not required**:
|
||||
|
||||
1. Add settings for **Disabling devices' Diagnostic Data opt-in settings interface**. If these aren't disabled, users of each device can potentially override the diagnostic data level of devices such that data won't be available for those devices in Windows Update for Business reports:
|
||||
- **Name**: Disable Telemetry opt-in interface
|
||||
- **Description**: Disables the ability for end users of devices can adjust diagnostic data to levels lower than defined by the Allow Telemetry setting.
|
||||
- **OMA-URI**: `./Vendor/MSFT/Policy/Config/System/ConfigureTelemetryOptInSettingsUx`
|
||||
- **Data type**: Integer
|
||||
- **Value**: 1
|
||||
1. (*Recommended, but not required*) Add a setting to **Allow device name in diagnostic data**; otherwise, the device name won't be in Windows Update for Business reports:
|
||||
1. Add a setting to **Allow device name in diagnostic data**; otherwise, the device name won't be in Windows Update for Business reports:
|
||||
- **Name**: Allow device name in Diagnostic Data
|
||||
- **Description**: Allows device name in Diagnostic Data.
|
||||
- **OMA-URI**: `./Vendor/MSFT/Policy/Config/System/AllowDeviceNameInDiagnosticData`
|
||||
- **Data type**: Integer
|
||||
- **Value**: 1
|
||||
|
||||
1. Add a setting to **Configure Telemetry Opt In Change Notification**. Diagnostic data opt-in change notifications won't appear when changes occur.
|
||||
- **Name**: Configure Telemetry Opt In Change Notification
|
||||
- **Description**: Disables Telemetry Opt In Change Notification
|
||||
- **OMA-URI**: `./Vendor/MSFT/Policy/Config/System/ConfigureTelemetryOptInChangeNotification`
|
||||
- **Data type**: Integer
|
||||
- **Value**: 1
|
||||
|
||||
1. Continue through the next set of tabs **Scope tags**, **Assignments**, and **Applicability Rules** to assign the configuration profile to devices you wish to enroll.
|
||||
1. Review the settings and then select **Create**.
|
||||
|
Reference in New Issue
Block a user