deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-12 13:27:23 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

edits

Browse Source
This commit is contained in:
Meghan Stewart 2023-01-25 08:57:19 -08:00
parent a5e5926bfc
commit d30ca671ee
5 changed files with 22 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
windows/deployment/update/deployment-service-drivers.md
View File

@ -31,5 +31,11 @@ In this tutorial, you will:
## Run queries to identify test devices
<!--Using include for Graph Explorer device queries-->
[!INCLUDE [Graph Explorer device queries](./includes/wufb-deployment-find-device-name.md)]
[!INCLUDE [Graph Explorer device queries](./includes/wufb-deployment-find-device-name-graph-explorer.md)]
## Enroll devices
When you enroll devices into driver management, the deployment service becomes the authority for driver updates coming from Windows Update. Devices don't receive drivers from Windows Update until a deployment is manually created or they're added to a driver update policy with approvals.
<!--Using include for enrolling devices using Graph Explorer-->
[!INCLUDE [Graph Explorer enroll devices](./includes/wufb-deployment-enroll-device-graph-explorer.md)]

2
windows/deployment/update/deployment-service-expedited-updates.md
View File

@ -34,7 +34,7 @@ In this tutorial, you will:
## Run queries to identify test devices
<!--Using include for Graph Explorer device queries-->
[!INCLUDE [Graph Explorer device queries](./includes/wufb-deployment-find-device-name.md)]
[!INCLUDE [Graph Explorer device queries](./includes/wufb-deployment-find-device-name-graph-explorer.md)]
## Enroll devices

9
windows/deployment/update/deployment-service-feature-updates.md
View File

@ -29,4 +29,11 @@ In this tutorial, you will:
## Run queries to identify test devices
<!--Using include for Graph Explorer device queries-->
[!INCLUDE [Graph Explorer device queries](./includes/wufb-deployment-find-device-name.md)]
[!INCLUDE [Graph Explorer device queries](./includes/wufb-deployment-find-device-name-graph-explorer.md)]
## Enroll devices
As long as a device remains enrolled in feature update management, the device doesn't receive any other feature updates from Windows Update unless explicitly deployed using the deployment service.
<!--Using include for enrolling devices using Graph Explorer-->
[!INCLUDE [Graph Explorer enroll devices](./includes/wufb-deployment-enroll-device-graph-explorer.md)]

7
windows/deployment/update/includes/wufb-deployment-enroll-device.md → windows/deployment/update/includes/wufb-deployment-enroll-device-graph-explorer.md
View File

@ -10,12 +10,9 @@ ms.localizationpriority: medium
---
<!--This file is shared by deployment-service-drivers.md, deployment-service-expedited-updates.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 (`drivers`). You can enroll devices to receive updates from multiple update classifications.
- As long as a device remains enrolled in feature update management, the device doesn't receive any other feature updates from Windows Update unless explicitly deployed using the deployment service.
- When you enroll devices into driver management, the deployment service becomes the authority for driver updates coming from Windows Update. Devices don't receive drivers from Windows Update until a deployment is manually created or they're added to a driver update policy with approvals.
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.
1.
```rest
POST https://graph.microsoft.com/beta/admin/windows/updates/updatableAssets/enrollAssets

7
windows/deployment/update/includes/wufb-deployment-find-device-name.md → windows/deployment/update/includes/wufb-deployment-find-device-name-graph-explorer.md
View File

@ -12,13 +12,13 @@ ms.localizationpriority: medium
You will need at least [Device.Read.All](/graph/permissions-reference#device-permissions) permission to display [device](/graph/api/resources/device) information.
Displays the AzureAD ID and name of all devices:
Displays the AzureAD device ID and name of all devices:
```rest
GET https://graph.microsoft.com/v1.0/devices?$select=deviceid,displayName
```
Displays the AzureAD ID for a device name that starts with `Test`:
Displays the AzureAD device ID for a device name that starts with `Test`:
```rest
GET https://graph.microsoft.com/v1.0/devices?$filter=startswith(displayName,'Test')&$select=deviceid,displayName
@ -34,7 +34,7 @@ For the next requests, set the **ConsistencyLevel** header to `eventual`. For mo
:::image type="content" source="../media/7512398-deployment-service-graph-modify-header.png" alt-text="Screenshot of the request headers tab in Graph Explorer":::
Displays the name and operating system version for the device that has the AzureAD ID of `01234567-89ab-cdef-0123-456789abcdef`:
Displays the name and operating system version for the device that has the AzureAD device ID of `01234567-89ab-cdef-0123-456789abcdef`:
```rest
GET https://graph.microsoft.com/v1.0/devices?$search="deviceid:01234567-89ab-cdef-0123-456789abcdef"?$select=displayName,operatingSystemVersion
@ -45,3 +45,4 @@ Find devices that don't have virtual machine listed as the model and that have a
```rest
GET https://graph.microsoft.com/v1.0/devices?$filter=model ne 'virtual machine' and NOT(manufacturer eq null)&$count=true&$select=deviceid,displayName,operatingSystemVersion
```