SCCM administrators set maintenance windows for devices. Users set business hours for the same devices. It seems inevitable that maintenance windows and business hours will overlap. During that overlap, will SCCM perform the operations that support maintenance windows?
This technet blog post is the best resource I have found for understanding maintenance windows and business hours. It is, however, silent on the matter of overlap between the two.
From my understanding; (fairly new to SCCM 2012, been working with SCE 2010 for a while though) the elements in play here:
The Business Scenario
Let's say you are trying to deploy "Java 8 Update xx" to end user machines in a single device collection. Why? Because Java.
The two in question:
Business Hours: This is a rotating weekly calendar which the end user is allowed to configure. I.E. end-user Mary wants all software updates and installations to occur when she leaves the office at 5:00 PM on the days she works Monday through Friday.
She will go into the Software Center console and set her Business Hours like...
We will call this $BizWindow, it will evaluate to TRUE during the hours specified and FALSE when outside of the set time frame.
Maintenance Windows: This can be a Monthly, Weekly, or Daily schedule where the administrator is allowed to set a range of hours when an installation will be available to computers. These settings are configured at the Device Collection level.
We will call this $MaintWindow, it will evaluate to TRUE when it is 4:00 PM - 8:00 PM every single day.
Necessary Conditions:
So for the software to begin installing on the client device, the computer needs to meet two conditions:
1.) It is not in the Business Hours
2.) It is in the Maintenance Window
I.E.
So for the above example
Mary's computer will install Java during:
Honorable Mentions
When publishing Apps and Packages, there is a way to supersede any sort of Maintenance Window and Business Hours rules in the deployment settings. Then the software will become available/install immediately after it has been distributed to the respective DP's and the SCCM client updates the list.
Hope that helps.
Empirical Results
I just ran a few tests to see how SCCM behaves. The results are as follows:
Note: All of the above tests were run after the "available time" with the installation deadline set to "As soon as possible after the available time."
The rule seems be as follows: