cmb

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.

Hello all. I am well versed in the Software Update functionality of SCCM but am just now getting into Task Sequences and could use some help. I am attempting to create a task sequence that performs the following: Check for pending reboot state If pending reboot state = true then restart computer After reboot, install deployed software updates Restart computer Perform scan cycle and determine compliance If non compliant, install software updates Restart Computer Repeat steps 5 through 7 again if necessary Complete I have been messing around with the Get-PendingReboot PowerShell script from the gallery: https://gallery.technet.microsoft.com/scriptcenter/Get-PendingReboot-Query-bdb79542 I'm a bit lost on how to take the results of a Run PowerShell Script task and use it as a condition to run a Restart Computer task. I also have no idea how I would execute a compliance scan and initiate a software update install of the computer if found to be non-compliant based on the software updates I've deployed to it. If it matters at all, I'm specifically focused on servers with strict maintenance windows. Our business is adverse to downtime so I need to attempt to configure SCCM to make the most of the small maintenance windows we have. Ideally our servers should come out of a maintenance window fully compliant and not in a pending reboot state. Any help provided is greatly appreciated.