Business hours and maintenance windows are two completely different things.
MWs restrict when things can run and can only be set on the ConfigMgr server side. MWs also only come into play after a deadline is reached when a deployment thus becomes mandatory. BHs cause things to run automatically before a deadline is reached based on a user's preference. They in no way restrict when deployments are executed and once a deadline is reached, BH's are not considered at all. There's a great blog post from the product Team (Dave Randall specifically) on this that goes into more details: http://blogs.technet.com/b/server-cloud/archive/2012/03/28/business-hours-vs-maintenance-windows-with-system-center-2012-configuration-manager.aspx J ________________________________ From: [email protected] <[email protected]> on behalf of s kissel <[email protected]> Sent: Wednesday, February 5, 2014 10:26 AM To: [email protected] Subject: [mssms] Business Hours and MWs as related to patching servers Environment is SCCM 2012 R2. Client has a couple thousand servers spread out through various patch collections having a maintenance window for each collection, but the maintenance window is different from collection to collection. Furthermore, the server owners are able to move their servers from one MW collection to another using a web interface, but that shouldn't be overly related. Knowing how MWs work and that they work the same as in CM07, what's to stop a server owner from entering the Software Center and setting their business hours From 12:00 AM through 12:00 AM for all days, AND checking the box "Automatically install or uninstall required software and restart the computer only outside of the specified business hours? Would that mean that the server would never get patched. Is this an accurate assumption, or am I missing something? I realize there are powershell and vb scripts that can set the business hours, but am curious how others are patching servers and dealing with the business hours. Thanks, -S
