mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 10:23:37 +00:00
edits
This commit is contained in:
@ -65,7 +65,7 @@ Once a device has been enrolled and added to a deployment audience, the Windows
|
||||
|
||||
## Create an update policy
|
||||
|
||||
Update policies define how content is deployed to a deployment audience. An [update policy](/graph/api/resources/windowsupdates-updatepolicy) ensures deployments to a deployment audience behave in a consistent manner without having to create and manage multiple individual deployments. When a content approval is added to the policy, it's deployed to the devices in the associated audiences.
|
||||
Update policies define how content is deployed to a deployment audience. An [update policy](/graph/api/resources/windowsupdates-updatepolicy) ensures deployments to a deployment audience behave in a consistent manner without having to create and manage multiple individual deployments. When a content approval is added to the policy, it's deployed to the devices in the associated audiences. The deployment and monitoring settings are optional.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> Any [deployment settings](/graph/api/resources/windowsupdates-deploymentsettings) configured for a [content approval](#approve-driver-content-for-deployment) will be combined with the existing update policy's deployment settings. If the content approval and update policy specify the same deployment setting, the setting from the content approval is used.
|
||||
|
@ -28,6 +28,7 @@ In this article, you will:
|
||||
> * [Create a deployment](#create-a-deployment)
|
||||
> * [Add members to the deployment audience](#add-members-to-the-deployment-audience)
|
||||
> * [Pause a deployment](#pause-a-deployment)
|
||||
> * [Delete a deployment](#delete-a-deployment)
|
||||
> * [Unenroll devices](#unenroll-devices)
|
||||
|
||||
|
||||
@ -89,7 +90,7 @@ The following truncated response displays a **Catalog ID** of `d9049ddb-0ca8-4b
|
||||
|
||||
## Create a deployment
|
||||
|
||||
When creating a deployment for a feature update, there are multiple options available to define how the deployment behaves. The following [deployment settings](/graph/api/resources/windowsupdates-deploymentsettings) are defined in the example request body for deploying the Windows 11, version 22H2 feature update (**Catalog ID** of `d9049ddb-0ca8-4bc1-bd3c-41a456ef300f`):
|
||||
When creating a deployment for a feature update, there are multiple options available to define how the deployment behaves. The deployment and monitoring settings are optional. The following [deployment settings](/graph/api/resources/windowsupdates-deploymentsettings) are defined in the example request body for deploying the Windows 11, version 22H2 feature update (**Catalog ID** of `d9049ddb-0ca8-4bc1-bd3c-41a456ef300f`):
|
||||
|
||||
- Deployment [start date](/graph/api/resources/windowsupdates-schedulesettings) of February 14, 2023 at 5 AM UTC
|
||||
- [Gradual rollout](/graph/api/resources/windowsupdates-gradualrolloutsettings) at a rate of 100 devices every three days
|
||||
@ -274,6 +275,17 @@ content-type: application/json
|
||||
}
|
||||
```
|
||||
|
||||
## Delete a deployment
|
||||
|
||||
To remove the deployment completely, DELETE the deployment. Deleting the deployment will prevent the content from being offered to devices if they haven't already received it. To resume offering the content, a new approval will need to be created.
|
||||
|
||||
|
||||
The following example deletes the deployment with a **Deployment ID** of `de910e12-3456-7890-abcd-ef1234567890`:
|
||||
|
||||
```msgraph-interactive
|
||||
DELETE https://graph.microsoft.com/beta/admin/windows/updates/deployments/de910e12-3456-7890-abcd-ef1234567890
|
||||
```
|
||||
|
||||
## Unenroll devices
|
||||
|
||||
<!--Using include for removing device enrollment-->
|
||||
|
@ -46,8 +46,7 @@ Windows Update for Business deployment service supports Windows client devices o
|
||||
- Look for the folder **C:\Program Files\Microsoft Update Health Tools** or review *Add Remove Programs* for **Microsoft Update Health Tools**.
|
||||
- As an Admin, run the following PowerShell script: `Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -match "Microsoft Update Health Tools"}`
|
||||
|
||||
- To take advantage of [Changes to Windows diagnostic data collection](/windows/privacy/changes-to-windows-diagnostic-data-collection#services-that-rely-on-enhanced-diagnostic-data), installing the February 2023 Cumulative Update, or a later equivalent update, for Windows 10 ([KB5022834](https://support.microsoft.com/help/5022834
|
||||
)) and Windows 11 ([KB5022836](https://support.microsoft.com/help/5022836)) is recommended
|
||||
- To take advantage of [Changes to Windows diagnostic data collection](/windows/privacy/changes-to-windows-diagnostic-data-collection#services-that-rely-on-enhanced-diagnostic-data), installing the February 2023 Cumulative Update, or a later equivalent update, is recommended
|
||||
|
||||
## Diagnostic data requirements
|
||||
|
||||
|
@ -14,7 +14,7 @@ For this article, you'll use Graph Explorer to make requests to the [Microsoft G
|
||||
|
||||
> [!WARNING]
|
||||
>
|
||||
> - Requests listed in this article require signing in with a Microsoft 365 account. Join the [Microsoft 365 Developer Program](https://developer.microsoft.com/microsoft-365/dev-program) to get a free sandbox preconfigured with sample data packs for testing.
|
||||
> - Requests listed in this article require signing in with a Microsoft 365 account. If needed, a free one month trial is available for [Microsoft 365 Business Premium](https://www.microsoft.com/microsoft-365/business/microsoft-365-business-premium).
|
||||
> - Using a test tenant to verify the deployment process first is highly recommended. If you use a production tenant, ensure you verify which client devices you're targeting with deployments.
|
||||
|
||||
1. From a browser, go to [Graph Explorer](https://developer.microsoft.com/graph/graph-explorer) and sign in using an Azure Active Directory (Azure AD) user account.
|
||||
|
Reference in New Issue
Block a user