Correct, that's why using MWs for end-user systems is not optimal unless you are also using WoL or Wake up timers (or some other method to wake up the systems during an available MW).
That's also why giving the users the ability to install before the deadline at their leisure is a very effective strategy as it avoids the use of MW altogether. Users, when given the ability to control their own destiny and contribute, will actually surprise you - treat them like babies and that's what they'll act like. For those that wish to ignore the communication from IT and the messages that ConfigMgr presents before the deadline should then be subject to the deadline and the reboot that follows (which by default is 90 minutes) after the update installation giving them plenty of time to finish up their work. J From: [email protected] [mailto:[email protected]] On Behalf Of Roland Janus Sent: Wednesday, February 5, 2014 1:27 PM To: [email protected] Subject: RE: [mssms] Business Hours and MWs as related to patching servers At the end of this article: Do nothing. If Melissa closes the dialog, or if she indicates she wants to be reminded later, Software Center does not schedule the installation. If this condition continues on until the deadline (in other words, the user has taken no action to schedule or install the software), the software will get to the deadline and check for a maintenance window. At that point, the deployment will wait until the available maintenance window before installing. So, the deployment will install at 8am on Saturday. What if the mw is always outside the times the client is switched on? It would never install, unless the option is set to ignore mw, right? Otherwise that basically means the deadline should always be when the client is switched on? But what if that user works at very odd times and never within a mw? Again, the only option is the mw override? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Mittwoch, 5. Februar 2014 19:28 To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Business Hours and MWs as related to patching servers 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]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> on behalf of s kissel <[email protected]<mailto:[email protected]>> Sent: Wednesday, February 5, 2014 10:26 AM To: [email protected]<mailto:[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
