I'm configuring maintenance windows in my environment and have experienced some strange behavior on one occasion. I'll give details of my implementation if needed, but my question may not require them.

If I set up a maintenance window, say for Saturday, set the Start to 8:00:00 AM, and set the End to be 12:00:00 AM, does SCCM understand how to handle that? The window duration appears to calculate correctly (showing 16 hours), but technically Saturday at 12 AM comes before 8 AM, and I thought it might cause some unexpected behavior in the background. 

In my particular case I saw a window duration in the Maintenance log that was longer than I anticipated. I'm working with multiple windows and had changed settings a couple times, so I'm not sure if it was just an unintended side effect, but I thought I'd throw this question out just in case.

Thanks!

can you explain a little more.  What is the unexpected behavior that you are seeing?   what times did the log file say that it ran to?

Spanning midnight with MWs is known to not work properly particularly if you are using UTC. I think it will work properly if you create two adjacent MWs however I think the current guidance is to not use UTC with MWs at all.

I had a deployment install a couple hours earlier than expected, based on my maintenance windows. If I remember correctly, one of the logs said I had a full 24 hour maintenance window, but I can't be sure right now.

I'll dig out those logs again so I can give specific details and a clearer snapshot of my setup. Thanks for the look, I'll get them up tomorrow (later today).

Do you have any site references for that? I did a quick search before I posted and didn't see anything (far from an exhaustive look though). I know I'm not using UTC time in my windows, and I was using two adjacent windows; one on Saturday from 8am-12am(midnight) and one on Sunday from 12am(morning) to 6pm. The unexpected installation was a task sequence and it started at 6am Saturday, which is 2 hours either direction from a maintenance window.

• Edited by EndlesslyHungry Wednesday, January 21, 2015 7:31 AM

I'm sorry I wasn't able to get logs on here as I intended, today was insanely busy. When I finally sat down to do it, I decided to research more first. I ran PolicySpy on one of the machines and found information about the maintenance windows, but it had these hex values for the schedule and that sent me down another rabbit hole. I found a post of yours, Jason, here

https://social.technet.microsoft.com/Forums/en-US/0915168c-94d7-4569-8653-bf975f3989a3/converting-schedule-token-from-ccmservicewindow?forum=configmanagergeneral 

and from there have been writing a PS script that takes the schedule hex value and converts it into readable data. I've finished the first half of the token (start time) and hope to get to the other half (recurrence) tomorrow. Then I can look at my ServiceWindowManager logs again and see if my questions answer themselves. I should have done this before I posted initially and apologize. 

There aren't any references for that -- its just based on internal reports. Doesn't sound like your issue although its difficult to tell. Please update the thread with your follow-on findings.

Hi,

Any update?

Best Regards,

Joyce

We got hit with some large, unexpected deadlines and I've had to put this to the side for a bit. Is there an etiquette for putting the thread on hold somehow?