mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-18 11:53:37 +00:00
Merge branch 'main' into vp-manage-qa2
This commit is contained in:
Vinay Pamnani
GitHub
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Update Policy CSP
|
||||
description: Learn more about the Update Area in Policy CSP.
|
||||
ms.date: 02/14/2024
|
||||
ms.date: 02/14/2024
|
||||
---
|
||||
|
||||
<!-- Auto-Generated CSP Document -->
|
||||
@ -1556,7 +1556,8 @@ Configure this policy to specify whether to receive **Windows Feature Updates**
|
||||
- SetPolicyDrivenUpdateSourceForOtherUpdates
|
||||
|
||||
> [!NOTE]
|
||||
> If you have not properly configured Update/UpdateServiceUrl correctly to point to your WSUS server, this policy will have no effect.
|
||||
> - If you have not properly configured Update/UpdateServiceUrl correctly to point to your WSUS server, this policy will have no effect.
|
||||
> - If you're also using the **Specify settings for optional component installation and component repair** ([ADMX_Servicing](policy-csp-admx-servicing.md)) policy to enable content for FoDs and language packs, see [How to make Features on Demand and language packs available when you're using WSUS or Configuration Manager](/windows/deployment/update/fod-and-lang-packs) to verify your policy configuration.
|
||||
<!-- SetPolicyDrivenUpdateSourceForFeatureUpdates-Editable-End -->
|
||||
|
||||
<!-- SetPolicyDrivenUpdateSourceForFeatureUpdates-DFProperties-Begin -->
|
||||
@ -1694,7 +1695,8 @@ Configure this policy to specify whether to receive **Windows Quality Updates**
|
||||
- SetPolicyDrivenUpdateSourceForOtherUpdates
|
||||
|
||||
> [!NOTE]
|
||||
> If you have not properly configured Update/UpdateServiceUrl correctly to point to your WSUS server, this policy will have no effect.
|
||||
> - If you have not properly configured Update/UpdateServiceUrl correctly to point to your WSUS server, this policy will have no effect.
|
||||
> - If you're also using the **Specify settings for optional component installation and component repair** ([ADMX_Servicing](policy-csp-admx-servicing.md)) policy to enable content for FoDs and language packs, see [How to make Features on Demand and language packs available when you're using WSUS or Configuration Manager](/windows/deployment/update/fod-and-lang-packs) to verify your policy configuration.
|
||||
<!-- SetPolicyDrivenUpdateSourceForQualityUpdates-Editable-End -->
|
||||
|
||||
<!-- SetPolicyDrivenUpdateSourceForQualityUpdates-DFProperties-Begin -->
|
||||
|
||||
@ -372,6 +372,8 @@
|
||||
href: update/update-other-microsoft-products.md
|
||||
- name: Delivery Optimization reference
|
||||
href: do/waas-delivery-optimization-reference.md?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json
|
||||
- name: FoD and language packs for WSUS and Configuration Manager
|
||||
href: update/fod-and-lang-packs.md
|
||||
- name: Windows client in S mode
|
||||
href: s-mode.md
|
||||
- name: Switch to Windows client Pro or Enterprise from S mode
|
||||
|
||||
@ -3,7 +3,7 @@ title: FoD and language packs for WSUS and Configuration Manager
|
||||
description: Learn how to make FoD and language packs available to clients when you're using WSUS or Configuration Manager.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: conceptual
|
||||
ms.topic: reference
|
||||
ms.author: mstewart
|
||||
author: mestew
|
||||
ms.localizationpriority: medium
|
||||
@ -13,28 +13,44 @@ appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/mem/configmgr/ > Microsoft Configuration Manager</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows-server/administration/windows-server-update-services/get-started/windows-server-update-services-wsus > WSUS </a>
|
||||
ms.date: 03/13/2019
|
||||
ms.date: 04/22/2024
|
||||
---
|
||||
|
||||
# How to make Features on Demand and language packs available when you're using WSUS or Configuration Manager
|
||||
|
||||
This reference article describes how to make Features on Demand (FoDs) and language packs available when you're using Windows Server Update Services (WSUS) or Configuration Manager for specific versions of Windows.
|
||||
|
||||
This article describes how to make Features on Demand and language packs available when you're using WSUS or Configuration Manager for specific versions of Windows.
|
||||
## High-level changes affecting Features on Demand and language pack content
|
||||
|
||||
## Version information for Features on Demand and language packs
|
||||
The following changes for FoD and language pack content affected how client policy needs to be configured:
|
||||
|
||||
- Starting in Windows 10 version 1709, you can't use WSUS to host [Features on Demand](/windows-hardware/manufacture/desktop/features-on-demand-v2--capabilities) (FoDs) locally.
|
||||
- Starting with Windows 10 version 1803, language packs can no longer be hosted on WSUS.
|
||||
|
||||
In Windows 10 version 21H2 and later, non-Administrator user accounts can add both a display language and its corresponding language features.
|
||||
Due to these changes, the **Specify settings for optional component installation and component repair** ([ADMX_Servicing](/windows/client-management/mdm/policy-csp-admx-servicing)) policy, located under `Computer Configuration\Administrative Templates\System` was used to specify alternate ways to acquire FoDs and language packs, along with content for corruption repair. This policy allows specifying one alternate location. It's important to note the policy behaves differently across OS versions. For more information, see the [Version specific information for Features on Demand and language packs](#version-specific-information-for-features-on-demand-and-language-packs) section.
|
||||
|
||||
As of Windows 10 version 1709, you can't use Windows Server Update Services (WSUS) to host [Features on Demand](/windows-hardware/manufacture/desktop/features-on-demand-v2--capabilities) (FODs) locally. Starting with Windows 10 version 1803, language packs can no longer be hosted on WSUS.
|
||||
The introduction of the **Specify source service for specific classes of Windows Updates** ([SetPolicyDrivenUpdateSourceFor<UpdateClass\>](/windows/client-management/mdm/policy-csp-update#setpolicydrivenupdatesourceforfeatureupdates)) policy in Windows 10, version 2004 further complicated configuring settings for FoD and language pack content.
|
||||
|
||||
The **Specify settings for optional component installation and component repair** policy, located under `Computer Configuration\Administrative Templates\System` in the Group Policy Editor, can be used to specify alternate ways to acquire FOD packages, language packages, and content for corruption repair. However, it's important to note this policy only allows specifying one alternate location and behaves differently across OS versions.
|
||||
Starting in Windows 11, version 22H2, on-premises Unified Update Platform (UUP) updates were introduced. FoDs and language packs are available from WSUS again. It's no longer necessary to use the **Specify settings for optional component installation and component repair** policy for FoD and language pack content.
|
||||
|
||||
In Windows 10 versions 1709 and 1803, changing the **Specify settings for optional component installation and component repair** policy to download content from Windows Update enables acquisition of FOD packages while also enabling corruption repair. Specifying a network location works for either, depending on the content is found at that location. Changing this policy on these OS versions doesn't influence how language packs are acquired.
|
||||
## Version specific information for Features on Demand and language packs
|
||||
|
||||
In Windows 10 version 1809 and beyond, changing the **Specify settings for optional component installation and component repair** policy also influences how language packs are acquired, however language packs can only be acquired directly from Windows Update. It's currently not possible to acquire them from a network share. Specifying a network location works for FOD packages or corruption repair, depending on the content at that location.
|
||||
Windows 11, version 22H2, and later clients use on-premises Unified Update Platform (UUP) updates with WSUS and Microsoft Configuration Manager. These clients don't need to use **Specify settings for optional component installation and component repair** for FoDs and language packs since the content is available in WSUS due to on-premises UUP.
|
||||
|
||||
For Windows 10, version 2004 through Windows 11, version 21H2, clients can't download FoDs or language packs when **Specify settings for optional component installation and component repair** is set to Windows Update and **Specify source service for specific classes of Windows Updates** ([SetPolicyDrivenUpdateSourceFor<FeatureUpdates/QualityUpdates>](/windows/client-management/mdm/policy-csp-update#setpolicydrivenupdatesourceforfeatureupdates)) for either feature or quality updates is set to WSUS. If you need this content, you can set **Specify settings for optional component installation and component repair** to Windows Update and then either:
|
||||
- Change the source selection for feature and quality updates to Windows Update
|
||||
- Allow all classes of updates to come from WSUS by not configuring any source selections <!--8907933-->
|
||||
|
||||
> [!Note]
|
||||
> In Windows 10 version 21H2 and later, non-Administrator user accounts can add both a display language and its corresponding language features.
|
||||
|
||||
In Windows 10 version 1809 and later, changing the **Specify settings for optional component installation and component repair** policy also influences how language packs are acquired, however language packs can only be acquired directly from Windows Update (until Windows 11 version 22H2). It's currently not possible to acquire them from a network share. Specifying a network location works for FoD packages or corruption repair, depending on the content at that location.
|
||||
|
||||
In Windows 10 versions 1709 and 1803, changing the **Specify settings for optional component installation and component repair** policy to download content from Windows Update enables acquisition of FoD packages while also enabling corruption repair. Specifying a network location works for either, depending on the content is found at that location. Changing this policy on these OS versions doesn't influence how language packs are acquired.
|
||||
|
||||
For all OS versions, changing the **Specify settings for optional component installation and component repair** policy doesn't affect how OS updates are distributed. They continue to come from WSUS, Configuration Manager, or other sources as you have scheduled them, even while optional content is sourced from Windows Update or a network location.
|
||||
|
||||
Learn about other client management options, including using Group Policy and administrative templates, in [Manage clients in Windows 10](/windows/client-management/).
|
||||
Learn about other client management options, including using Group Policy and administrative templates, in [Manage Windows clients](/windows/client-management/).
|
||||
|
||||
## More resources
|
||||
|
||||
|
||||
@ -11,11 +11,11 @@ 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: 03/15/2023
|
||||
ms.date: 04/22/2024
|
||||
---
|
||||
|
||||
# Migrating and acquiring optional Windows content during updates
|
||||
|
||||
|
||||
This article provides some background on the problem of keeping language resources and Features on Demand during operating system updates and offers guidance to help you move forward in the short term and prepare for the long term.
|
||||
|
||||
When you update the operating system, it's critical to keep language resources and Features on Demand (FODs). Many commercial organizations use Configuration Manager or other management tools to distribute and orchestrate Windows client setup using a local Windows image or WIM file (a *media-based* or *task-sequence-based* update). Others do in-place updates using an approved Windows client feature update by using Windows Server Update Services (WSUS), Configuration Manager, or equivalent tools (a *servicing-based* update).
|
||||
@ -28,7 +28,8 @@ Optional content includes the following items:
|
||||
|
||||
- General Features on Demand also referred to as FODs (for example, Windows Mixed Reality)
|
||||
- Language-based and regional FODs (for example, Language.Basic~~~ja-jp~0.0.1.0)
|
||||
- Local Experience Packs
|
||||
- Local Experience Packs
|
||||
- Language packs
|
||||
|
||||
Optional content isn't included by default in the Windows image file that is part of the operating system media available in the Volume Licensing Service Center (VLSC). Instead, it's released as an additional ISO file on VLSC. Shipping these features out of the operating system media and shipping them separately reduces the disk footprint of Windows. This approach provides more space for user's data. It also reduces the time needed to service the operating system, whether installing a monthly quality update or upgrading to a newer version. A smaller default Windows image also means less data to transmit over the network.
|
||||
|
||||
@ -137,7 +138,8 @@ Several of the options address ways to address optional content migration issues
|
||||
- This setting doesn't support installing language packs from an alternate source file path, only Features on Demand. If the policy is configured to acquire content from Windows Update, language packs will be acquired.
|
||||
- If this setting isn't configured or disabled, files are downloaded from the default Windows Update location, for example Windows Update for Business or WSUS.
|
||||
|
||||
For more information, see [Configure a Windows Repair Source](/windows-hardware/manufacture/desktop/configure-a-windows-repair-source).
|
||||
|
||||
For more information, see [Configure a Windows Repair Source](/windows-hardware/manufacture/desktop/configure-a-windows-repair-source) and [How to make Features on Demand and language packs available when you're using WSUS or Configuration Manager](fod-and-lang-packs.md).
|
||||
|
||||
|
||||
## More resources
|
||||
|
||||
@ -15,11 +15,11 @@ 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>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows-server/administration/windows-server-update-services/get-started/windows-server-update-services-wsus > WSUS </a>
|
||||
ms.date: 12/31/2017
|
||||
ms.date: 04/22/2024
|
||||
---
|
||||
|
||||
# Deploy Windows client updates using Windows Server Update Services (WSUS)
|
||||
|
||||
|
||||
> **Looking for consumer information?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq)
|
||||
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ manager: aaroncz
|
||||
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: 12/15/2023
|
||||
ms.date: 04/22/2024
|
||||
---
|
||||
|
||||
# Windows Update for Business reports prerequisites
|
||||
@ -35,8 +35,9 @@ Before you begin the process of adding Windows Update for Business reports to yo
|
||||
|
||||
## Operating systems and editions
|
||||
|
||||
- Windows 11 Professional, Education, Enterprise, and [Enterprise multi-session](/azure/virtual-desktop/windows-10-multisession-faq) editions
|
||||
- Windows 10 Professional, Education, Enterprise, and [Enterprise multi-session](/azure/virtual-desktop/windows-10-multisession-faq) editions
|
||||
- Windows 11 Professional, Education, and Enterprise editions <!--8928451-->
|
||||
- Windows 10 Professional, Education, and Enterprise editions
|
||||
|
||||
|
||||
Windows Update for Business reports only provides data for the standard desktop Windows client version and isn't currently compatible with Windows Server, Surface Hub, IoT, or other versions.
|
||||
|
||||
|
||||
@ -11,10 +11,10 @@ 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: 01/13/2022
|
||||
ms.date: 04/22/2024
|
||||
---
|
||||
|
||||
# Use Windows Update for Business and WSUS together
|
||||
# Use Windows Update for Business and WSUS together
|
||||
|
||||
> **Looking for consumer information?** See [Windows Update: FAQ](https://support.microsoft.com/help/12373/windows-update-faq)
|
||||
|
||||
@ -69,7 +69,8 @@ The policy can be configured using the following two methods:
|
||||
|
||||
> [!NOTE]
|
||||
> - You should configure **all** of these policies if you are using CSPs.
|
||||
> - Editing the registry to change the behavior of update policies isn't recommended. Use Group Policy or the Configuration Service Provider (CSP) policy instead of directly writing to the registry. However, if you choose to edit the registry, ensure you've configured the `UseUpdateClassPolicySource` registry key too, or the scan source won't be altered.
|
||||
> - Editing the registry to change the behavior of update policies isn't recommended. Use Group Policy or the Configuration Service Provider (CSP) policy instead of directly writing to the registry. However, if you choose to edit the registry, ensure you've configured the `UseUpdateClassPolicySource` registry key too, or the scan source won't be altered.
|
||||
> - If you're also using the **Specify settings for optional component installation and component repair** policy to enable content for FoDs and language packs, see [How to make Features on Demand and language packs available when you're using WSUS or Configuration Manager](fod-and-lang-packs.md) to verify your policy configuration.
|
||||
|
||||
- [Update/SetPolicyDrivenUpdateSourceForDriverUpdates](/windows/client-management/mdm/policy-csp-update#update-setpolicydrivenupdatesourcefordriver)
|
||||
- [Update/SetPolicyDrivenUpdateSourceForFeatureUpdates](/windows/client-management/mdm/policy-csp-update#update-setpolicydrivenupdatesourceforfeature)
|
||||
|
||||
Reference in New Issue
Block a user