mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-19 20:33:42 +00:00
Merge branch 'main' into ADO-8098862
This commit is contained in:
Gary Moore
GitHub
@ -15,7 +15,7 @@ metadata:
|
||||
author: aczechowski
|
||||
ms.author: aaroncz
|
||||
manager: aaroncz
|
||||
ms.date: 03/07/2022 #Required; mm/dd/yyyy format.
|
||||
ms.date: 12/22/2023 #Required; mm/dd/yyyy format.
|
||||
localization_priority: medium
|
||||
|
||||
# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
|
||||
|
||||
@ -161,7 +161,7 @@ Starting in Windows 10, version 1803, set this policy to restrict peer selection
|
||||
- 4 = DNS Suffix
|
||||
- 5 = Starting with Windows 10, version 1903, you can use the Microsoft Entra tenant ID as a means to define groups. To do this set the value for DOGroupIdSource to its new maximum value of 5.
|
||||
|
||||
When set, the Group ID is assigned automatically from the selected source. If you set this policy, the GroupID policy is ignored. The default behavior, when the GroupID or GroupIDSource policies aren't set, is to determine the Group ID using AD Site (1), Authenticated domain SID (2) or Microsoft Entra tenant ID (5), in that order. If GroupIDSource is set to either DHCP Option ID (3) or DNS Suffix (4) and those methods fail, the default behavior is used instead. The option set in this policy only applies to Group (2) download mode. If Group (2) isn't set as Download mode, this policy will be ignored. If you set the value to anything other than 0-5, the policy is ignored.
|
||||
When set, the Group ID will be assigned automatically from the selected source. This policy is ignored if the GroupID policy is also set. The default behavior, when the GroupID or GroupIDSource policies aren't set, is to determine the Group ID using AD Site (1), Authenticated domain SID (2) or Microsoft Entra tenant ID (5), in that order. If GroupIDSource is set to either DHCP Option ID (3) or DNS Suffix (4) and those methods fail, the default behavior is used instead. The option set in this policy only applies to Group (2) download mode. If Group (2) isn't set as Download mode, this policy will be ignored. If you set the value to anything other than 0-5, the policy is ignored.
|
||||
|
||||
### Minimum RAM (inclusive) allowed to use Peer Caching
|
||||
|
||||
@ -335,7 +335,7 @@ The device can download from peers while on battery regardless of this policy.
|
||||
|
||||
MDM Setting: **DOCacheHost**
|
||||
|
||||
Set this policy to designate one or more Microsoft Connected Cache servers to be used by Delivery Optimization. You can set one or more FQDNs or IP Addresses that are comma-separated, for example: myhost.somerandomhost.com,myhost2.somerandomhost.com,10.10.1.7. **By default, this policy has no value.** Delivery Optimization client will connect to the listed Microsoft Connected Cache servers in the order as they are listed. When multiple FQDNs or IP Addresses are listed, the Microsoft Connected Cache server priority order is determined based on the order as they are listed. If the first server fails, it will move the the next one. When the last server fails, it will fallback to the CDN.
|
||||
Set this policy to designate one or more Microsoft Connected Cache servers to be used by Delivery Optimization. You can set one or more FQDNs or IP Addresses that are comma-separated, for example: myhost.somerandomhost.com,myhost2.somerandomhost.com,10.10.1.7. **By default, this policy has no value.** Delivery Optimization client will connect to the listed Microsoft Connected Cache servers in the order as they are listed. When multiple FQDNs or IP Addresses are listed, the Microsoft Connected Cache server priority order is determined based on the order as they are listed. If the first server fails, it will move the next one. When the last server fails, it will fallback to the CDN.
|
||||
|
||||
>[!IMPORTANT]
|
||||
> Any value will signify that the policy is set. For example, an empty string ("") isn't considered empty.
|
||||
|
||||
@ -59,7 +59,7 @@ The following table lists the minimum Windows 10 version that supports Delivery
|
||||
| Edge Browser Updates | Windows 10 1809, Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| Configuration Manager Express updates| Windows 10 1709 + Configuration Manager version 1711, Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| Dynamic updates| Windows 10 1903, Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| MDM Agent | Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
|
||||
| MDM Agent | Windows 11 | :heavy_check_mark: | | |
|
||||
| Xbox Game Pass (PC) | Windows 10 1809, Windows 11 | :heavy_check_mark: | | :heavy_check_mark: |
|
||||
| Windows Package Manager| Windows 10 1809, Windows 11 | :heavy_check_mark: | | |
|
||||
| MSIX Installer| Windows 10 2004, Windows 11 | :heavy_check_mark: | | |
|
||||
|
||||
@ -1,104 +1,180 @@
|
||||
### YamlMime:Landing
|
||||
### YamlMime:Hub
|
||||
|
||||
title: Windows client deployment resources and documentation # < 60 chars
|
||||
summary: Learn about deploying and keeping Windows client devices up to date. # < 160 chars
|
||||
title: Deploy and update Windows # < 60 chars; shows at top of hub page
|
||||
summary: Learn about deploying and updating Windows client devices in your organization. # < 160 chars
|
||||
|
||||
metadata:
|
||||
title: Windows client deployment resources and documentation # Required; page title displayed in search results. Include the brand. < 60 chars.
|
||||
description: Learn about deploying Windows and keeping it up to date in your organization. # Required; article description that is displayed in search results. < 160 chars.
|
||||
ms.topic: landing-page
|
||||
ms.technology: itpro-deploy
|
||||
title: Windows client deployment documentation # Required; browser tab title displayed in search results. Include the brand. < 60 chars.
|
||||
description: Learn about deploying and updating Windows client devices in your organization. # Required; article description that is displayed in search results. < 160 chars.
|
||||
ms.topic: hub-page
|
||||
ms.prod: windows-client
|
||||
ms.technology: itpro-deploy
|
||||
ms.collection:
|
||||
- highpri
|
||||
- tier1
|
||||
author: frankroj
|
||||
ms.author: frankroj
|
||||
author: aczechowski
|
||||
ms.author: aaroncz
|
||||
manager: aaroncz
|
||||
ms.date: 10/31/2022
|
||||
ms.date: 12/20/2023
|
||||
localization_priority: medium
|
||||
|
||||
# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
|
||||
|
||||
landingContent:
|
||||
# Cards and links should be based on top customer tasks or top subjects
|
||||
# Start card title with a verb
|
||||
# Card (optional)
|
||||
- title: Plan
|
||||
linkLists:
|
||||
- linkListType: overview
|
||||
links:
|
||||
- text: Create a deployment plan
|
||||
url: update/create-deployment-plan.md
|
||||
- text: Define readiness criteria
|
||||
url: update/plan-define-readiness.md
|
||||
- text: Evaluate infrastructure and tools
|
||||
url: update/eval-infra-tools.md
|
||||
- text: Define your servicing strategy
|
||||
url: update/plan-define-strategy.md
|
||||
# common graphics: https://review.learn.microsoft.com/content-production-service/internal/image-gallery?branch=main
|
||||
|
||||
# Card (optional)
|
||||
- title: Prepare
|
||||
linkLists:
|
||||
- linkListType: how-to-guide
|
||||
productDirectory:
|
||||
title: Get started
|
||||
items:
|
||||
- title: Plan
|
||||
imageSrc: /media/common/i_overview.svg
|
||||
links:
|
||||
- text: Plan for Windows 11
|
||||
url: /windows/whats-new/windows-11-plan?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json
|
||||
- text: Create a deployment plan
|
||||
url: update/create-deployment-plan.md
|
||||
- text: Define readiness criteria
|
||||
url: update/plan-define-readiness.md
|
||||
- text: Define your servicing strategy
|
||||
url: update/plan-define-strategy.md
|
||||
- text: Determine application readiness
|
||||
url: update/plan-determine-app-readiness.md
|
||||
- text: Plan for volume activation
|
||||
url: volume-activation/plan-for-volume-activation-client.md
|
||||
|
||||
- title: Prepare
|
||||
imageSrc: /media/common/i_tasks.svg
|
||||
links:
|
||||
- text: Prepare for Windows 11
|
||||
url: /windows/whats-new/windows-11-prepare?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json
|
||||
- text: Prepare to deploy Windows updates
|
||||
url: update/prepare-deploy-windows.md
|
||||
- text: Prepare updates using Windows Update for Business
|
||||
url: update/waas-manage-updates-wufb.md
|
||||
- text: Evaluate and update infrastructure
|
||||
url: update/update-policies.md
|
||||
- text: Set up Delivery Optimization for Windows client updates
|
||||
url: do/waas-delivery-optimization-setup.md?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json
|
||||
- text: Prepare for imaging with Configuration Manager
|
||||
url: deploy-windows-cm/prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md
|
||||
|
||||
- title: Deploy
|
||||
imageSrc: /media/common/i_deploy.svg
|
||||
links:
|
||||
- text: Deploy Windows with Autopilot
|
||||
url: /mem/autopilot/tutorial/autopilot-scenarios
|
||||
- text: Assign devices to servicing channels
|
||||
url: update/waas-servicing-channels-windows-10-updates.md
|
||||
- text: Deploy updates with Intune
|
||||
url: update/deploy-updates-intune.md
|
||||
- text: Deploy Windows updates with Configuration Manager
|
||||
url: update/deploy-updates-configmgr.md
|
||||
- text: Upgrade Windows using Configuration Manager
|
||||
url: deploy-windows-cm/upgrade-to-windows-10-with-configuration-manager.md
|
||||
- text: Check release health
|
||||
url: update/check-release-health.md
|
||||
|
||||
additionalContent:
|
||||
sections:
|
||||
- title: Solutions
|
||||
items:
|
||||
|
||||
- title: Windows Autopilot
|
||||
links:
|
||||
- text: Prepare to deploy Windows updates
|
||||
url: update/prepare-deploy-windows.md
|
||||
- text: Prepare updates using Windows Update for Business
|
||||
- text: Overview
|
||||
url: /mem/autopilot/windows-autopilot
|
||||
- text: Scenarios
|
||||
url: /mem/autopilot/tutorial/autopilot-scenarios
|
||||
- text: Device registration
|
||||
url: /mem/autopilot/registration-overview
|
||||
- text: Learn more about Windows Autopilot >
|
||||
url: /mem/autopilot
|
||||
|
||||
- title: Windows Autopatch
|
||||
links:
|
||||
- text: What is Windows Autopatch?
|
||||
url: windows-autopatch/overview/windows-autopatch-overview.md
|
||||
- text: Frequently asked questions (FAQ)
|
||||
url: windows-autopatch/overview/windows-autopatch-faq.yml
|
||||
- text: Prerequisites
|
||||
url: windows-autopatch/prepare/windows-autopatch-prerequisites.md
|
||||
- text: Learn more about Windows Autopatch >
|
||||
url: windows-autopatch/index.yml
|
||||
|
||||
- title: Windows Update for Business
|
||||
links:
|
||||
- text: What is Windows Update for Business?
|
||||
url: update/waas-manage-updates-wufb.md
|
||||
- text: Prepare for Zero Touch Installation of Windows 10 with Configuration Manager
|
||||
url: deploy-windows-cm/prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md
|
||||
- text: Set up Delivery Optimization for Windows client updates
|
||||
- text: Windows Update for Business deployment service
|
||||
url: update/deployment-service-overview.md
|
||||
- text: Manage Windows Update settings
|
||||
url: update/waas-wu-settings.md
|
||||
- text: Windows Update for Business reports overview
|
||||
url: update/wufb-reports-overview.md
|
||||
|
||||
- title: Optimize and cache content
|
||||
links:
|
||||
- text: What is Delivery Optimization?
|
||||
url: do/waas-delivery-optimization.md
|
||||
- text: What is Microsoft Connected Cache?
|
||||
url: do/waas-microsoft-connected-cache.md
|
||||
- text: Frequently asked questions
|
||||
url: do/waas-delivery-optimization-faq.yml
|
||||
- text: Learn more about Delivery Optimization >
|
||||
url: do/index.yml
|
||||
|
||||
# Card (optional)
|
||||
- title: Deploy
|
||||
linkLists:
|
||||
- linkListType: deploy
|
||||
- title: In-place upgrade and imaging
|
||||
links:
|
||||
- text: Deploy Windows 10 with Autopilot
|
||||
url: /mem/autopilot
|
||||
- text: Assign devices to servicing channels
|
||||
url: update/waas-servicing-channels-windows-10-updates.md
|
||||
|
||||
# Card
|
||||
- title: Overview
|
||||
linkLists:
|
||||
- linkListType: overview
|
||||
links:
|
||||
- text: What's new in Windows deployment
|
||||
url: deploy-whats-new.md
|
||||
- text: Windows 11 overview
|
||||
url: /windows/whats-new/windows-11
|
||||
- text: Windows client deployment scenarios
|
||||
url: windows-10-deployment-scenarios.md
|
||||
- text: Basics of Windows updates, channels, and tools
|
||||
url: update/get-started-updates-channels-tools.md
|
||||
- text: Overview of Windows Autopilot
|
||||
url: /mem/autopilot/windows-autopilot
|
||||
- text: Upgrade Windows using Configuration Manager
|
||||
url: deploy-windows-cm/upgrade-to-windows-10-with-configuration-manager.md
|
||||
- text: Deploy a Windows image using Configuration Manager
|
||||
url: deploy-windows-cm/refresh-a-windows-7-client-with-windows-10-using-configuration-manager.md
|
||||
- text: Convert a disk from MBR to GPT
|
||||
url: mbr-to-gpt.md
|
||||
- text: Resolve Windows upgrade errors
|
||||
url: upgrade/resolve-windows-10-upgrade-errors.md
|
||||
|
||||
# Card
|
||||
- title: Support remote work
|
||||
linkLists:
|
||||
- linkListType: concept
|
||||
- title: Licensing and activation
|
||||
links:
|
||||
- text: Deploy Windows 10 for a remote world
|
||||
url: https://techcommunity.microsoft.com/t5/windows-it-pro-blog/deploying-a-new-version-of-windows-10-in-a-remote-world/ba-p/1419846
|
||||
- text: Empower remote workers with Microsoft 365
|
||||
url: /microsoft-365/solutions/empower-people-to-work-remotely
|
||||
- text: Top 12 tasks for security teams to support working from home
|
||||
url: /microsoft-365/security/top-security-tasks-for-remote-work
|
||||
- text: Support your remote workforce
|
||||
url: /microsoftteams/faq-support-remote-workforce
|
||||
- text: Plan for volume activation
|
||||
url: volume-activation/plan-for-volume-activation-client.md
|
||||
- text: Subscription activation
|
||||
url: windows-10-subscription-activation.md
|
||||
- text: Volume activation management tool (VAMT)
|
||||
url: volume-activation/introduction-vamt.md
|
||||
- text: Activate using key management service (KMS)
|
||||
url: volume-activation/activate-using-key-management-service-vamt.md
|
||||
- text: Windows commercial licensing overview
|
||||
url: /windows/whats-new/windows-licensing
|
||||
|
||||
# Card (optional)
|
||||
- title: Microsoft Learn training
|
||||
linkLists:
|
||||
- linkListType: learn
|
||||
- title: More resources
|
||||
items:
|
||||
|
||||
- title: Release and lifecycle
|
||||
links:
|
||||
- text: Plan to deploy updates for Windows 10 and Microsoft 365 Apps
|
||||
url: /training/modules/windows-plan
|
||||
- text: Prepare to deploy updates for Windows 10 and Microsoft 365 Apps
|
||||
url: /training/modules/windows-prepare/
|
||||
- text: Deploy updates for Windows 10 and Microsoft 365 Apps
|
||||
url: /training/modules/windows-deploy
|
||||
- text: Windows release health dashboard
|
||||
url: /windows/release-health
|
||||
- text: Windows client features lifecycle
|
||||
url: /windows/whats-new/feature-lifecycle
|
||||
- text: Lifecycle FAQ - Windows
|
||||
url: /lifecycle/faq/windows
|
||||
|
||||
- title: Windows hardware
|
||||
links:
|
||||
- text: Download and install the Windows ADK
|
||||
url: /windows-hardware/get-started/adk-install
|
||||
- text: Deployment tools
|
||||
url: /windows-hardware/manufacture/desktop/boot-and-install-windows
|
||||
# - text:
|
||||
# url:
|
||||
# - text:
|
||||
# url:
|
||||
|
||||
- title: Community
|
||||
links:
|
||||
- text: Windows IT pro blog
|
||||
url: https://techcommunity.microsoft.com/t5/windows-it-pro-blog/bg-p/Windows10Blog
|
||||
- text: Windows office hours
|
||||
url: https://aka.ms/windows/officehours
|
||||
# - text:
|
||||
# url:
|
||||
# - text:
|
||||
# url:
|
||||
|
||||
|
||||
@ -5,10 +5,11 @@ manager: aaroncz
|
||||
ms.technology: itpro-updates
|
||||
ms.prod: windows-client
|
||||
ms.topic: include
|
||||
ms.date: 08/21/2023
|
||||
ms.date: 12/15/2023
|
||||
ms.localizationpriority: medium
|
||||
---
|
||||
<!--This file is shared by updates/wufb-reports-prerequisites.md and the update/update-compliance-configuration-manual.md articles. Headings are driven by article context. -->
|
||||
|
||||
<!-- This file is shared by update/wufb-reports-prerequisites.md and update/wufb-reports-configuration-manual.md articles. Headings are driven by article context. -->
|
||||
|
||||
Devices must be able to contact the following endpoints in order to authenticate and send diagnostic data:
|
||||
|
||||
@ -20,5 +21,5 @@ Devices must be able to contact the following endpoints in order to authenticate
|
||||
| `settings-win.data.microsoft.com` | Used by Windows components and applications to dynamically update their configuration. Required for Windows Update functionality. |
|
||||
| `adl.windows.com` | Required for Windows Update functionality. |
|
||||
| `oca.telemetry.microsoft.com` | Online Crash Analysis, used to provide device-specific recommendations and detailed errors if there are certain crashes. |
|
||||
| `login.live.com` | This endpoint facilitates your Microsoft account access and is required to create the primary identifier we use for devices. Without this service, devices won't be visible in the solution. The Microsoft Account Sign-in Assistant service must also be running (wlidsvc). |
|
||||
| `*.blob.core.windows.net` | Azure blob data storage.|
|
||||
| `login.live.com` | This endpoint facilitates your Microsoft account access and is required to create the primary identifier we use for devices. Without this service, devices aren't visible in the solution. The Microsoft Account Sign-in Assistant service must also be running (wlidsvc). |
|
||||
| `ceuswatcab01.blob.core.windows.net` <br> `ceuswatcab02.blob.core.windows.net` <br> `eaus2watcab01.blob.core.windows.net` <br> `eaus2watcab02.blob.core.windows.net` <br> `weus2watcab01.blob.core.windows.net` <br> `weus2watcab02.blob.core.windows.net` | Azure blob data storage. <!-- 8603508 --> |
|
||||
|
||||
@ -4,7 +4,7 @@ titleSuffix: Windows Update for Business reports
|
||||
description: How to manually configure devices for Windows Update for Business reports using a PowerShell script.
|
||||
ms.prod: windows-client
|
||||
ms.technology: itpro-updates
|
||||
ms.topic: conceptual
|
||||
ms.topic: how-to
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
manager: aaroncz
|
||||
@ -12,61 +12,60 @@ ms.localizationpriority: medium
|
||||
appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
ms.date: 11/15/2022
|
||||
ms.date: 12/15/2023
|
||||
---
|
||||
|
||||
# Manually configuring devices for Windows Update for Business reports
|
||||
# Manually configure devices for Windows Update for Business reports
|
||||
<!--37063317, 30141258, 37063041-->
|
||||
|
||||
There are a number of requirements to consider when manually configuring devices for Windows Update for Business reports. These requirements can potentially change with newer versions of Windows client. The [Windows Update for Business reports configuration script](wufb-reports-configuration-script.md) will be updated when any configuration requirements change so only a redeployment of the script will be required.
|
||||
There are many requirements to consider when manually configuring devices for Windows Update for Business reports. These requirements can potentially change with later versions of Windows client. When any configuration requirements change, we'll update the [Windows Update for Business reports configuration script](wufb-reports-configuration-script.md). If that happens, you only need to redeploy the script.
|
||||
|
||||
The requirements are separated into different categories:
|
||||
|
||||
1. Ensuring the [**required policies**](#required-policies) for Windows Update for Business reports are correctly configured.
|
||||
2. Devices in every network topography must send data to the [**required endpoints**](#required-endpoints) for Windows Update for Business reports. For example, devices in both main and satellite offices, which might have different network configurations, must be able to reach the endpoints.
|
||||
3. Ensure [**Required Windows services**](#required-services) are running or are scheduled to run. It's recommended all Microsoft and Windows services are set to their out-of-box defaults to ensure proper functionality.
|
||||
|
||||
3. Ensure [**Required Windows services**](#required-services) are running or are scheduled to run. For proper functionality, leave Windows services set to their out-of-box default configurations.
|
||||
|
||||
## Required policies
|
||||
|
||||
Windows Update for Business reports has a number of policies that must be appropriately configured in order for devices to be processed by Microsoft and visible in Windows Update for Business reports. Thee policies are listed below, separated by whether the policies will be configured via [Mobile Device Management](/windows/client-management/mdm/) (MDM) or Group Policy. For both tables:
|
||||
The Windows Update for Business reports service has several policies that you need to configure appropriately. These policies allow Microsoft to process your devices and show them in Windows Update for Business reports. The policies are listed in the following subsections, separated by [mobile device management](/windows/client-management/mdm/) (MDM) or group policy.
|
||||
|
||||
- **Policy** corresponds to the location and name of the policy.
|
||||
- **Value** Indicates what value the policy must be set to. Windows Update for Business reports requires *at least* Basic (or Required) diagnostic data, but can function off Enhanced or Full (or Optional).
|
||||
- **Function** details why the policy is required and what function it serves for Windows Update for Business reports. It will also detail a minimum version the policy is required, if any.
|
||||
The following definitions apply for both tables:
|
||||
|
||||
### Mobile Device Management policies
|
||||
- **Policy**: The location and name of the policy.
|
||||
- **Value**: Set the policy to this value. Windows Update for Business reports requires at least *Required* (previously *Basic*) diagnostic data, but can function with *Enhanced* or *Optional* (previously *Full*).
|
||||
- **Function**: Details for why the policy is required and what function it serves for Windows Update for Business reports. It also details a minimum version the policy requires, if any.
|
||||
|
||||
Each MDM Policy links to its documentation in the configuration service provider (CSP) hierarchy, providing its exact location in the hierarchy and more details.
|
||||
### MDM policies
|
||||
|
||||
| Policy | Data type | Value | Function | Required or recommended|
|
||||
Each MDM policy links to more detailed documentation in the configuration service provider (CSP) hierarchy.
|
||||
|
||||
| Policy | Data type | Value | Function | Required or recommended |
|
||||
|---|---|---|---|---|
|
||||
|**System/**[**AllowTelemetry**](/windows/client-management/mdm/policy-csp-system#system-allowtelemetry) |Integer | 1 - Basic |Configures the maximum allowed diagnostic data to be sent to Microsoft. Individual users can still set this value lower than what the policy defines. For more information, see the following policy. | Required |
|
||||
|**System/**[**ConfigureTelemetryOptInSettingsUx**](/windows/client-management/mdm/policy-csp-system#system-configuretelemetryoptinsettingsux) |Integer |1 - Disable Telemetry opt-in Settings | Determines whether users of the device can adjust diagnostic data to levels lower than the level defined by AllowTelemetry. We recommend that you disable this policy or the effective diagnostic data level on devices might not be sufficient. | Recommended |
|
||||
|**System/**[**AllowDeviceNameInDiagnosticData**](/windows/client-management/mdm/policy-csp-system#system-allowdevicenameindiagnosticdata) |Integer | 1 - Allowed | Allows device name to be sent for Windows Diagnostic Data. If this policy is Not Configured or set to 0 (Disabled), Device Name won't be sent and won't be visible in Windows Update for Business reports, showing `#` instead. | Recommended |
|
||||
| **System/**[**ConfigureTelemetryOptInChangeNotification**](/windows/client-management/mdm/policy-csp-system#configuretelemetryoptinchangenotification) | Integer | 1 - Disabled | Disables user notifications that appear for changes to the diagnostic data level. | Recommended |
|
||||
| **System/**[**AllowTelemetry**](/windows/client-management/mdm/policy-csp-system#allowtelemetry) | Integer | `1`: Basic (Required) | Configures the device to send the minimum required diagnostic data. | Required |
|
||||
| **System/**[**ConfigureTelemetryOptInSettingsUx**](/windows/client-management/mdm/policy-csp-system#configuretelemetryoptinsettingsux) | Integer | `1`: Disable diagnostic data opt-in settings | Determines whether users of the device can adjust diagnostic data to levels lower than you define by the *AllowTelemetry* policy. Set the recommended value to disable opt-in settings, or users can change the effective diagnostic data level that might not be sufficient. | Recommended |
|
||||
| **System/**[**AllowDeviceNameInDiagnosticData**](/windows/client-management/mdm/policy-csp-system#allowdevicenameindiagnosticdata) | Integer | `1`: Allowed | Allows the device to send its name with Windows diagnostic data. If you don't configure this policy or set it to `0`: Disabled, then the data doesn't include the device name. If the data doesn't include the device name, you can't see the device in Windows Update for Business reports. In this instance, the reports show `#` instead. | Recommended |
|
||||
| **System/**[**ConfigureTelemetryOptInChangeNotification**](/windows/client-management/mdm/policy-csp-system#configuretelemetryoptinchangenotification) | Integer | `1`: Disabled | Disables user notifications that appear for changes to the diagnostic data level. | Recommended |
|
||||
|
||||
### Group policies
|
||||
|
||||
All Group policies that need to be configured for Windows Update for Business reports are under **Computer Configuration>Administrative Templates>Windows Components\Data Collection and Preview Builds**. All of these policies must be in the *Enabled* state and set to the defined *Value* below.
|
||||
All group policies that you need to configure for Windows Update for Business reports are under the following path: **Computer Configuration > Administrative Templates > Windows Components > Data Collection and Preview Builds**. All of these policies must be in the *Enabled* state and set to the defined *Value*.
|
||||
|
||||
| Policy | Value | Function | Required or recommended|
|
||||
|---|---|---|---|
|
||||
|**Allow Diagnostic Data** | Send required diagnostic data (minimum) | Configures the maximum allowed diagnostic data to be sent to Microsoft. Individual users can still set this value lower than what the policy defines. For more information, see the **Configure diagnostic data opt-in setting user interface**. | Required |
|
||||
|**Configure diagnostic data opt-in setting user interface** | Disable diagnostic data opt in settings | Determines whether users of the device can adjust diagnostic data to levels lower than the level defined by AllowTelemetry. We recommend that you disable this policy, otherwise the effective diagnostic data level on devices might not be sufficient. | Recommended |
|
||||
|**Allow device name to be sent in Windows diagnostic data** | Enabled | Allows device name to be sent for Windows Diagnostic Data. If this policy is Not Configured or Disabled, Device Name won't be sent and won't be visible in Windows Update for Business reports, showing `#` instead. | Recommended |
|
||||
|**Configure diagnostic data opt-in change notifications** | Disable diagnostic data change notifications | Disables user notifications that appear for changes to the diagnostic data level. | Recommended |
|
||||
| **Allow Diagnostic Data** | Send required diagnostic data | Configures the device to send the minimum required diagnostic data. | Required |
|
||||
| **Configure diagnostic data opt-in setting user interface** | Disable diagnostic data opt-in settings | Determines whether users of the device can adjust diagnostic data to levels lower than you define by the *Allow Diagnostic Data* policy. Set the recommended value to disable opt-in settings, or users can change the effective diagnostic data level that might not be sufficient. | Recommended |
|
||||
| **Allow device name to be sent in Windows diagnostic data** | Enabled | Allows the device to send its name with Windows diagnostic data. If you don't configure this policy or set it to *Disabled*, then the data doesn't include the device name. If the data doesn't include the device name, you can't see the device in Windows Update for Business reports. In this instance, the reports show `#` instead. | Recommended |
|
||||
| **Configure diagnostic data opt-in change notifications** | Disable diagnostic data change notifications | Disables user notifications that appear for changes to the diagnostic data level. | Recommended |
|
||||
|
||||
## Required endpoints
|
||||
|
||||
To enable data sharing between devices, your network, and Microsoft's Diagnostic Data Service, configure your proxy to allow devices to contact the below endpoints.
|
||||
|
||||
<!--Using include for endpoint access requirements-->
|
||||
[!INCLUDE [Endpoints for Windows Update for Business reports](./includes/wufb-reports-endpoints.md)]
|
||||
|
||||
## Required services
|
||||
|
||||
Many Windows and Microsoft services are required to ensure that not only the device can function, but Windows Update for Business reports can see device data. It's recommended that you allow all default services from the out-of-box experience to remain running. The [Windows Update for Business reports Configuration Script](wufb-reports-configuration-script.md) checks whether the majority of these services are running or are allowed to run automatically.
|
||||
Many Windows services are required for Windows Update for Business reports to see device data. Allow all default services from the out-of-box experience to remain running. Use the [Windows Update for Business reports configuration script](wufb-reports-configuration-script.md) to check whether required services are running or are allowed to run automatically.
|
||||
|
||||
## Next steps
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ manager: aaroncz
|
||||
appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
ms.date: 08/30/2023
|
||||
ms.date: 12/15/2023
|
||||
---
|
||||
|
||||
# Windows Update for Business reports prerequisites
|
||||
@ -22,12 +22,12 @@ Before you begin the process of adding Windows Update for Business reports to yo
|
||||
|
||||
## Azure and Microsoft Entra ID
|
||||
|
||||
- An Azure subscription with [Microsoft Entra ID](/azure/active-directory/)
|
||||
- An Azure subscription with [Microsoft Entra ID](/azure/active-directory/).
|
||||
- Devices must be Microsoft Entra joined and meet the below OS, diagnostic, and endpoint access requirements.
|
||||
- Devices can be [Microsoft Entra joined](/azure/active-directory/devices/concept-azure-ad-join) or [Microsoft Entra hybrid joined](/azure/active-directory/devices/concept-azure-ad-join-hybrid).
|
||||
- Devices that are [Microsoft Entra registered](/azure/active-directory/devices/concept-azure-ad-register) only (Workplace joined) aren't supported with Windows Update for Business reports.
|
||||
- The Log Analytics workspace must be in a [supported region](#log-analytics-regions)
|
||||
- Data in the **Driver update** tab of the [workbook](wufb-reports-workbook.md) is only available for devices that receive driver and firmware updates from the [Windows Update for Business deployment service](deployment-service-overview.md)
|
||||
- Devices that are [Microsoft Entra registered](/azure/active-directory/devices/concept-azure-ad-register) only (workplace joined) aren't supported with Windows Update for Business reports.
|
||||
- The Log Analytics workspace must be in a [supported region](#log-analytics-regions).
|
||||
- Data in the **Driver update** tab of the [workbook](wufb-reports-workbook.md) is only available for devices that receive driver and firmware updates from the [Windows Update for Business deployment service](deployment-service-overview.md).
|
||||
|
||||
## Permissions
|
||||
|
||||
@ -38,7 +38,7 @@ Before you begin the process of adding Windows Update for Business reports to yo
|
||||
- Windows 11 Professional, Education, Enterprise, and [Enterprise multi-session](/azure/virtual-desktop/windows-10-multisession-faq) editions
|
||||
- Windows 10 Professional, Education, Enterprise, and [Enterprise multi-session](/azure/virtual-desktop/windows-10-multisession-faq) editions
|
||||
|
||||
Windows Update for Business reports only provides data for the standard Desktop Windows client version and isn't currently compatible with Windows Server, Surface Hub, IoT, or other versions.
|
||||
Windows Update for Business reports only provides data for the standard desktop Windows client version and isn't currently compatible with Windows Server, Surface Hub, IoT, or other versions.
|
||||
|
||||
## Windows client servicing channels
|
||||
|
||||
@ -49,27 +49,25 @@ Windows Update for Business reports supports Windows client devices on the follo
|
||||
|
||||
### 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
|
||||
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*). For more information about what's included in different diagnostic levels, see [Configure Windows diagnostic data in your organization](/windows/privacy/configure-windows-diagnostic-data-in-your-organization).
|
||||
At minimum, Windows Update for Business reports requires devices to send diagnostic data at the *Required* level (previously *Basic*). For more information about what data each diagnostic level includes, see [Configure Windows diagnostic data in your organization](/windows/privacy/configure-windows-diagnostic-data-in-your-organization).
|
||||
|
||||
The following levels are recommended, but not required:
|
||||
- The *Enhanced* level for Windows 10 devices
|
||||
- The *Optional* level for Windows 11 devices (previously *Full*) <!--8027083-->
|
||||
|
||||
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:
|
||||
- The *Enhanced* level for Windows 10 devices.
|
||||
- The *Optional* level for Windows 11 devices (previously *Full*). <!--8027083-->
|
||||
|
||||
|
||||
- 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 action for you, but when using other client configuration methods, set one of the following policies 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**
|
||||
|
||||
> [!TIP]
|
||||
> Windows Update for Business reports uses [services configuration](/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services#bkmk-svccfg), also called OneSettings. Disabling the services configuration can cause some of the client data to be incorrect or missing in reports. For more information, see the [DisableOneSettingsDownloads](/windows/client-management/mdm/policy-csp-system#disableonesettingsdownloads) policy settings.
|
||||
|
||||
|
||||
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).
|
||||
|
||||
## Endpoints
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Manage Windows Autopatch groups
|
||||
description: This article explains how to manage Autopatch groups
|
||||
ms.date: 07/25/2023
|
||||
ms.date: 12/13/2023
|
||||
ms.prod: windows-client
|
||||
ms.technology: itpro-updates
|
||||
ms.topic: how-to
|
||||
@ -46,7 +46,7 @@ Before you start managing Autopatch groups, ensure you’ve met the following pr
|
||||
- Windows Autopatch – Ring2
|
||||
- Windows Autopatch – Ring3
|
||||
- Windows Autopatch – Last
|
||||
- Additionally, **don't** modify the Microsoft Entra group ownership of any of the groups above otherwise, Autopatch groups device registration process won't be able to add devices into these groups. If the ownership is modified, you must add the **Modern Workplace Management** Service Principal as the owner of these groups.
|
||||
- Additionally, **don't** modify the Microsoft Entra group ownership of any of the groups above otherwise, Autopatch groups device registration process won't be able to add devices into these groups. If the ownership is modified, you must add the **Modern Workplace Management** enterprise application as the owner of these groups.
|
||||
- For more information, see [assign an owner or member of a group in Microsoft Entra ID](/azure/active-directory/privileged-identity-management/groups-assign-member-owner#assign-an-owner-or-member-of-a-group) for steps on how to add owners to Azure Microsoft Entra groups.
|
||||
- Make sure you have [app-only auth turned on in your Windows Autopatch tenant](../operate/windows-autopatch-maintain-environment.md#windows-autopatch-tenant-actions). Otherwise, the Autopatch groups functionality won’t work properly. Autopatch uses app-only auth to:
|
||||
- Read device attributes to successfully register devices.
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Changes made at tenant enrollment
|
||||
description: This reference article details the changes made to your tenant when enrolling into Windows Autopatch
|
||||
ms.date: 06/23/2023
|
||||
ms.date: 12/13/2023
|
||||
ms.prod: windows-client
|
||||
ms.technology: itpro-updates
|
||||
ms.topic: reference
|
||||
@ -32,14 +32,6 @@ Windows Autopatch creates an enterprise application in your tenant. This enterpr
|
||||
| ----- | ------ | ----- |
|
||||
| Modern Workplace Management | The Modern Workplace Management application:<ul><li>Manages the service</li><li>Publishes baseline configuration updates</li><li>Maintains overall service health</li></ul> | <ul><li>DeviceManagementApps.ReadWrite.All</li><li>DeviceManagementConfiguration.ReadWrite.All</li><li>DeviceManagementManagedDevices.PriviligedOperation.All</li><li>DeviceManagementManagedDevices.ReadWrite.All</li><li>DeviceManagementRBAC.ReadWrite.All</li><li>DeviceManagementServiceConfig.ReadWrite.All</li><li>Directory.Read.All</li><li>Group.Create</li><li>Policy.Read.All</li><li>WindowsUpdates.ReadWrite.All</li></ul> |
|
||||
|
||||
### Service principal
|
||||
|
||||
Windows Autopatch will create a service principal in your tenant to establish an identity and restrict access to what resources the service has access to within the tenant. For more information, see [Application and service principal objects in Microsoft Entra ID](/azure/active-directory/develop/app-objects-and-service-principals#service-principal-object). The service principal created by Windows Autopatch is:
|
||||
|
||||
- Modern Workplace Customer APIs
|
||||
|
||||
<a name='azure-active-directory-groups'></a>
|
||||
|
||||
## Microsoft Entra groups
|
||||
|
||||
Windows Autopatch will create the required Microsoft Entra groups to operate the service.
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: What's new 2023
|
||||
description: This article lists the 2023 feature releases and any corresponding Message center post numbers.
|
||||
ms.date: 12/04/2023
|
||||
ms.date: 12/14/2023
|
||||
ms.prod: windows-client
|
||||
ms.technology: itpro-updates
|
||||
ms.topic: whats-new
|
||||
@ -29,6 +29,13 @@ Minor corrections such as typos, style, or formatting issues aren't listed.
|
||||
| ----- | ----- |
|
||||
| [Prerequisites](../prepare/windows-autopatch-prerequisites.md#more-about-licenses) | Added F SKU licenses to the [More about licenses](../prepare/windows-autopatch-prerequisites.md#more-about-licenses) section. Also see [FAQ](../overview/windows-autopatch-faq.yml)<ul><li>[MC690609](https://admin.microsoft.com/adminportal/home#/MessageCenter)</li></ul> |
|
||||
|
||||
## December service release
|
||||
|
||||
| Message center post number | Description |
|
||||
| ----- | ----- |
|
||||
| [MC697414](https://admin.microsoft.com/adminportal/home#/MessageCenter) | New Feature: Alerts for Windows Autopatch policy conflicts Public Preview announcement |
|
||||
| [MC695483](https://admin.microsoft.com/adminportal/home#/MessageCenter) | Planned Maintenance: Windows Autopatch configuration update – December 2023 |
|
||||
|
||||
## November service release
|
||||
|
||||
| Message center post number | Description |
|
||||
|
||||
Reference in New Issue
Block a user