The deployment for the SUG already ran and installed the patches, it won’t go and do a second run to install the 1 failed.
Software update evaluation cycle is what causes the patches to install, and that runs either: 1. Depending on what you set in client settings for schedule deployment evaluation. We have it set for once a day, we can’t set it more aggressive as we have lots of clients. 2. Making a 2nd mandatory deployment of the SUG that is set to run the WM. Having the MW open doesn’t cause 2nd run of the SUG to occur. Rob From: [email protected] [mailto:[email protected]] On Behalf Of Stephen Owen Sent: Wednesday, January 20, 2016 12:19 PM To: [email protected] Subject: Re: [mssms] RE: SCCM 1511 - SUG / MW question Well, unless you're removing the deployment, then the missing updates would still be required for that machine. So, that system you're targeting wouldsee that it has 9 out of 10 updates installed, and if in a Maintenance Window, should attempt to install the one missing required update again. Isn't that how it works today? On Wed, Jan 20, 2016 at 12:08 PM, Robert Spinelli <[email protected]<mailto:[email protected]>> wrote: Agreed. Just having to create a 2nd deployment during the MW to have it kick off a 2nd run is annoying. Thanks Rob From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Jason Sandys Sent: Wednesday, January 20, 2016 10:37 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: SCCM 1511 - SUG / MW question One quick note here (that doesn’t address your scenario): Simply adding a maintenance is useless. Maintenance Windows do *not* ever cause activity. Only required deployments do so that’s why you have to add a deployment. Maintenance windows only allow activity. J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Robert Spinelli Sent: Monday, January 18, 2016 11:01 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] SCCM 1511 - SUG / MW question I have always had a wish that if you have a SUG targeted to a machine with required deployment time in the past and MW opened up the SUG would run more than just 1 time. Is there any new functionality in 1511 that gives you this? The main reason I’ve always hoped for something like this is to attempt reinstall of failed patches in a SUG without needing to create another deployment during the opened MW. Example below: • 2016-01 SUG has 10 patches and deployment set as required 1/11/16 6:00AM to a collection with Server001 in it. • Server001 has MW set for 1/18/16 8AM – 11AM • 2016-01 SUG will run at 1/18/16 8AM on Server001, install 9 patches successfully and fail to install 1 patch. The only way I would be able to have that 1 failed patch attempt to install again is to have a 2nd required deployment set for 1/18/16 9:30 AM (within the 8AM – 11AM MW) for the 2016-01 SUG targeting collection with Server001 in it. If there was some way to say 2016-01 SUG deployment can run 3 times when the MW opens up on Server001 the 2nd deployment wouldn’t be needed. What I’ve seen is a lot of the patch failures can be resolved with another run (see this a lot with .Net Framework patches) of the SUG with a 2nd deployment during the open MW. If you’re patching monthly the next month when the MW opens up again the failed patch will attempt to install again and hopefully work, but then you’re not patched for a month for that patch. I’ve also tested setting multiple MW’s on a machine hoping the deployment would run again, (e.g. 8:00AM-9:59AM, 10:01AM – 11:00AM) but there is something to do with software updates deployment evaluation cycle that it won’t run the same deployment again if it ran within the last 24 hours. How do others handle this currently in SCCM 2012 R2 and does anything in 1511 help with this scenario? Thanks Rob
