I think I figured it out. As long as this checkbox is NOT checked, BH's are ignored.
[image: Inline image 1] On Tue, Feb 16, 2016 at 8:56 AM, CESAR.ABREG0 . <[email protected]> wrote: > Are you thinking busines hours? Two seperate things, MW trump service > windows. If you need to maintain certain windows schedule, you need to > setup you MW based on that. When deployment deadline comes it will install > during MW. BUs are more if the end user needs to start the deployment. > > On Tue, Feb 16, 2016, 5:20 AM David Jones <[email protected]> wrote: > >> sorry here is the rest of this. >> >> My problem is I have areas with much different and tighter maintenance >> window requirements. How do I get rid of these since they are created on >> the client and not on the server? >> >> >> >> On Tue, Feb 16, 2016 at 8:18 AM, David Jones <[email protected]> >> wrote: >> >>> This defaults to 5am to 10pm Monday thru Friday on a new install. Does >>> this translate into a default maintenance window of 10pm to 5am on a new >>> install? I ask because on Zander's Client Center, both old and new, they >>> show up as service windows. On the old Client Center they show up with a >>> creation date in 2009 ( We have the latest SCCM ). On the new Client Center >>> 2012 they show up green instead of Blue with an X in them. When I hover >>> over them in the Client Center I get a GUID. A search for that GUID in the >>> logs shows entries in the ServiceWindowManager.log >>> >>> Here is just one (Monday's) >>> [image: Inline image 1] >>> >> >> >> >
