update manager alias

This commit is contained in:
Aaron Czechowski
2025-06-03 16:47:25 -07:00
parent 4dca10ac5f
commit 51d668848a
277 changed files with 981 additions and 985 deletions

View File

@ -1,7 +1,7 @@
---
author: tiaraquan
ms.author: tiaraquan
manager: aaroncz
manager: bpardi
ms.service: windows-client
ms.subservice: autopatch
ms.topic: include

View File

@ -1,7 +1,7 @@
---
author: tiaraquan
ms.author: tiaraquan
manager: aaroncz
manager: bpardi
ms.service: windows-client
ms.subservice: autopatch
ms.topic: include
@ -14,8 +14,8 @@ A deployment audience is a collection of devices that you want to deploy updates
1. To create a new audience, **POST** to the [deployment audience](/graph/api/resources/windowsupdates-deploymentaudience) resource with a request body of `{}`.
```msgraph-interactive
POST https://graph.microsoft.com/beta/admin/windows/updates/deploymentAudiences
content-type: application/json
POST https://graph.microsoft.com/beta/admin/windows/updates/deploymentAudiences
content-type: application/json
{}
```
@ -35,8 +35,8 @@ A deployment audience is a collection of devices that you want to deploy updates
1. Add devices, using their **Microsoft Entra ID**, to the deployment audience so they become audience members. Specify the deployment **Audience ID** in the URL field and the devices to add in the request body. The `id` property specifies the **Microsoft Entra ID** of the device.
```msgraph-interactive
POST https://graph.microsoft.com/beta/admin/windows/updates/deploymentAudiences/d39ad1ce-0123-4567-89ab-cdef01234567/updateAudience
content-type: application/json
POST https://graph.microsoft.com/beta/admin/windows/updates/deploymentAudiences/d39ad1ce-0123-4567-89ab-cdef01234567/updateAudience
content-type: application/json
{
"addMembers": [

View File

@ -1,7 +1,7 @@
---
author: tiaraquan
ms.author: tiaraquan
manager: aaroncz
manager: bpardi
ms.service: windows-client
ms.subservice: autopatch
ms.topic: include

View File

@ -1,7 +1,7 @@
---
author: tiaraquan
ms.author: tiaraquan
manager: aaroncz
manager: bpardi
ms.service: windows-client
ms.subservice: autopatch
ms.topic: include
@ -10,7 +10,7 @@ ms.localizationpriority: medium
---
<!--This file is shared by windows-autopatch-driver-and-firmware-programmatic-controls.md, windows-autopatch-troubleshoot-programmatic-controls.md, and the deployment-service-prerequisites.md articles. Headings may be driven by article context. 7512398 -->
It's possible for the service to receive content approval but the content doesn't get installed on the device because of a Group Policy, CSP, or registry setting on the device. In some cases, organizations specifically configure these policies to fit their current or future needs. For instance, organizations may want to review applicable driver content, but not allow installation. Configuring this sort of behavior can be useful, especially when transitioning management of driver updates due to changing organizational needs. The following list describes driver related update policies that can affect deployments:
It's possible for the service to receive content approval but the content doesn't get installed on the device because of a Group Policy, CSP, or registry setting on the device. In some cases, organizations specifically configure these policies to fit their current or future needs. For instance, organizations may want to review applicable driver content, but not allow installation. Configuring this sort of behavior can be useful, especially when transitioning management of driver updates due to changing organizational needs. The following list describes driver related update policies that can affect deployments:
### Policies that exclude drivers from Windows Update for a device
@ -20,7 +20,7 @@ The following policies exclude drivers from Windows Update for a device:
- **Group Policy**: `\Windows Components\Windows Update\Do not include drivers with Windows Updates` set to `enabled`
- **CSP**: [ExcludeWUDriversInQualityUpdate](/windows/client-management/mdm/policy-csp-update#excludewudriversinqualityupdate) set to `1`
- **Registry**: `HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\ExcludeWUDriversFromQualityUpdates` set to `1`
- **Intune**: [**Windows Drivers** update setting](/mem/intune/protect/windows-update-settings#update-settings) for the update ring set to `Block`
- **Intune**: [**Windows Drivers** update setting](/mem/intune/protect/windows-update-settings#update-settings) for the update ring set to `Block`
**Behavior**: Devices with driver exclusion polices that are enrolled for **drivers** and added to an audience:
- Will display the applicable driver content

View File

@ -1,7 +1,7 @@
---
author: tiaraquan
ms.author: tiaraquan
manager: aaroncz
manager: bpardi
ms.service: windows-client
ms.subservice: autopatch
ms.topic: include

View File

@ -1,7 +1,7 @@
---
author: tiaraquan
ms.author: tiaraquan
manager: aaroncz
manager: bpardi
ms.service: windows-client
ms.subservice: autopatch
ms.topic: include

View File

@ -1,7 +1,7 @@
---
author: tiaraquan
ms.author: tiaraquan
manager: aaroncz
manager: bpardi
ms.service: windows-client
ms.subservice: autopatch
ms.topic: include

View File

@ -1,7 +1,7 @@
---
author: tiaraquan
ms.author: tiaraquan
manager: aaroncz
manager: bpardi
ms.service: windows-client
ms.subservice: autopatch
ms.topic: include

View File

@ -1,7 +1,7 @@
---
author: tiaraquan
ms.author: tiaraquan
manager: aaroncz
manager: bpardi
ms.service: windows-client
ms.subservice: autopatch
ms.topic: include
@ -28,6 +28,6 @@ For this article, you'll use Graph Explorer to make requests to the [Microsoft G
1. Enter the request into the URL field. The version will populate automatically based on the URL.
1. If you need to modify the request body, edit the **Request body** tab.
1. Select the **Run query** button. The results will appear in the **Response** window.
> [!TIP]
> When reviewing [Microsoft Graph documentation](/graph/), you may notice example requests usually list `content-type: application/json`. Specifying `content-type` typically isn't required for Graph Explorer, but you can add it to the request by selecting the **Headers** tab and adding the `content-type` to the **Request headers** field as the **Key** and `application/json` as the **Value**.

View File

@ -1,7 +1,7 @@
---
author: tiaraquan
ms.author: tiaraquan
manager: aaroncz
manager: bpardi
ms.service: windows-client
ms.subservice: autopatch
ms.topic: include

View File

@ -1,7 +1,7 @@
---
author: tiaraquan
ms.author: tiaraquan
manager: aaroncz
manager: bpardi
ms.service: windows-client
ms.subservice: autopatch
ms.topic: include

View File

@ -1,7 +1,7 @@
---
author: tiaraquan
ms.author: tiaraquan
manager: aaroncz
manager: bpardi
ms.service: windows-client
ms.subservice: autopatch
ms.topic: include

View File

@ -1,7 +1,7 @@
---
author: tiaraquan
ms.author: tiaraquan
manager: aaroncz
manager: bpardi
ms.service: windows-client
ms.subservice: autopatch
ms.topic: include
@ -15,7 +15,7 @@ The Update Health Tools are used when you deploy expedited updates. In some case
**Log location**: `%ProgramFiles%\Microsoft Update Health Tools\Logs`
- The logs are in `.etl` format.
- The logs are in `.etl` format.
- Microsoft offers [PerfView as a download on GitHub](https://github.com/Microsoft/perfview/blob/main/documentation/Downloading.md), which displays `.etl` files.
For more information, see [Troubleshooting expedited updates](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/get-the-most-out-of-expedited-windows-quality-updates/ba-p/3659741).