Maintenance Schedule and Change Conflict

[DuaneNMore]

Newbie trying to understand the nuance of maintenance Schedules and Change Requests.

Version Helsinki

I have 2 maintenance Schedules:

Global Infrastructure

• Applies to:cmdb_ci
• Schedule: saturday 01:00:00 - 04:00:00 repeating weekly

IP Network

• TZ US\Pac
• Applies to cmdb_ci
• schedule:Monday 01:00:00-11:00:00 repeating weekly.
• (Initially I had an additional "Assignment group" is Network clause but removed it)

I have a Normal change request:

• Assignment group:Network
• CI: a network device
• Scheduled Date:2016-10-24 03:00:50 to 2016-10-24 04:00:06

When I check the conflict it returns

                              Not In Maintenance Window         Global Infrastructure

Now clearly the time for the Change scheduled date falls within the "IP Network". Is there some nuance on how conflict resolutions is working that I am not understanding? To make sure I wasn't failing to understand Timezones I updated the "IP Network" scheduled to be 00:00:00-23:59:59 repeating daily; but I still get the conflict.

[Michael Fry1]

When you check for Conflicts, it checks against all possibly windows. In your example, it says 'Global Infrastructure' is the one outside of the window, which it is. You can use conditions to limit schedules to a class or several classes.

[DuaneNMore]

So it works exactly opposite to how I would have expected. What you are saying is that it checks all possible scheduled windows, its default behavior is to look for a conflict rather than to look for a match.

With a complex IT with a diverse support structure it will become difficult to craft the windows in the fashion that you have noted. I would be unsurprised if we ended up with one that just repeats everyday from 000000 to 235959 so that we can get around this and move forward.

One example is, we have 4 production maintenance windows under which we patch windows servers during patch week. the only difference between any of these servers is the window they are in. They all reside in the same IP Address space, share common Assignment groups etc. The only real difference is   they have preventative maintenance and patching performed during window Prod-A, Prod-B, Prod-C, Prod-D; as selected by the various data center subscribing customers.

I was hoping device groups might help, but that doesn't appear to be a criteria in the selection.