cmb Posted October 13, 2015 Report post Posted October 13, 2015 I am dealing with a couple of different challenges at my organization and I could use a little help. Description of Issue: A client is assigned a 2 hour maintenance window. Patches are deployed to the client. The client hits its maintenance window and spends 20 minutes installing patches. One or more of those patches require a reboot so SCCM reboots the client. At this point, I've encountered two different scenarios that I need to be able to explain. 1) A patch requires a second reboot to complete its installation. Despite there being 1.5 hours left in the MW, SCCM does not initiate a second reboot. 2) A patch that was installed actually creates the need for a follow up patch. That follow up patch was included in the same deployment as the original patch. Despite there being 1.5 hours left in the maintenance window, SCCM does not detect the need for the second patch, install it and reboot. I have the unfortunate task of having to explain why to our management team. I have read through the following resources and I believe I have a solid understanding of the various underlying components at work in the Software Update process. However, I feel like I've yet to locate the "smoking gun". I have read through the following: -The free ebook from Microsoft press called "Microsoft System Center Software Update Management Field Experience" -http://blog.configmgrftw.com/notes-software-update-scan-cycle/ -https://technet.microsoft.com/en-us/library/gg682168.aspx My gut tells me it has something to do with the various polling cycles at work for all the various components that are involved in getting scan state from the client back to the site server, which can then update policy, which can then direct the client on what to do next. I need to be able to substantiate that though. Any help is greatly appreciated. Quote Share this post Link to post Share on other sites More sharing options...
GarthMJ Posted October 14, 2015 Report post Posted October 14, 2015 First off a 2 hour MW, IMO is to small, I recommend nothing less than 4 hours. Secondly the only way a follow-up SU will apply is in there is another deployment during that MW, otherwise that is the expected. Even then it is rare to an a follow up SU during a particular monthly SU cycle. So yes in a nutshell you gut is right. if you need "proof" then you will need to get your TAM to provide it. Quote Share this post Link to post Share on other sites More sharing options...