"Available" effectively means that the deployment must be initiated by the user. So, that's what the available time sets: When a user can initiate the enforcement of a deployment. Required means that the ConfigMgr agent will initiate the deployment. So, that's what the deadline sets: When the agent will enforce a deployment.
No deadline = no automatic agent enforcement. Also, only required deployments are constrained by maintenance windows. Anything user initiated ignores maintenance windows including the user scheduling a deployment outside of their business hours (but don't mix the two up, business hours only apply to a user scheduling a deployment and have no power or deadlines on required deployments). This goes for *all* deployment types. J From: [email protected] [mailto:[email protected]] On Behalf Of Orlebeck, Geoffrey Sent: Tuesday, December 9, 2014 4:56 PM To: '[email protected]' Subject: [mssms] RE: Software Updates & Maintenance Windows: Understood. I was previously assuming deadlines were the point that *forced* the install, but if you made a deployment available, the next maintenance window it would try to install (until the deadline, then it would do it forcibly). That was my assumption because you can make the software "available" but then set a deadline a week later. That was just looking at it at face value, but once I started pushing it out to test clients and seeing the behavior I figured either my assumption as wrong or I misconfigured something. I had more of a WSUS mindset, where you can set a deadline, but if a GOP says to install updates each night, then once an update is approved it will attempt to install unless it can't, then at deadline it will do it forcefully. Though perhaps that's more like having nightly deadlines for any available updates. Regardless, as long as that is the expected behavior, I can now plan our patching and cycles based off the deadlines and maintenance windows. Thanks, Geoff From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Tuesday, December 09, 2014 2:03 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Software Updates & Maintenance Windows: As an additional note here, deadlines are not "lines in the sand", they are absolute lines in concrete. A ConfigMgr client agent will not enforce a deployment until that deployment has reached its deadline (or the user initiates the deployment). J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Orlebeck, Geoffrey Sent: Tuesday, December 9, 2014 11:39 AM To: '[email protected]' Subject: [mssms] RE: Software Updates & Maintenance Windows: Great, thank you for getting back to me! -Geoff From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Gerry Hampson Sent: Tuesday, December 09, 2014 9:33 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Software Updates & Maintenance Windows: Geoff, the updates will install during the first maintenance windows AFTER the deadline is reached. Regards, Gerry From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Orlebeck, Geoffrey Sent: 09 December 2014 17:24 To: '[email protected]' Subject: [mssms] Software Updates & Maintenance Windows: Hello group. I've been working a bit more with SCCM (2012 R2, single primary site) and I have a question surrounding how maintenance windows and deadlines work. I just want to confirmation as I haven't seen this addressed specifically anywhere that I've looked, including TechNet. If I create a Software Update Group today (12/9) and deploy it with a deadline for 12/13 @ 2AM to a collection with a Software Updates maintenance window daily from 11PM-5AM, the updates still won't actually install until the deadline is hit, correct? That is the behavior I am currently seeing in my environment. Even though the devices may download the updates today, and there are maintenance windows that occur nightly from now until 12/13, the updates don't actually install until the deadline is reached. Is that correct? My assumption (I know...assumptions) was the deadline was a line in the sand, but if a maintenance window passes before the deadline and there are pending deployments, those would process. Since this is my first go with ConfigMgr, I just want to confirm the above behavior is by design and that I haven't misconfigured something. Happy to provide any additional details if needed. Thanks! -Geoff Confidentiality Notice: This is a transmission from Community Hospital of the Monterey Peninsula. This message and any attached documents may be confidential and contain information protected by state and federal medical privacy statutes. They are intended only for the use of the addressee. If you are not the intended recipient, any disclosure, copying, or distribution of this information is strictly prohibited. If you received this transmission in error, please accept our apologies and notify the sender. Thank you. Confidentiality Notice: This is a transmission from Community Hospital of the Monterey Peninsula. This message and any attached documents may be confidential and contain information protected by state and federal medical privacy statutes. They are intended only for the use of the addressee. If you are not the intended recipient, any disclosure, copying, or distribution of this information is strictly prohibited. If you received this transmission in error, please accept our apologies and notify the sender. Thank you. Confidentiality Notice: This is a transmission from Community Hospital of the Monterey Peninsula. This message and any attached documents may be confidential and contain information protected by state and federal medical privacy statutes. They are intended only for the use of the addressee. If you are not the intended recipient, any disclosure, copying, or distribution of this information is strictly prohibited. If you received this transmission in error, please accept our apologies and notify the sender. Thank you.
