How to make Features on Demand and language packs available when you’re using WSUS/SCCM

As of Windows 10 version 1709, you cannot use Windows Server Update Services (WSUS) to host Features on Demand (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.

For Windows domain environments running WSUS or SCCM, change the Specify settings for optional component installation and component repair policy to enable downloading FOD and language packs from Windows Update. This setting is located in Computer Configuration\Policies\Administrative Templates\System in the Group Policy Editor.

Changing this policy does not affect how other updates are distributed. They continue to come from WSUS or SCCM as you have scheduled them.

Learn about other client management options, including using Group Policy and administrative templates, in Manage clients in Windows 10.

Information reference from https://docs.microsoft.com/en-us/windows/deployment/update/fod-and-lang-packs

Convert install.esd to install.wim

I haven’t put up new post for quite some time, this is definitely worth keeping it.

Recently I started to look at creating a system image for Winodws 10, it will be used for the desktop/laptop deployment.  It is not funny that you have to do so much to get it to work when you don’t have SCCM in your environment.

One thing that was blocking my way, there is no more install.wim for creating the package, the latest build of Windows 10 download only comes with install.esd under the source directory.  Although you can ask Uncle Google, and there will be many software options to convert, extract, decrypt…etc many many terms, but I don’t like any of them as I don’t feel comfortable downloading a script or software that wasn’t verified, you just don’t know what it’s embedded.

I am luckily enough to find these information from a Technet article.

  1. you need to copy the install.esd file onto a local storage location.
  2. run cmd in elevated mode.
  3. execute this command – dism /Get-WimInfo /WimFile:install.esd (this should pointing to the physical path)
  4. note down the Index number for the operating system you would like to deploy
  5. then execute this command – dism /export-image /SourceImageFile:install.esd /SourceIndex:1 /DestinationImageFile:install.wim /Compress:max /CheckIntegrity
  6. if it ran ok, you will get install.wim extract in the same folder.  now you can use this to work with MDT.

Have fun!