mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 02:13:43 +00:00
edit
This commit is contained in:
Meghan Stewart
@ -244,7 +244,7 @@ GET https://graph.microsoft.com/beta/admin/windows/updates/deploymentAudiences/d
|
||||
|
||||
The following truncated response displays:
|
||||
- An **Azure AD ID** of `01234567-89ab-cdef-0123-456789abcdef`
|
||||
- The **Catalog ID** of `1d082682ff38a3a885cefd68ec6ab3782be3dc31d156c9e5c6fd3dc55cbd839d`
|
||||
- The **Catalog ID** of `5d6dede684ba5c4a731d62d9c9c2a99db12c5e6015e9f8ad00f3e9387c7f399c`
|
||||
|
||||
```json
|
||||
"matchedDevices": [
|
||||
@ -257,7 +257,17 @@ The following truncated response displays:
|
||||
],
|
||||
"catalogEntry": {
|
||||
"@odata.type": "#microsoft.graph.windowsUpdates.driverUpdateCatalogEntry",
|
||||
"id": "1d082682ff38a3a885cefd68ec6ab3782be3dc31d156c9e5c6fd3dc55cbd839d",
|
||||
"id": "5d6dede684ba5c4a731d62d9c9c2a99db12c5e6015e9f8ad00f3e9387c7f399c",
|
||||
"displayName": "Microsoft - Test - 1.0.0.1",
|
||||
"deployableUntilDateTime": null,
|
||||
"releaseDateTime": "0001-01-21T04:18:32Z",
|
||||
"description": "Microsoft test driver update released in January 2021",
|
||||
"driverClass": "OtherHardware",
|
||||
"provider": "Microsoft",
|
||||
"setupInformationFile": null,
|
||||
"manufacturer": "Microsoft",
|
||||
"version": "1.0.0.1",
|
||||
"versionDateTime": "2021-01-11T02:43:14Z"
|
||||
```
|
||||
|
||||
## Approve driver content for deployment
|
||||
@ -267,7 +277,7 @@ Each driver update is associated with a unique [catalog entry](/graph/api/resour
|
||||
> [!IMPORTANT]
|
||||
> Any [deployment settings](/graph/api/resources/windowsupdates-deploymentsettings) configured for the content approval will be combined with the existing [update policy's](#create-an-update-policy) deployment settings. If the content approval and update policy specify the same deployment setting, the setting from the content approval is used.
|
||||
|
||||
Add a content approval to an existing policy, **Policy ID** `9011c330-1234-5678-9abc-def012345678` for the driver update with the **Catalog ID** `1d082682ff38a3a885cefd68ec6ab3782be3dc31d156c9e5c6fd3dc55cbd839d`. Schedule the start date for February 14, 2023 at 1 AM UTC:
|
||||
Add a content approval to an existing policy, **Policy ID** `9011c330-1234-5678-9abc-def012345678` for the driver update with the **Catalog ID** `5d6dede684ba5c4a731d62d9c9c2a99db12c5e6015e9f8ad00f3e9387c7f399c`. Schedule the start date for February 14, 2023 at 1 AM UTC:
|
||||
|
||||
```http
|
||||
POST https://graph.microsoft.com/beta/admin/windows/updates/updatePolicies/9011c330-1234-5678-9abc-def012345678/complianceChanges
|
||||
@ -279,7 +289,7 @@ Content-type: application/json
|
||||
"@odata.type": "#microsoft.graph.windowsUpdates.catalogContent",
|
||||
"catalogEntry": {
|
||||
"@odata.type": "#microsoft.graph.windowsUpdates.driverUpdateCatalogEntry",
|
||||
"id": "1d082682ff38a3a885cefd68ec6ab3782be3dc31d156c9e5c6fd3dc55cbd839d"
|
||||
"id": "5d6dede684ba5c4a731d62d9c9c2a99db12c5e6015e9f8ad00f3e9387c7f399c"
|
||||
}
|
||||
},
|
||||
"deploymentSettings": {
|
||||
@ -355,7 +365,7 @@ Content-type: application/json
|
||||
}
|
||||
```
|
||||
|
||||
## Remove device enrollment
|
||||
## Unenroll device
|
||||
|
||||
<!--Using include for removing device enrollment-->
|
||||
[!INCLUDE [Graph Explorer enroll devices](./includes/wufb-deployment-graph-unenroll.md)]
|
||||
|
||||
@ -51,7 +51,7 @@ As long as a device remains enrolled in feature update management, the device do
|
||||
[!INCLUDE [Graph Explorer enroll devices](./includes/wufb-deployment-enroll-device-graph-explorer.md)]
|
||||
|
||||
|
||||
## Remove device enrollment
|
||||
## Unenroll devices
|
||||
|
||||
<!--Using include for removing device enrollment-->
|
||||
[!INCLUDE [Graph Explorer enroll devices](./includes/wufb-deployment-graph-unenroll.md)]
|
||||
@ -10,7 +10,7 @@ ms.localizationpriority: medium
|
||||
---
|
||||
<!--This file is shared by deployment-service-drivers.md and the deployment-service-feature-updates.md articles. Headings may be driven by article context. 7512398 -->
|
||||
|
||||
You enroll devices based on the types of updates you want them to recieve.Currently, you can enroll devices to receive feature updates (`feature`) or drivers (`driver`). You can enroll devices to receive updates from multiple update classifications.
|
||||
You enroll devices based on the types of updates you want them to receive. Currently, you can enroll devices to receive feature updates (`feature`) or drivers (`driver`). You can enroll devices to receive updates from multiple update classifications.
|
||||
|
||||
1. To enroll devices, POST to [updatableAssets](/graph/api/resources/windowsupdates-updatableasset) using [enrollAssets](/graph/api/windowsupdates-updatableasset-enrollassets). The following example enrolls three devices to receive driver updates:
|
||||
1. In Graph Explorer, select **POST** from the drop-down list for the HTTP verb.
|
||||
|
||||
@ -10,12 +10,13 @@ ms.localizationpriority: medium
|
||||
---
|
||||
<!--This file is shared by deployment-service-drivers.md and the deployment-service-feature-updates.md articles. Headings may be driven by article context. 7512398 -->
|
||||
|
||||
When a device no longer needs to be managed by the deployment service, remove the enrollment it. Just like [enrolling a device](#enroll-devices), specify either `driver` or `feature` as the value for the `updateCategory`. The device will no longer receive updates from the deployment service for the specfied update category, even if it's still assigned to an active deployment. Depending on the device's configuration, it may start to receive updates from Windows Update. For instance, if a device is still enrolled for feature updates, but the enrollment for drivers is removed:
|
||||
- Existing driver deployments from the service won't be installed
|
||||
When a device no longer needs to be managed by the deployment service, unenroll it. Just like [enrolling a device](#enroll-devices), specify either `driver` or `feature` as the value for the `updateCategory`. The device will no longer receive updates from the deployment service for the specified update category. Depending on the device's configuration, it may start to receive updates from Windows Update. For instance, if a device is still enrolled for feature updates, but it's unenrolled from drivers:
|
||||
|
||||
- Existing driver deployments from the service won't be offered to the device
|
||||
- The device will continue to receive feature updates from the deployment service
|
||||
- Drivers may start being installed from Windows Update depending on the device's configuration
|
||||
|
||||
To remove device enrollment, POST to [updatableAssets](/graph/api/resources/windowsupdates-updatableasset) using [unenrollAssets](/graph/api/windowsupdates-updatableasset-unenrollassets). In the request body, specify:
|
||||
To unenroll a device, POST to [updatableAssets](/graph/api/resources/windowsupdates-updatableasset) using [unenrollAssets](/graph/api/windowsupdates-updatableasset-unenrollassets). In the request body, specify:
|
||||
- **Azure AD Device ID** as `id` for the device
|
||||
- Either `feature` or `driver` for the updateCategory
|
||||
|
||||
|
||||
Reference in New Issue
Block a user