Hey Guys,

I'm having a little issue with maintenance windows for software updates only. For testing purposes, I've set a maintenace window from 7am to 10am, with a deadline of 11:30am on the same day. The package was staged and targeted for deployment at 10:30pm the day before, and made available at 11:30pm.

I have also manually forced a client policy update + software update eval on the client machine to speed things up. And I do see a notification, and there are 47 items that need to be installed, and the source files are present in the ccmcache. However, the client refuses to do anything during the maintenance window.

I have read the blog on windows maintenance windows/business hours/deadline, and everything makes sense. Am I right to say the maintenance hours override business hours? I have also checked UpdatesDeployment.log on the client, and I see "No current windows available to run updates assignment with time required = 1". What does this actually mean?

We're on SCCM 2012 R2. Any response will be greatly appreciated. Thanks

• Edited by gdpt 13 hours 51 minutes ago Add

Maintenance Windows and Business hours are two totally different things.

MWs constrain the time a deployment is executed after the deadline has passed. MWs have no effect on deployments whose deadlines have not yet passed.

BHs enable a user to allow automatic execution of a deployment before a deadline has occurred. Once a deadline has occurred, BHs are useless.

Thus, based on your above times, the deadline hadn't past when the client entered the MW so nothing should happen during the MW but once the deadline is reached, the client is outside the MW so can't execute anything until the next MW.

Thanks Jason. That makes perfect sense now.