Is it ok to place servicing stack and cumulative updates in the same Software Update Groups?

Copper Contributor


Microsoft recommends to install the latest servicing stack updates for your operating system before installing the latest cumulative update.  If I'm creating a Software Update Group in Configuration Manager is to ok to place servicing stack and cumulative updates in the same update group? Does ConfigMgr have logic to install them in the correct order? 

6 Replies

If you create an ADR you'll see that the SSU will be added automatically to the SUG.

It is recommended but not required to install SSU before the cumulative update.

best response confirmed by Hogan_Klink (Copper Contributor)

Unlike Microsoft Update, ConfigMgr does not have built-in logic to install the servicing stack update before the latest cumulative update. One way to get around this is by using the technique outlined in @Mike Terrill's blog post here.


You may also want to vote on this UserVoice suggestion.



Thank you. This is certainly less then an optimal solution. I sure hope the ConfigMgr team creates a better solution.

@Hogan_Klink ConfigMgr 2002 release fixes this problem:

Evaluate software updates after a servicing stack update

Configuration Manager now detects if a servicing stack update (SSU) is part of an installation for multiple updates. When an SSU is detected, it's installed first. After install of the SSU, a software update evaluation cycle runs to install the remaining updates. This change allows a dependent cumulative update to be installed after the servicing stack update. The device doesn't need to restart between installs, and you don't need to create an additional maintenance window. SSUs are installed first only for non-user initiated installs. For instance, if a user initiates an installation for multiple updates from Software Center, the SSU might not be installed first.

For more information, see Plan for software updates.

@josugo This is the only correct answer. @Hogan_Klink you should consider updating to version 2002 if you haven't done so already!