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
31 comments
-
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.
-
Anonymous
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.
-
Sriram
commented
Indeed MS should enhance SCCM capability for sug to detect a pre-requisite, before patches in sug get applied on device
-
Sai Kurapati
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.
-
Paul
commented
This is proving almost unmanageable.
We also work in healthcare, our Servers have 2 hours maintenance windows which is well enough to install updates but when the SSU installs the process then completes, no reboot and the CU which has been saved to the ccmcache folder just sits uninstalled. So next month comes around and same thing can happen again with the next SSU and no CU.Very very poor MS, can you please coordinate the ConfigMgr and WinUpdate teams to work together on a solution.We have had many times in the past where there are clashes between CM and WU and neither team claim responsibility, please MS these are your products! Remember we have choices as to patching mechanisms, Operating Systems and these situations are not in your favour!
-
CBraun
commented
No SSU this month? Does that mean it has been built into the monthly CU? This is a good sign for patching in the days ahead.
-
Anonymous
commented
Same problem when offline-servicing an OS image.
-
Meister-T
commented
Planned. Great. How its going on. Any status updates or feedback?
-
Jesper Hassing
commented
Planned! Yay!
-
Andrew
commented
This patching process is making my job miserable. Working in healthcare, I have a very small window to deploy patches. Finding out that patches didn't apply in time, or the CU's weren't even detected because the SSU wasn't updated is causing us to miss our patching window, which means more coordinated downtime with the units. Please find a better way to handle these updates.
-
Ken
commented
The service stack is a wall between old and new updates.
Old update are still valid until the time the service stack is installed.
Then No Updates are viable.
After the service stack is install and scan run only then can the new updates viable.Can the cumulative update monthly install equal to the service stack month not be made viable for both pre and post cumulative update?
Then both order and scans become irrelevant.
Its detection and install will work before the service stack or after the service stack. -
Pieter Pessemier
commented
My 2 cents:
Just having an option to automatically run an SU Scan Cycle and SU Deployment Evaluation Cycle right after successful or unsuccessful installation of the triggered updates, regardless of a reboot requirement, would fix this. We basically just want everything patched within our defined maintenance window regardless of the amount of reboots or prerequisites.
-
Bryan Dam
commented
@Charles: You're not wrong but keep in mind that options 2-4 are out of the ConfigMgr team's hands. So the only thing in their control is #1 which I've been told they are looking into.
I can't find this stated anywhere but I heard from the product team that the new Unified Update Platform will implement #2: Make the SSU and CU on patch. But that's not going to help for a long time.
It's worth noting that the behavior indicated by the actual UVI (install SSU before CU if both appear) would be great from a steady-state perspective. This month we're just all a tizzy because MS made them pre-reqs again which hasn't been the norm. So we really need both.
