deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-15 18:33:43 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Updates to improve clarity and address questions/feedback

Browse Source 
The currently live text isn't fully accurate and has raised a number of questions from customers, support, and the field.  This more verbose proposal attempts to improve accuracy while addressing questions that have been raised.
This commit is contained in:
Terry Dolan
2019-09-17 15:45:57 -07:00
committed by GitHub
parent fa7de5f7a0
commit c1ebe010c6
1 changed files with 10 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
windows/deployment/update/fod-and-lang-packs.md
View File

@ -6,7 +6,8 @@ ms.mktglfcycl: manage
ms.sitesec: library
ms.pagetype: article
ms.author: greglin
audience: itpro
audience: itpro
author: greg-lindsay
ms.localizationpriority: medium
ms.date: 03/13/2019
ms.reviewer:
@ -17,10 +18,14 @@ ms.topic: article
> Applies to: Windows 10
As of Windows 10 version 1709, you cannot use Windows Server Update Services (WSUS) to host [Features on Demand](https://docs.microsoft.com/windows-hardware/manufacture/desktop/features-on-demand-v2--capabilities) (FOD) and language packs for Windows 10 clients locally. Instead, you can enforce a Group Policy setting that tells the clients to pull them directly from Windows Update. You can also host FOD and language packs on a network share, but starting with Windows 10 version 1809, FOD and language packs can only be installed from Windows Update.
As of Windows 10 version 1709, you cannot use Windows Server Update Services (WSUS) to host [Features on Demand](https://docs.microsoft.com/windows-hardware/manufacture/desktop/features-on-demand-v2--capabilities) (FOD) locally. Starting with Windows 10 version 1803, language packs can no longer be hosted on WSUS.
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 Feature on Demand packages, language packages, as well as where to source content for corruption repair. However, it’s important to note this policy only allows specifying one alternate location and will behave differently based on OS version.
In Windows 10 version 1709 and 1803, changing the **Specify settings for optional component installation and component repair** policy to download content from Windows Update will enable acquisition of Feature on Demand packages while also enabling corruption repair. Specifying a network location will work for either, depending on the content is found at that location. Changing this policy on these OS versions will not influence how language packs are acquired.
In Windows 10 version 1809 and beyond, changing the **Specify settings for optional component installation and component repair** policy will also influence 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 will work for either Feature on Demand packages or corruption repair, depending on the content stored at that location.
For all OS versions, changing the **Specify settings for optional component installation and component repair** policy will not affect how OS updates are distributed. They will continue to come from WSUS or SCCM 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](https://docs.microsoft.com/windows/client-management/).