mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 13:27:23 +00:00
Merge pull request #7851 from mestew/eudb
Eudb diag data changes-7269562
This commit is contained in:
Meghan Stewart
GitHub
commit
7bf02353b1
@ -1,9 +1,9 @@
|
||||
---
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
manager: dougeby
|
||||
ms.prod: w10
|
||||
ms.collection: M365-modern-desktop
|
||||
manager: aaroncz
|
||||
ms.technology: itpro-updates
|
||||
ms.prod: windows-client
|
||||
ms.topic: include
|
||||
ms.date: 08/18/2022
|
||||
ms.localizationpriority: medium
|
||||
|
||||
@ -1,9 +1,9 @@
|
||||
---
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
manager: dougeby
|
||||
ms.prod: w10
|
||||
ms.collection: M365-modern-desktop
|
||||
manager: aaroncz
|
||||
ms.technology: itpro-updates
|
||||
ms.prod: windows-client
|
||||
ms.topic: include
|
||||
ms.date: 04/06/2022
|
||||
ms.localizationpriority: medium
|
||||
|
||||
@ -1,9 +1,9 @@
|
||||
---
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
manager: dougeby
|
||||
ms.prod: w10
|
||||
ms.collection: M365-modern-desktop
|
||||
manager: aaroncz
|
||||
ms.technology: itpro-updates
|
||||
ms.prod: windows-client
|
||||
ms.topic: include
|
||||
ms.date: 08/18/2022
|
||||
ms.localizationpriority: medium
|
||||
|
||||
@ -2,8 +2,8 @@
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
manager: aaroncz
|
||||
ms.prod: w10
|
||||
ms.collection: M365-modern-desktop
|
||||
ms.technology: itpro-updates
|
||||
ms.prod: windows-client
|
||||
ms.topic: include
|
||||
ms.date: 12/05/2022
|
||||
ms.localizationpriority: medium
|
||||
@ -11,4 +11,5 @@ ms.localizationpriority: medium
|
||||
<!--This file is shared by all Update Compliance v1 articles. -->
|
||||
|
||||
> [!Important]
|
||||
> Update Compliance is [deprecated](/windows/whats-new/deprecated-features) and is no longer accepting new onboarding requests. Update Compliance has been replaced by [Windows Update for Business reports](..\wufb-reports-overview.md). If you're currently using Update Compliance, you can continue to use it, but you can't change your `CommercialID`. Support for Update Compliance will end on March 31, 2023 when the service will be [retired](/windows/whats-new/feature-lifecycle#terminology).
|
||||
> - Update Compliance is [deprecated](/windows/whats-new/deprecated-features) and is no longer accepting new onboarding requests. Update Compliance has been replaced by [Windows Update for Business reports](..\wufb-reports-overview.md). If you're currently using Update Compliance, you can continue to use it, but you can't change your `CommercialID`. Support for Update Compliance will end on March 31, 2023 when the service will be [retired](/windows/whats-new/feature-lifecycle#terminology).
|
||||
> - Changes have been made to the Windows diagnostic data processor configuration. For more information, see [Windows diagnostic data processor changes](/windows/deployment/update/windows-diagnostic-data-processor-changes).
|
||||
|
||||
@ -1,9 +1,9 @@
|
||||
---
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
manager: dougeby
|
||||
ms.prod: w10
|
||||
ms.collection: M365-modern-desktop
|
||||
manager: aaroncz
|
||||
ms.technology: itpro-updates
|
||||
ms.prod: windows-client
|
||||
ms.topic: include
|
||||
ms.date: 08/18/2022
|
||||
ms.localizationpriority: medium
|
||||
|
||||
@ -1,9 +1,9 @@
|
||||
---
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
manager: dougeby
|
||||
ms.prod: w10
|
||||
ms.collection: M365-modern-desktop
|
||||
manager: aaroncz
|
||||
ms.technology: itpro-updates
|
||||
ms.prod: windows-client
|
||||
ms.topic: include
|
||||
ms.date: 08/10/2022
|
||||
ms.localizationpriority: medium
|
||||
|
||||
@ -53,6 +53,7 @@ Open `RunConfig.bat` and configure the following (assuming a first-run, with `ru
|
||||
[!INCLUDE [Update Compliance script error codes](./includes/wufb-reports-script-error-codes.md)]
|
||||
|
||||
## Verify device configuration
|
||||
<!--Using include for verifying device configuration-->
|
||||
[!INCLUDE [Endpoints for Update Compliance](./includes/wufb-reports-verify-device-configuration.md)]:
|
||||
|
||||
<!--Using include for verifying device configuration-->
|
||||
[!INCLUDE [Endpoints for Update Compliance](./includes/wufb-reports-verify-device-configuration.md)]
|
||||
|
||||
|
||||
@ -17,6 +17,10 @@ ms.date: 12/31/2017
|
||||
- Windows 10
|
||||
- Windows 11
|
||||
|
||||
<!--Using include for recommending Windows Update for Business reports for all Update Compliance v1 docs-->
|
||||
[!INCLUDE [Recommend Windows Update for Business reports](./includes/wufb-reports-recommend.md)]
|
||||
|
||||
|
||||
Update Compliance is fully committed to privacy, centering on these tenets:
|
||||
|
||||
- **Transparency:** Windows client diagnostic data events that are required for Update Compliance's operation are fully documented (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](/windows/configuration/diagnostic-data-viewer-overview) for details).
|
||||
|
||||
@ -7,7 +7,7 @@ author: mestew
|
||||
ms.author: mstewart
|
||||
ms.localizationpriority: medium
|
||||
ms.topic: article
|
||||
ms.date: 11/15/2022
|
||||
ms.date: 02/10/2023
|
||||
ms.technology: itpro-updates
|
||||
---
|
||||
|
||||
@ -43,10 +43,6 @@ Open `RunConfig.bat` and configure the following (assuming a first-run, with `ru
|
||||
1. Examine the logs for any issues. If there are no issues, then all devices with a similar configuration and network profile are ready for the script to be deployed with `runMode=Deployment`.
|
||||
1. If there are issues, gather the logs and provide them to Microsoft Support.
|
||||
|
||||
## Verify device configuration
|
||||
|
||||
<!--Using include for verifying device configuration-->
|
||||
[!INCLUDE [Endpoints for Windows Update for Business reports](./includes/wufb-reports-verify-device-configuration.md)]
|
||||
|
||||
## Script errors
|
||||
|
||||
|
||||
@ -6,7 +6,7 @@ ms.prod: windows-client
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
ms.topic: article
|
||||
ms.date: 11/15/2022
|
||||
ms.date: 02/10/2023
|
||||
ms.technology: itpro-updates
|
||||
---
|
||||
|
||||
@ -87,11 +87,6 @@ To share feedback about the Microsoft Learn platform, see [Microsoft Learn feedb
|
||||
|
||||
Use the following troubleshooting tips to resolve the most common problems when using Windows Update for Business reports:
|
||||
|
||||
### Verify client configuration
|
||||
|
||||
<!--Using include for verifying device configuration-->
|
||||
[!INCLUDE [Endpoints for Windows Update for Business reports](./includes/wufb-reports-verify-device-configuration.md)]
|
||||
|
||||
### Ensuring devices are configured correctly to send data
|
||||
|
||||
The first step in troubleshooting Windows Update for Business reports is ensuring that devices are configured. Review [Manually configuring devices for Windows Update for Business reports](wufb-reports-configuration-manual.md) for the settings. We recommend using the [Windows Update for Business reports configuration script](wufb-reports-configuration-script.md) for troubleshooting and configuring devices.
|
||||
|
||||
@ -6,7 +6,7 @@ ms.prod: windows-client
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
ms.topic: article
|
||||
ms.date: 11/15/2022
|
||||
ms.date: 02/14/2023
|
||||
ms.technology: itpro-updates
|
||||
---
|
||||
|
||||
@ -49,19 +49,26 @@ Windows Update for Business reports supports Windows client devices on the follo
|
||||
- General Availability Channel
|
||||
- Windows Update for Business reports *counts* Windows Insider Preview devices, but doesn't currently provide detailed deployment insights for them.
|
||||
|
||||
### Windows operating system updates
|
||||
|
||||
- For [Changes to Windows diagnostic data collection](/windows/privacy/changes-to-windows-diagnostic-data-collection#services-that-rely-on-enhanced-diagnostic-data), installing the January 2023 release preview cumulative update, or a later equivalent update, is recommended
|
||||
|
||||
## Diagnostic data requirements
|
||||
|
||||
At minimum, Windows Update for Business reports requires devices to send diagnostic data at the *Required* level (previously *Basic*). Some queries in Windows Update for Business reports require devices to send diagnostic data at the following levels:
|
||||
At minimum, Windows Update for Business reports requires devices to send diagnostic data at the *Required* level (previously *Basic*). For more information about what's included in different diagnostic levels, see [Diagnostics, feedback, and privacy in Windows](https://support.microsoft.com/windows/diagnostics-feedback-and-privacy-in-windows-28808a2b-a31b-dd73-dcd3-4559a5199319).
|
||||
|
||||
- *Optional* level (previously *Full*) for Windows 11 devices
|
||||
For some queries, such as Windows 11 eligibility reporting, Windows Update for Business reports requires devices to send diagnostic data at the following levels:
|
||||
|
||||
- *Optional* level for Windows 11 devices (previously *Full*)
|
||||
- *Enhanced* level for Windows 10 devices
|
||||
|
||||
> [!Note]
|
||||
> Device names don't appear in Windows Update for Business reports unless you individually opt-in devices by using policy. The configuration script does this for you, but when using other client configuration methods, set one of the following to display device names:
|
||||
> - CSP: System/[AllowDeviceNameInDiagnosticData](/windows/client-management/mdm/policy-csp-system#system-allowdevicenameindiagnosticdata)
|
||||
> - Group Policy: **Allow device name to be sent in Windows diagnostic data** under **Computer Configuration\Administrative Templates\Windows Components\Data Collection and Preview Builds**
|
||||
Device names don't appear in Windows Update for Business reports unless you individually opt-in devices by using a policy. The configuration script does this for you, but when using other client configuration methods, set one of the following to display device names:
|
||||
|
||||
For more information about what's included in different diagnostic levels, see [Diagnostics, feedback, and privacy in Windows](https://support.microsoft.com/windows/diagnostics-feedback-and-privacy-in-windows-28808a2b-a31b-dd73-dcd3-4559a5199319).
|
||||
|
||||
- CSP: System/[AllowDeviceNameInDiagnosticData](/windows/client-management/mdm/policy-csp-system#system-allowdevicenameindiagnosticdata)
|
||||
- Group Policy: **Allow device name to be sent in Windows diagnostic data** under **Computer Configuration\Administrative Templates\Windows Components\Data Collection and Preview Builds**
|
||||
|
||||
Microsoft is committed to providing you with effective controls over your data and ongoing transparency into our data handling practices. For more information about data handling and privacy for Windows diagnostic data, see [Configure Windows diagnostic data in your organization](/windows/privacy/configure-windows-diagnostic-data-in-your-organization) and [Changes to Windows diagnostic data collection](/windows/privacy/changes-to-windows-diagnostic-data-collection#services-that-rely-on-enhanced-diagnostic-data).
|
||||
|
||||
## Data transmission requirements
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user