Business hours are completely unrelated to maintenance windows: http://blogs.technet.com/b/server-cloud/archive/2012/03/28/business-hours-vs-maintenance-windows-with-system-center-2012-configuration-manager.aspx
Business hours allow users to schedule deployments at convenient times for them but cannot/do not over rode deadlines in any way. If a deployment has a deadline, then business hours simply allow users to schedule it’s execution *before* the deadline; once the deadline hits, users have zero control over the deployment short of turning off their system (or worse if they’re a local admin but that’s a whole different topic). J From: Daniel Corkill Sent: Monday, June 17, 2013 5:13 AM To: [email protected] Hi all, As I play around with CM12 I’m trying to figure out how I’m going to make this new business hours feature fit for our existing software distributions and software update deployments. Oddly (at least to me) you can’t seem to centrally manage the business hours in terms of specifying the hours or disabling it altogether. Personally I’d like to just disable as it seems like it’s going to be a headache and something that will necessitate us modifying our deployment behaviour. As an example, our existing software update deployments have a deadline of Tuesday at 2pm. Users are aware that this happens and they’re aware that the reboot is suppressed and they’re expected to reboot/shutdown at the end of the day. How am I supposed to make this work now with business hours? Am I going to have to make the deployments ignore maintenance windows? And how do business hours work on servers? Just would like to hear from others on their business hours strategy I guess… Daniel.
