Install Servicing Stack Updates Before Other Updates
Currently, when servicing stack updates and regular updates are deployed in the same software update group, the patches do not apply in a determinant order. This leads to cases where a cumulative update that requires a new servicing stack is installed before the servicing stack itself.
While this can be worked around by separately deploying the servicing stack update before updates that require said servicing stack, it would be much more convenient if the update installation process checked if there are any servicing stack updates to be deployed and automatically installed them first
Jesse Schauer
shared this idea
Check it out in 2002 Technical Preview https://docs.microsoft.com/en-us/configmgr/core/get-started/2020/technical-preview-2002#bkmk_ssu
43 comments
-
Mihai Canguru
commented
Ola
-
Sebastian Savard
commented
Will this update impact clients that have the configmgr client installed but receive updates through vanilla WSUS and GPO settings, or will we need to use ADR?
-
Per Bengtsson
commented
@Harvey & @Anonymous, Even if it was possible to install the SSU before everything else in the CU, how do you then make sure that the CU is installed before all other updates?
You're are just suggesting that they move the problem to the CU instead of the SSU. -
Bryan Dam
commented
@Anonymous: Because the SSU updates the thing that applies the CU.
In the forthcoming, long promised, Universal Update Platform they've designed around this problem but we're not there quite yet.
-
Anonymous
commented
If Service Stack is required, why don't they just build them into the CU releases...
-
Jimmy
commented
Any update?
-
AG
commented
An Admin of a large ConfigMgr evironment here, I totally agree the installation process should have the fuzzy logic to install servicing stack first.
This has been a PIA lately for us. Now to convince our change management team of this new workflow. Upside is these don't require a reboot thankfully -
Harvey
commented
If Service Stack is required, why don't they just build them into the CU releases...
-
Kristoff Braddy
commented
+1 #SSUCKS
-
Mike Bourne
commented
+1 as well, may have to consider the ADR solution
-
SCCMGuy89
commented
+1
-
Richie
commented
Any update on this? We are having issues getting November '19 SSUs and CUs installed properly via ConfigMgr.
-
John Williamson commented
This needs to be implemented sooner rather than later. Its documented that if a service stack update is installed with other updates, it can cause a system to hang after the reboot.
-
Arindam Chatterjee
commented
A much needed feature. Kindly look into it on priority.
-
Anonymous
commented
Planned since June - can we get an update? Thanks!!
-
Anonymous
commented
This really needs to get addressed ASAP.
-
Anonymous
commented
The SSU’s never require a restart correct? Just create a separate ADR to install prior to your patch ADR and set to enforce install at deadline and suppress reboot. I would still do this off hours but the average user wouldn’t even know its going on in the background while they read reddit in the morning.
-
Monica Montes
commented
I agree with all the comments. For windows 2012 SSU and CU can be installed together, why newest OS don't work in same way? I have small maintenance windows for all my servers and there are servers that just reboot 1 time per year, I can't have cumulative updates pending/waiting for a reboot 12 months because just the SSU was intalled. These are MS products so, I hope we could have a solution soon.
-
Chris Miller
commented
I agree with all the comments in this thread. We need the ability to run software update evaluation after all updates are installed regardless of reboot.
-
Beth
commented
I agree with all the comments in this thread. We need the ability to run software update evaluation after all updates are installed regardless of reboot.
