Partager via

Adding .NET Framework to Windows 10 using MDT 2013 Update 1

  • Article

If you didn’t read through my last post at https://blogs.technet.com/b/mniehaus/archive/2015/09/01/adding-features-including-net-3-5-to-windows-10.aspx, read through that for some background. 

At the bottom of that post is a discussion about adding these “Features on Demand v2” packages to Windows using the DISM /Add-Package command. 

But if you are using MDT 2013 Update 1, there is an even easier approach:  Import the CAB files that you want to add into your deployment share using Workbench, and then MDT will inject them automatically, offline before the OS boots for the first time.  Here’s a sample deployment share that I’ve been using:

image

That includes the latest (well, latest at the time) Windows 10 cumulative update package, as well as the .NET 3.5 “OnDemandPack” package, in both x86 and x64 flavors.  These will be automatically installed as part of the Windows 10 task sequences.

You can do the same thing with MDT integrated into ConfigMgr using the MDT-provided “Install Updates Offline” feature.  To use that, you would need to create a ConfigMgr package containing the .NET CAB files (one per folder), then point the “Install Updates Offline” step (which you need to add manually to the task sequence sometime before the TS boots into the new OS) to that package.

That’s much easier than the Windows 8/8.1 mechanism, as you don’t need to worry about the “\sources\sxs” folder, very long file paths, etc.

Comments

  • Anonymous
    September 02, 2015
    Do you need to add a task sequence step in MDT2013U1 and point it at the package? or does it just install everything in the "Packages" folder you add to it?
  • Anonymous
    September 02, 2015
    The default task sequence already takes care of it, selecting all the packages that match the OS version and architecture.
  • Anonymous
    September 03, 2015
    That's awesome! :) cheers!
  • Anonymous
    September 08, 2015
    I have found using this method, in conjunction with editing the features of the foundation package in WSIM, results in two servicing sections being present in the unattend.xml and the foundation package not being configured during setup. I went back to inserting the OnDemand packages in WSIM with the long paths to get all the packages installed and configured.
  • Anonymous
    September 08, 2015
    The multiple servicing section issue is a bug in MDT 2013 Update 1 that will be fixed in a re-release of MDT, due in the next couple of weeks.