mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 21:37:22 +00:00
commit
8b26839eb9
@ -11,7 +11,7 @@ ms.localizationpriority: medium
|
||||
appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
ms.date: 04/22/2024
|
||||
ms.date: 04/01/2025
|
||||
---
|
||||
|
||||
# Use Windows Update client policies and WSUS together
|
||||
@ -23,7 +23,9 @@ The Windows update scan source policy enables you to choose what types of update
|
||||
We added the scan source policy starting with the [September 1, 2021—KB5005101 (OS Builds 19041.1202, 19042.1202, and 19043.1202) Preview](https://support.microsoft.com/help/5005101) update and it applies to Window 10, version 2004 and above and Windows 11. This policy changes the way devices determine whether to scan against a local WSUS server or Windows Update service.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> The policy **Do not allow update deferral policies to cause scans against Windows Update**, also known as Dual Scan, is no longer supported on Windows 11 and on Windows 10 it's replaced by the new Windows scan source policy and isn't recommended for use. If you configure both on Windows 10, you won't get updates from Windows Update.
|
||||
> - If you use Configuration Manager and have co-managed devices, see [Integrate with Windows Update client policies](/intune/configmgr/sum/deploy-use/integrate-windows-update-for-business-windows-10) for more information about configuring clients.
|
||||
> - The policy **Do not allow update deferral policies to cause scans against Windows Update**, also known as Dual Scan, is no longer supported on Windows 11 and on Windows 10 it's replaced by the new Windows scan source policy and isn't recommended for use. If you configure both on Windows 10, you won't get updates from Windows Update.
|
||||
|
||||
|
||||
## About the scan source policy
|
||||
|
||||
@ -38,13 +40,13 @@ We recommend using this policy on your transition from fully on-premises managed
|
||||
|
||||
## Default scan behavior
|
||||
|
||||
To help you better understand the scan source policy, see the default scan behavior below and how we can change it:
|
||||
To help you better understand the scan source policy, see the following default scan behavior and how we can change it:
|
||||
|
||||
- If no policies are configured: All of your updates will come from Windows Update.
|
||||
- If no policies are configured: All of your updates come from Windows Update.
|
||||
- If you configure only the WSUS server policy:
|
||||
|
||||
- On Windows 10: All of your updates will come from WSUS.
|
||||
- On Windows 11: All of your updates will still come from WSUS unless you configure the specify scan source policy.
|
||||
- On Windows 10: All of your updates come from WSUS.
|
||||
- On Windows 11: All of your updates still come from WSUS unless you configure the specify scan source policy.
|
||||
|
||||
- If you configure a WSUS server and deferral policies on Windows 10: All of your updates will come from Windows Update unless you specify the scan source policy or have disabled dual scan.
|
||||
- If you configure a WSUS server and the scan source policy: All of your updates will come from the source chosen in the scan source policy.
|
||||
|
Loading…
x
Reference in New Issue
Block a user