The best way to get to know a new operating system is to start using it and expose yourself to all the cool new quirks and also figure out design flaws. I wouldn’t call “Feature on Demand” a flaw – it’s a great way to get the binaries when you need them – but depending on the design of your patch management this could cause problems for end users.
In Windows 8 and in Windows Server 2012, features like “.Net Framework 3.5” is a Feature on Demand. The metadata for Features on Demand are included in Windows 8 and in Windows Server 2012. However, the binaries and other files associated with the feature are not included. When you enable the feature, Windows tries to contact Windows Update to download the missing information to install the feature.
This works great if you connect directly to Windows Update – but if you are using Windows Intune, SCCM or WSUS you run in to problems and you won’t be able to download and install your desired feature(s).
There are three ways you could handle this:
- Set at Path of a shared folder.
- Set a Path of a WIM file.
- Select the Contact Windows Update directly to download repair content instead of Windows ServerUpdate Services (WSUS) check box.
In my opinion method 3 is the way to go for our company.
- Start the Local Group Policy Editor or Group Policy Management Console.
- Expand Computer Configuration, expand Administrative Templates, and then select System.
- Open the Specify settings for optional component installation and component repair Group Policy setting, and then select Enabled.
- Specify your Option.
- Run gpupdate /force on affected computer(s).
Read the full KB here.
IT Architect and Senior Consultant at Addlevel. An Infrastructure Expert and DevOps Engineer with engagements ranging from automation, loganalytics, security design and architecture.