ConfigMgr Current Branch – Software Update Delivery Video Tutorial


The release of Windows 10 brought with it a change in the way updates are released – updates are now cumulative.  Since the release of Windows 10 this same cumulative update approach has been adopted for the remainder of supported operating systems.  While this approach has significant advantages there still remains some confusion about what it all means. 

The video linked below was prepared by Steven Rachui, a Principal Premier Field Engineer focused on manageability technologies.  In this session, Steven talks through the changes, why the decision was made to move to a cumulative approach to updating, how this new model affects software updating, how the cumulative approach is applied similarly and differently between versions of supported operating systems and more.

Next in the series, Steven will discuss Windows Update for Business and its integration with Configuration Manager.

Posts in this Series


Comments (4)
  1. Hackmuss says:

    Excellent. Really useful – keep ’em coming!! Looking forward to the WUB one next – there is so much confusion still around on the dual scan issue that i hope will be addressed.

  2. Bryan Dam says:

    Steve, great video. Eagerly awaiting the rest of them.

    You mention that the cumulative updates for the legacy operating systems (Windows 7 and 8.1 specifically) are fully cumulative. Do you mean from October 2016 when they started or the latest release of that OS’s ISO? When Microsoft started this model the ISO was the stated goal and I’ve watched as they have superseded pre-October 2016 updates since then. Do you know for certain that they actually made it all the way there? If so, then that would reduce the build and capture update scenarios to simply installing the latest cumulative update.

    1. Steven Rachui says:

      Hi Bryan, I appreciate the comment. My comment about the legacy operating systems being cumulative was simply to indicate we have switched from the monthly individual update model to a cumulative approach. That started in October 2016. Software updates for legacy operating systems are not exactly the same as Windows 10, as discussed in the video, but similar. Further, we do expect that at some point all of the individual updates released prior to October 2016 and that remain relevant will make their way into the cumulative rollups. I know there are at least some of the legacy operating systems where we haven’t fully realized this reality yet.

  3. cojoe72 says:

    Did you all take into account at all that when Microsoft releases a bad patch we’re now forced to pull every patch for an entire month in order to remove the one bad one? You discuss companies picking and choosing which updates to deploy as if we randomly decide “yes” on this one and “no” on that one for no logical reason. The only time we pull an update from deployment in our environment is if it negatively impacts a production application that affects whether or not our users are up and running or sitting at their desks doing nothing. The Spectre/Meltdown updates are a perfect example. They completely crashed one of our core applications that keep our business up and running. Because of the Update Rollup method Microsoft has switched to we had to pull every security update for the month of January rather than being able to selectively pull the one update that is causing the issue.

Comments are closed.

Skip to main content