Keeping SCCM builds aligned with Windows 10 builds

[sparkeh]

Having just gone through the process of updating SCCM for (and deploying) Window 10 v1703 I thought that I would share what I did and what I learned in case it helps anyone.

 

 

• SCCM will now be updated along with the release of new Windows 10 builds. This means that you will also need to update to the ADK released with the new Win 10 build and possibly MDT (though this won't be updated for every build, just as needed). Although its not strictly necessary to have everything aligned like this, it is recommended. There is however a handy chart of supported configurations here
  
• 
  
• You can find the latest ADK here: https://developer.microsoft.com/en-us/windows/hardware/windows-assessment-deployment-kit
  
• Update ADK first! When you update SCCM it will generate new boot disks. If you have already updated ADK then you will get updated boot disks based on the new ADK. If you don't then you get boot disks based on the old ADK. You can check if you have the latest boot disks by comparing the version of the boot disks in SCCM to the version of ADK in add/remove programs:
  
• 
  
• If you do update SCCM first you can regenerate the boot disks to be based on the update ADK with this handy script: https://gallery.technet.microsoft.com/RegenerateBootImageWinPE10-f508f1e4
  
• After this you can update SCCM from the console
  
• Next check if there is an update to MDT here: https://technet.microsoft.com/en-us/windows/dn475741.aspx?f=255&MSPPError=-2147217396
  
  • If there is an update to MDT then install it and remember to integrate it into SCCM again. Also remember to create a new MDT tookit and setting package and a new USMT package (easiest way is to create an MDT TS and let it create the package)
    

   

  [*]Now you can download your chosen Win 10 build from MSVLC. At this point I use @Arthur's script to strip out the unwanted Modern Apps from the install.wim and then import into SCCM. Slight gotcha here as I learned that when you update ADK you get a new version of DISM, but its installed side-by-side with any existing versions allowing you to swap between them. You can use import-module to use the version you want.

  [*]You also need to update any language packs that you are deploying, these are also available from MSVLC.

 

After this you should be go to go and update your deployment TS to reflect the new source, boot disks, MDT packages, lang packs etc.

Edited August 15, 2017 by sparkeh
Typo