mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 02:13:43 +00:00
driver-policy-edit
This commit is contained in:
@ -330,3 +330,8 @@ GET https://graph.microsoft.com/beta/admin/windows/updates/deployments?orderby=c
|
||||
|
||||
<!--Using include for removing device enrollment-->
|
||||
[!INCLUDE [Graph Explorer enroll devices](./includes/wufb-deployment-graph-unenroll.md)]
|
||||
|
||||
## Policy considerations for drivers
|
||||
|
||||
<!--Using include for Policy considerations for drivers-->
|
||||
[!INCLUDE [Windows Update for Business deployment service driver policy considerations](./includes/wufb-deployment-driver-policy-considerations.md)]
|
@ -91,6 +91,12 @@ When you use [Windows Update for Business reports](wufb-reports-overview.md) in
|
||||
<!--Using include for deployment service limitations-->
|
||||
[!INCLUDE [Windows Update for Business deployment service limitations](./includes/wufb-deployment-limitations.md)]
|
||||
|
||||
## Policy considerations for drivers
|
||||
|
||||
<!--Using include for Policy considerations for drivers-->
|
||||
[!INCLUDE [Windows Update for Business deployment service driver policy considerations](./includes/wufb-deployment-driver-policy-considerations.md)]
|
||||
|
||||
|
||||
## General tips for the deployment service
|
||||
|
||||
Follow these suggestions for the best results with the service:
|
||||
|
@ -54,3 +54,8 @@ While expedite update deployments will override an update deferral for the updat
|
||||
|
||||
<!--Using include for Update Health Tools log location-->
|
||||
[!INCLUDE [Windows Update for Business deployment service permissions using Graph Explorer](./includes/wufb-deployment-update-health-tools-logs.md)]
|
||||
|
||||
## Policy considerations for drivers
|
||||
|
||||
<!--Using include for Policy considerations for drivers-->
|
||||
[!INCLUDE [Windows Update for Business deployment service driver policy considerations](./includes/wufb-deployment-driver-policy-considerations.md)]
|
||||
|
@ -0,0 +1,18 @@
|
||||
---
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
manager: aaroncz
|
||||
ms.technology: itpro-updates
|
||||
ms.prod: windows-client
|
||||
ms.topic: include
|
||||
ms.date: 02/14/2023
|
||||
ms.localizationpriority: medium
|
||||
---
|
||||
<!--This file is shared by deployment-service-drivers.md, deployment-service-troubleshoot.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 through the deployment service, 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 table describes driver related update policies that can affect deployments through the deployment service:
|
||||
|
||||
| Description of policies | Locations | Behavior with the deployment service|
|
||||
|---|---|---|
|
||||
| Policies that exclude drivers from Windows Update for a device | - **Group Policy**: `\Windows Components\Windows Update\Do not include drivers with Windows Updates` set to `enabled` </br> - **CSP**: [ExcludeWUDriversInQualityUpdate](/windows/client-management/mdm/policy-csp-update#excludewudriversinqualityupdate) set to `1` </br> - **Registry**: `HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\ExcludeWUDriversFromQualityUpdates` set to `1`</br> - **Intune**: [**Windows Drivers** update setting](/mem/intune/protect/windows-update-settings#update-settings) for the update ring set to `Allow` | Devices that are enrolled for **drivers** and added to an audience though the deployment service: </br></br> - Won't install drivers that are approved from the deployment service </br> - Will display the applicable driver content in the deployment service |
|
||||
| Policies that define the source for driver updates as either Windows Update or Windows Server Update Service (WSUS)| - **Group Policy**: `\Windows Components\Windows Update\Manage updates offered from Windows Server Update Service\Specify source service for specific classes of Windows Updates` set to `enabled` with the `Driver Updates` option set to `Windows Update`</br> - **CSP**: [SetPolicyDrivenUpdateSourceForDriverUpdates](/windows/client-management/mdm/policy-csp-update#setpolicydrivenupdatesourcefordriverupdates) set to `0` for Windows Update as the source</br> - **Registry**: `HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\SetPolicyDrivenUpdateSourceForDriverUpdates` set to `0`. Under `\AU`, `UseUpdateClassPolicySource` also needs to be set to `1`</br> - **Intune**: Not applicable. Intune deploys updates using Windows Update for Business. [Co-managed clients from Configuration Manager](/mem/configmgr/comanage/overview?toc=/mem/configmgr/cloud-attach/toc.json&bc=/mem/configmgr/cloud-attach/breadcrumb/toc.json) with the workload for Windows Update policies set to Intune will also use Windows Update for Business. | Devices that are enrolled for **drivers** and added to an audience though the deployment service: </br></br> - Will display the applicable driver content in the deployment service </br> - Will install drivers that are approved from the deployment service |
|
@ -1,21 +0,0 @@
|
||||
---
|
||||
author: mestew
|
||||
ms.author: mstewart
|
||||
manager: aaroncz
|
||||
ms.technology: itpro-updates
|
||||
ms.prod: windows-client
|
||||
ms.topic: include
|
||||
ms.date: 02/14/2023
|
||||
ms.localizationpriority: medium
|
||||
---
|
||||
<!--This file is shared by deployment-service-drivers.md, deployment-service-troubleshoot.md, and the deployment-service-prerequisites.md articles. Headings may be driven by article context. 7512398 -->
|
||||
|
||||
## Policy considerations
|
||||
|
||||
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 policies to fit their needs. For instance, they may want to review applicable driver content, but not approve it for install through the deployment service. Configuring this sort of behavior can be useful, especially when transitioning driver update management due to changing organizational needs.
|
||||
|
||||
| Policy | Behavior |
|
||||
|---|---|
|
||||
|
|
||||
|
||||
|
@ -142,7 +142,7 @@ To add more flexibility to the update process, settings are available to control
|
||||
|
||||
[Configure Automatic Updates](#configure-automatic-updates) offers four different options for automatic update installation, while [Do not include drivers with Windows Updates](#do-not-include-drivers-with-windows-updates) makes sure drivers are not installed with the rest of the received updates.
|
||||
|
||||
### Do not include drivers with Windows Updates
|
||||
### Do not include drivers with Windows Updates
|
||||
|
||||
Allows admins to exclude Windows Update drivers during updates.
|
||||
|
||||
|
@ -71,7 +71,7 @@ Drivers are automatically enabled because they are beneficial to device systems.
|
||||
We also recommend that you allow Microsoft product updates as discussed previously.
|
||||
|
||||
### Set when devices receive feature and quality updates
|
||||
|
||||
|
||||
#### I want to receive pre-release versions of the next feature update
|
||||
|
||||
1. Ensure that you are enrolled in the Windows Insider Program for Business. This is a completely free program available to commercial customers to aid them in their validation of feature updates before they are released. Joining the program enables you to receive updates prior to their release as well as receive emails and content related to what is coming in the next updates.
|
||||
|
Reference in New Issue
Block a user