Not 100% on this, but from my experience:
When you schedule an update to a system that has a maintenance window assigned to it, the system will receive the policy, determine if it is inside the maint window or not… if it is not, it will wait until the maintenance window opens before it attempts the scan/eval/install. If it fails, it’s not going to retry until the next scan and eval schedule. That schedule is NOT based on the last time it scanned – it’s based on the first time it scanned once it received the client policy to enable software updates and it performed its first scan. In other words, by it scanning during the maintenance window – that’s not based on the schedule, that’s based on the deployment policy being received prior to a maintenance window being open. This is all based on “simple schedule” for software updates scanning. I believe you can set a defined date/time schedule, too. From: [email protected] [mailto:[email protected]] On Behalf Of Robert Spinelli Sent: Friday, January 23, 2015 11:06 AM To: [email protected] Subject: [mssms] Retry of failed patches - SCCM 2012 I'm pretty sure I got this right, just wanted to get some clarification. Machine with maint windows of 9AM-9PM every Saturday (ex: 1/24) I deploy SUG on Friday (ex: 1/23) night that has 2 patches in it to a collection with that machine in it. Deployment runs on machine at 9AM on 1/24 Installs 1 patch successfully but fails on 1 patch Machine reboots The failed patch won't try to re-install until the Software Updates \ Schedule deployment re-evaluation cycle runs again which by default is set to every 7 days. If we have it set to once a day if and the re-eval kicks off Sunday (1/25) at 9AM since its outside the maintenance window the failed patch won't attempt to reinstall until the maintenance window opens back up on 1/30at 9AM. Do I have that right? Thanks
