mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 18:33:43 +00:00
formatting
This commit is contained in:
@ -17,6 +17,7 @@ ms.date: 02/14/2023
|
||||
|
||||
In this article, you will:
|
||||
> [!div class="checklist"]
|
||||
>
|
||||
> - [Open Graph Explorer](#open-graph-explorer)
|
||||
> - [Run queries to identify test devices](#run-queries-to-identify-devices)
|
||||
> - [Enroll devices](#enroll-devices)
|
||||
@ -30,6 +31,7 @@ In this article, you will:
|
||||
## Prerequisites
|
||||
|
||||
All of the [prerequisites for the Windows Update for Business deployment service](deployment-service-overview.md#prerequisites) must be met.
|
||||
|
||||
### Permissions
|
||||
|
||||
<!--Using include for Graph Explorer permissions-->
|
||||
@ -74,6 +76,7 @@ When you enroll devices into driver management, the deployment service becomes t
|
||||
}
|
||||
```
|
||||
|
||||
|
||||
1. Add devices, using their **Azure AD 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 **Azure AD ID** of the device.
|
||||
|
||||
```rest
|
||||
@ -201,7 +204,11 @@ Content-type: application/json
|
||||
|
||||
## Review applicable driver content
|
||||
|
||||
Once Windows Update for Business deployment service has scan results from devices, the applicability for driver and firmware updates can be displayed for a deployment audience.
|
||||
Once Windows Update for Business deployment service has scan results from devices, the applicability for driver and firmware updates can be displayed for a deployment audience. Each applicable update returns the following information:
|
||||
|
||||
- An `id` for its [catalog entry](/graph/api/resources/windowsupdates-catalogentry)
|
||||
- The **Azure AD ID** of the devices it's applicable to
|
||||
- Information describing the update such as the name and version.
|
||||
|
||||
To display [applicable content](/graph/api/resources/windowsupdates-applicablecontent), run a query using the **Audience ID**, for example `d39ad1ce-0123-4567-89ab-cdef01234567`:
|
||||
|
||||
@ -209,12 +216,6 @@ To display [applicable content](/graph/api/resources/windowsupdates-applicableco
|
||||
GET https://graph.microsoft.com/beta/admin/windows/updates/deploymentAudiences/d39ad1ce-0123-4567-89ab-cdef01234567/applicableContent
|
||||
```
|
||||
|
||||
Each applicable update returns the following information:
|
||||
|
||||
- An `id` for its [catalog entry](/graph/api/resources/windowsupdates-catalogentry)
|
||||
- The **Azure AD ID** of the devices it's applicable to
|
||||
- Information describing the update such as the name and version.
|
||||
|
||||
The following truncated response displays:
|
||||
- An **Azure AD ID** of `01234567-89ab-cdef-0123-456789abcdef`
|
||||
- The **Catalog ID** of `1d082682ff38a3a885cefd68ec6ab3782be3dc31d156c9e5c6fd3dc55cbd839d`
|
||||
@ -266,7 +267,6 @@ Content-type: application/json
|
||||
|
||||
Review the compliance changes to a policy with the most recent changes listed in the response first. The following example returns the compliance changes for a policy with the **Policy ID** `9011c330-1234-5678-9abc-def012345678` and sorts by `createdDateTime` in descending order:
|
||||
|
||||
|
||||
```rest
|
||||
GET https://graph.microsoft.com/beta/admin/windows/updates/updatePolicies/9011c330-1234-5678-9abc-def012345678/complianceChanges?orderby=createdDateTime desc
|
||||
|
||||
@ -276,7 +276,6 @@ GET https://graph.microsoft.com/beta/admin/windows/updates/updatePolicies/9011c3
|
||||
|
||||
Approval for content can be revoked by setting the `isRevoked` property of the [compliance change](/graph/api/resources/windowsupdates-compliance) to true. This setting can be changed while a deployment is in progress. However, revoking will only prevent the content from being offered to devices if they haven't already received it. To resume offering the content, a new [approval](#approve-driver-content-for-deployment) will need to be created.
|
||||
|
||||
|
||||
### Request
|
||||
|
||||
```http
|
||||
|
@ -12,19 +12,16 @@ ms.localizationpriority: medium
|
||||
|
||||
Use the [device](/graph/api/resources/device) resource type to find clients to enroll into the deployment service. Change the query parameters to fit your specific needs. For more information, see [Use query parameters](/graph/query-parameters).
|
||||
|
||||
Displays the **AzureAD Device 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
|
||||
```
|
||||
`GET https://graph.microsoft.com/v1.0/devices?$select=deviceid,displayName`
|
||||
|
||||
Displays the **AzureAD Device ID** and **Name** for device names that starts with `Test`:
|
||||
- Displays the **AzureAD Device ID** and **Name** for devices that have a name starting with `Test`:
|
||||
|
||||
```rest
|
||||
GET https://graph.microsoft.com/v1.0/devices?$filter=startswith(displayName,'Test')&$select=deviceid,displayName
|
||||
```
|
||||
`GET https://graph.microsoft.com/v1.0/devices?$filter=startswith (displayName,'Test')&$select=deviceid,displayName`
|
||||
|
||||
### Add a request header
|
||||
|
||||
### Add a request header for advanced queries
|
||||
|
||||
For the next requests, set the **ConsistencyLevel** header to `eventual`. For more information about advanced query parameters, see [Advanced query capabilities on Azure AD directory objects](/graph/aad-advanced-queries).
|
||||
|
||||
@ -34,17 +31,14 @@ 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" lightbox="../media/7512398-deployment-service-graph-modify-header.png":::
|
||||
|
||||
Displays the **Name** and **Operating system version** for the device that has the **AzureAD Device ID** of `01234567-89ab-cdef-0123-456789abcdef`:
|
||||
- Display the **Name** and **Operating system version** for the device that has `01234567-89ab-cdef-0123-456789abcdef` as the **AzureAD Device ID**:
|
||||
|
||||
```rest
|
||||
GET https://graph.microsoft.com/v1.0/devices?$search="deviceid:01234567-89ab-cdef-0123-456789abcdef"?$select=displayName,operatingSystemVersion
|
||||
```
|
||||
`GET https://graph.microsoft.com/v1.0/devices?$search="deviceid:01234567-89ab-cdef-0123-456789abcdef"?$select=displayName,operatingSystemVersion`
|
||||
|
||||
To find devices that likely aren't virtual machines, filter for devices that don't have virtual machine listed as the model but do have a manufacturer listed. Display the **AzureAD Device ID**, **Name**, and **Operating system version** for each device:
|
||||
- To find devices that likely aren't virtual machines, filter for devices that don't have virtual machine listed as the model but do have a manufacturer listed. Display the **AzureAD Device ID**, **Name**, and **Operating system version** for each device:
|
||||
|
||||
`GET https://graph.microsoft.com/v1.0/devices?$filter=model ne 'virtual machine' and NOT(manufacturer eq null)&$count=true&$select=deviceid,displayName,operatingSystemVersion`
|
||||
|
||||
```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
|
||||
```
|
||||
|
||||
> [!Tip]
|
||||
> Requests using the [device](/graph/api/resources/device) resource type typically have both an `id` and a `deviceid`:
|
||||
|
Reference in New Issue
Block a user