mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-16 19:03:46 +00:00
Merge branch 'main' into do_docs
This commit is contained in:
Carmen Forsmann
GitHub
@ -29,7 +29,7 @@
|
||||
- name: Plan
|
||||
items:
|
||||
- name: Plan for Windows 11
|
||||
href: /windows/whats-new/windows-11-plan?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json
|
||||
href: /windows/whats-new/windows-11-plan?context=/windows/deployment/context/context
|
||||
- name: Create a deployment plan
|
||||
href: update/create-deployment-plan.md
|
||||
- name: Define readiness criteria
|
||||
@ -41,12 +41,12 @@
|
||||
- name: Define your servicing strategy
|
||||
href: update/plan-define-strategy.md
|
||||
- name: Delivery Optimization for Windows client updates
|
||||
href: do/waas-delivery-optimization.md?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json
|
||||
href: do/waas-delivery-optimization.md?context=/windows/deployment/context/context
|
||||
items:
|
||||
- name: Using a proxy with Delivery Optimization
|
||||
href: do/delivery-optimization-proxy.md?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json
|
||||
href: do/delivery-optimization-proxy.md?context=/windows/deployment/context/context
|
||||
- name: Delivery Optimization client-service communication
|
||||
href: do/delivery-optimization-workflow.md?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json
|
||||
href: do/delivery-optimization-workflow.md?context=/windows/deployment/context/context
|
||||
- name: Windows 10 deployment considerations
|
||||
href: planning/windows-10-deployment-considerations.md
|
||||
- name: Windows 10 infrastructure requirements
|
||||
@ -56,17 +56,17 @@
|
||||
- name: Features removed or planned for replacement
|
||||
items:
|
||||
- name: Windows client features lifecycle
|
||||
href: /windows/whats-new/feature-lifecycle?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json
|
||||
href: /windows/whats-new/feature-lifecycle?context=/windows/deployment/context/context
|
||||
- name: Deprecated features
|
||||
href: /windows/whats-new/deprecated-features?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json
|
||||
href: /windows/whats-new/deprecated-features?context=/windows/deployment/context/context
|
||||
- name: Resources for deprecated features
|
||||
href: /windows/whats-new/deprecated-features-resources?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json
|
||||
href: /windows/whats-new/deprecated-features-resources?context=/windows/deployment/context/context
|
||||
- name: Removed features
|
||||
href: /windows/whats-new/removed-features?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json
|
||||
href: /windows/whats-new/removed-features?context=/windows/deployment/context/context
|
||||
- name: Prepare
|
||||
items:
|
||||
- name: Prepare for Windows 11
|
||||
href: /windows/whats-new/windows-11-prepare?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json
|
||||
href: /windows/whats-new/windows-11-prepare?context=/windows/deployment/context/context
|
||||
- name: Prepare to deploy Windows client updates
|
||||
href: update/prepare-deploy-windows.md
|
||||
- name: Evaluate and update infrastructure
|
||||
@ -74,7 +74,7 @@
|
||||
- name: Update Baseline
|
||||
href: update/update-baseline.md
|
||||
- name: Set up Delivery Optimization for Windows client updates
|
||||
href: do/waas-delivery-optimization-setup.md?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json
|
||||
href: do/waas-delivery-optimization-setup.md?context=/windows/deployment/context/context
|
||||
- name: Configure BranchCache for Windows client updates
|
||||
href: update/waas-branchcache.md
|
||||
- name: Prepare for deployment with Configuration Manager
|
||||
@ -324,25 +324,25 @@
|
||||
- name: Resolve Windows upgrade errors
|
||||
href: upgrade/resolve-windows-upgrade-errors.md
|
||||
- name: Quick fixes
|
||||
href: /troubleshoot/windows-client/deployment/windows-10-upgrade-quick-fixes?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json
|
||||
href: /troubleshoot/windows-client/deployment/windows-10-upgrade-quick-fixes?context=/windows/deployment/context/context
|
||||
- name: SetupDiag
|
||||
href: upgrade/setupdiag.md
|
||||
- name: Troubleshooting upgrade errors
|
||||
href: /troubleshoot/windows-client/deployment/windows-10-upgrade-issues-troubleshooting?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json
|
||||
href: /troubleshoot/windows-client/deployment/windows-10-upgrade-issues-troubleshooting?context=/windows/deployment/context/context
|
||||
- name: Windows error reporting
|
||||
href: upgrade/windows-error-reporting.md
|
||||
- name: Upgrade error codes
|
||||
href: /troubleshoot/windows-client/deployment/windows-10-upgrade-error-codes?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json
|
||||
href: /troubleshoot/windows-client/deployment/windows-10-upgrade-error-codes?context=/windows/deployment/context/context
|
||||
- name: Log files
|
||||
href: upgrade/log-files.md
|
||||
- name: Resolution procedures
|
||||
href: /troubleshoot/windows-client/deployment/windows-10-upgrade-resolution-procedures?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json
|
||||
href: /troubleshoot/windows-client/deployment/windows-10-upgrade-resolution-procedures?context=/windows/deployment/context/context
|
||||
- name: Submit Windows client upgrade errors
|
||||
href: upgrade/submit-errors.md
|
||||
- name: Troubleshoot Windows Update
|
||||
items:
|
||||
- name: How to troubleshoot Windows Update
|
||||
href: /troubleshoot/windows-client/deployment/windows-update-issues-troubleshooting?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json
|
||||
href: /troubleshoot/windows-client/deployment/windows-update-issues-troubleshooting?context=/windows/deployment/context/context
|
||||
- name: Opt out of safeguard holds
|
||||
href: update/safeguard-opt-out.md
|
||||
- name: Determine the source of Windows Updates
|
||||
@ -350,7 +350,7 @@
|
||||
- name: Windows Update security
|
||||
href: ./update/windows-update-security.md
|
||||
- name: Common Windows Update errors
|
||||
href: /troubleshoot/windows-client/deployment/common-windows-update-errors?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json
|
||||
href: /troubleshoot/windows-client/deployment/common-windows-update-errors?context=/windows/deployment/context/context
|
||||
- name: Windows Update error code reference
|
||||
href: update/windows-update-error-reference.md
|
||||
- name: Troubleshoot the Windows Update for Business deployment service
|
||||
@ -371,13 +371,13 @@
|
||||
- name: Servicing stack updates
|
||||
href: update/servicing-stack-updates.md
|
||||
- name: Update CSP policies
|
||||
href: /windows/client-management/mdm/policy-csp-update?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json
|
||||
href: /windows/client-management/mdm/policy-csp-update?context=/windows/deployment/context/context
|
||||
- name: Additional Windows Update settings
|
||||
href: update/waas-wu-settings.md
|
||||
- name: Update other Microsoft products
|
||||
href: update/update-other-microsoft-products.md
|
||||
- name: Delivery Optimization reference
|
||||
href: do/waas-delivery-optimization-reference.md?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json
|
||||
href: do/waas-delivery-optimization-reference.md?context=/windows/deployment/context/context
|
||||
- name: FoD and language packs for WSUS and Configuration Manager
|
||||
href: update/fod-and-lang-packs.md
|
||||
- name: Windows client in S mode
|
||||
|
||||
4
windows/deployment/context/context.yml
Normal file
4
windows/deployment/context/context.yml
Normal file
@ -0,0 +1,4 @@
|
||||
### YamlMime: ContextObject
|
||||
brand: windows
|
||||
breadcrumb_path: ../breadcrumb/toc.yml
|
||||
toc_rel: ../toc.yml
|
||||
@ -12,7 +12,7 @@ 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: 12/15/2023
|
||||
ms.date: 07/09/2024
|
||||
---
|
||||
|
||||
# Manually configure devices for Windows Update for Business reports
|
||||
|
||||
@ -12,7 +12,7 @@ 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: 07/11/2023
|
||||
ms.date: 07/09/2024
|
||||
---
|
||||
|
||||
# Configuring devices through the Windows Update for Business reports configuration script
|
||||
@ -22,9 +22,9 @@ The Windows Update for Business reports configuration script is the recommended
|
||||
|
||||
## About the script
|
||||
|
||||
The configuration script configures registry keys directly. Be aware that registry keys can potentially be overwritten by policy settings like Group Policy or MDM. *Reconfiguring devices with the script doesn't reconfigure previously set policies, both in the case of Group Policy and MDM*. If there are conflicts between your Group Policy or MDM configurations and the required configurations listed in [Manually configuring devices for Windows Update for Business reports](wufb-reports-configuration-manual.md), device data might not appear in Windows Update for Business reports correctly.
|
||||
The configuration script configures registry keys directly. Registry keys can potentially be overwritten by policy settings like Group Policy or MDM. *Reconfiguring devices with the script doesn't reconfigure previously set policies, both in the case of Group Policy and MDM*. If there are conflicts between your Group Policy or MDM configurations and the required configurations listed in [Manually configuring devices for Windows Update for Business reports](wufb-reports-configuration-manual.md), device data might not appear in Windows Update for Business reports correctly.
|
||||
|
||||
You can download the script from the [Microsoft Download Center](https://www.microsoft.com/download/details.aspx?id=101086). Keep reading to learn how to configure the script and interpret error codes that are output in logs for troubleshooting.
|
||||
You can download the script from the [Microsoft Download Center](https://www.microsoft.com/download/details.aspx?id=101086).
|
||||
|
||||
## How this script is organized
|
||||
|
||||
@ -39,11 +39,11 @@ Edit the `RunConfig.bat` file to configure the following variables, then run the
|
||||
|
||||
| Variable | Allowed values and description | Example |
|
||||
|---|---|---|
|
||||
| runMode | **Pilot** (default): Verbose mode with additional diagnostics with additional logging. Pilot mode is best for a testing run of the script or for troubleshooting. <br> **Deployment**: Doesn't run any additional diagnostics or add extra logging | `runMode=Pilot` |
|
||||
| logPath | Path where the logs will be saved. The default location of the logs is `.\UCLogs`. | `logPath=C:\temp\logs` |
|
||||
| logMode | **0**: Log to the console only </br> **1** (default): Log to file and console. </br> **2**: Log to file only. | `logMode=2` |
|
||||
| DeviceNameOptIn | **true** (default): Device name is sent to Microsoft. </br> **false**: Device name isn't sent to Microsoft. | `DeviceNameOptIn=true` |
|
||||
| ClientProxy | **Direct** (default): No proxy is used. The connection to the endpoints is direct. </br> **System**: The system proxy, without authentication, is used. This type of proxy is typically configured with [netsh](/windows-server/networking/technologies/netsh/netsh-contexts) and can be verified using `netsh winhttp show proxy`. </br> **User**: The proxy is configured through IE and it might or might not require user authentication. </br> </br> For more information, see [How the Windows Update client determines which proxy server to use to connect to the Windows Update website](https://support.microsoft.com/en-us/topic/how-the-windows-update-client-determines-which-proxy-server-to-use-to-connect-to-the-windows-update-website-08612ae5-3722-886c-f1e1-d012516c22a1) | `ClientProxy=Direct` |
|
||||
| runMode | **Pilot** (default): Verbose mode with additional diagnostics and logging. Pilot mode is best for a testing run of the script or for troubleshooting. <br> **Deployment**: Doesn't run any additional diagnostics or add extra logging | `runMode=Pilot` |
|
||||
| logPath | Path where the logs are saved. The default location of the logs is `.\UCLogs`.| `logPath=C:\temp\logs` |
|
||||
| logMode | **0**: Log to the console only </br> **1** (default): Log to file and console.</br> **2**: Log to file only. | `logMode=2` |
|
||||
| DeviceNameOptIn | **true** (default): Device name is sent to Microsoft.</br> **false**: Device name isn't sent to Microsoft. | `DeviceNameOptIn=true` |
|
||||
| ClientProxy | **Direct** (default): No proxy is used. The connection to the endpoints is direct.</br> **System**: The system proxy, without authentication, is used. This type of proxy is typically configured with [netsh](/windows-server/networking/technologies/netsh/netsh-contexts) and can be verified using `netsh winhttp show proxy`. </br> **User**: The proxy is configured through IE and it might or might not require user authentication. </br> </br> For more information, see [How the Windows Update client determines which proxy server to use to connect to the Windows Update website](https://support.microsoft.com/en-us/topic/how-the-windows-update-client-determines-which-proxy-server-to-use-to-connect-to-the-windows-update-website-08612ae5-3722-886c-f1e1-d012516c22a1) | `ClientProxy=Direct` |
|
||||
| source | Used by the .bat file and PowerShell script to locate dependencies. It's recommended that you don't change this value. | `source=%~dp0` |
|
||||
|
||||
|
||||
|
||||
@ -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: 07/11/2023
|
||||
ms.date: 07/09/2024
|
||||
---
|
||||
|
||||
# Enable Windows Update for Business reports
|
||||
@ -34,7 +34,7 @@ After verifying the [prerequisites](wufb-reports-prerequisites.md) are met, you
|
||||
|
||||
## <a name="bkmk_add"></a> Add Windows Update for Business reports to your Azure subscription
|
||||
|
||||
Before you configure clients to send data, you'll need to add Windows Update for Business reports to your Azure subscription so the data can be received. First, you'll select or create a new Log Analytics workspace to use. Second, you'll enroll Windows Update for Business reports to the workspace.
|
||||
Before you configure clients to send data, you need to add Windows Update for Business reports to your Azure subscription so the data can be received. First, you select or create a new Log Analytics workspace to use. Second, you enroll Windows Update for Business reports to the workspace.
|
||||
|
||||
## <a name="bkmk_workspace"></a> Select or create a new Log Analytics workspace for Windows Update for Business reports
|
||||
|
||||
@ -69,7 +69,7 @@ Enroll into Windows Update for Business reports by configuring its settings thro
|
||||
> [!Tip]
|
||||
> If a `403 Forbidden` error occurs, verify the account you're using has [permissions](wufb-reports-prerequisites.md#permissions) to enroll into Windows Update for Business reports.
|
||||
1. The initial setup can take up to 24 hours. During this time, the workbook will display that it's **Waiting for Windows Update for Business reports data**.
|
||||
- Enrolling into Windows Update for Business reports doesn't influence the rate that required data is uploaded from devices. Device connectivity to the internet and how active the device is influences how long it will take before the device appears in reporting. Devices that are active and connected to the internet daily can expect to be fully uploaded within one week (usually less than 72 hours). Devices that are less active can take up to two weeks before data is fully available.
|
||||
- Enrolling into Windows Update for Business reports doesn't influence the rate that required data is uploaded from devices. Device connectivity to the internet and how active the device is influences how long it takes before the device appears in reporting. Devices that are active and connected to the internet daily can expect to be fully uploaded within one week (usually less than 72 hours). Devices that are less active can take up to two weeks before data is fully available.
|
||||
|
||||
##### <a name="bkmk_admin-center"></a> Enroll through the Microsoft 365 admin center
|
||||
<!--Using include for onboarding Windows Update for Business reports through the Microsoft 365 admin center-->
|
||||
|
||||
@ -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: 02/10/2023
|
||||
ms.date: 07/09/2024
|
||||
---
|
||||
|
||||
# Windows Update for Business reports feedback, support, and troubleshooting
|
||||
@ -52,7 +52,7 @@ You can open support requests directly from the Azure portal. If the **Help + S
|
||||
- **Service type** - Select ***Windows Update for Business reports*** under ***Monitoring and Management***
|
||||
|
||||
|
||||
1. Based on the information you provided, you'll be shown some **Recommended solutions** you can use to try to resolve the problem.
|
||||
1. Based on the information you provided, you are shown some **Recommended solutions** you can use to try to resolve the problem.
|
||||
1. Complete the **Additional details** tab and then create the request on the **Review + create** tab.
|
||||
|
||||
## Documentation feedback
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Register your devices
|
||||
description: This article details how to register devices in Autopatch.
|
||||
ms.date: 02/15/2024
|
||||
ms.date: 07/10/2024
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: how-to
|
||||
@ -112,10 +112,7 @@ The following are the possible device readiness statuses in Windows Autopatch:
|
||||
|
||||
## Built-in roles required for device registration
|
||||
|
||||
A role defines the set of permissions granted to users assigned to that role. You can use one of the following built-in roles in Windows Autopatch to register devices:
|
||||
|
||||
- Microsoft Entra Global Administrator
|
||||
- Intune Service Administrator
|
||||
A role defines the set of permissions granted to users assigned to that role. You can use the **Intune Service Administrator** role to register devices.
|
||||
|
||||
For more information, see [Microsoft Entra built-in roles](/azure/active-directory/roles/permissions-reference) and [Role-based access control (RBAC) with Microsoft Intune](/mem/intune/fundamentals/role-based-access-control).
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: policy health and remediation
|
||||
description: Describes what Autopatch does it detects policies in the tenant are either missing or modified to states that affect the service
|
||||
ms.date: 07/08/2024
|
||||
ms.date: 07/10/2024
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: how-to
|
||||
@ -44,7 +44,7 @@ Alerts are raised when deployment rings don't have the required policies and the
|
||||
|
||||
## Built-in roles required for remediation actions
|
||||
|
||||
The minimum role required to restore configurations is **Intune Service Administrator**. You can also perform these actions in the Global administrator role.
|
||||
The minimum role required to restore configurations is **Intune Service Administrator**.
|
||||
|
||||
## Restore device configuration policy
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Windows quality and feature update reports overview
|
||||
description: This article details the types of reports available and info about update device eligibility, device update health, device update trends in Windows Autopatch.
|
||||
ms.date: 04/09/2024
|
||||
ms.date: 07/10/2024
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: conceptual
|
||||
@ -53,7 +53,6 @@ The Windows feature update report types are organized into the following focus a
|
||||
|
||||
Users with the following permissions can access the reports:
|
||||
|
||||
- Global Administrator
|
||||
- Intune Service Administrator
|
||||
- Global Reader
|
||||
- Services Support Administrator
|
||||
|
||||
Reference in New Issue
Block a user