Updates installing when MaintenanceWindow is deleted

Hi,

We are currently in a patching cycle for our server and are currently in the Test Phase. All the steps for the deployment are as per the previous cycles.  However this time round the servers started to update as per normal when the Maintenance Window and Stopped when the window closed.  As the window is not re-occurring and thus not needed, I decided to delete the Window, soon after this servers that were not fully compliant started installing and servers restarting.  I have re-applied the back-dated Maintenance Window and this has put a stop to updates and restarts occurring. 

From reviewing the collections that have Maintenance Windows set, non apply for the servers in question.

Can anyone please explain why this would occur? and possible fixes

Some Logs from ServiceWindowManager.log

With a Maintenance Window.....

OnIsServiceWindowAvailable called with: Runtime:300, Type:4 ServiceWindowManager 09/09/2015 08:13:54 2272 (0x08E0)
No Service Windows exist for this type. Will check if the program can run in the All Programs window... ServiceWindowManager 09/09/2015 08:13:54 2272 (0x08E0)
        Biggest Active Service Window for Type=1 not found ServiceWindowManager 09/09/2015 08:13:54 2272 (0x08E0)
Program cannot Run! Setting *canProgramRun to FALSE ServiceWindowManager 09/09/2015 08:13:54 2272 (0x08E0)
WillProgramRun called with: Runtime:300, Type:4 ServiceWindowManager 09/09/2015 08:13:54 2272 (0x08E0)
No Service Windows of this type exist. ServiceWindowManager 09/09/2015 08:13:54 2272 (0x08E0)
There does not exist an All Programs window for this duration or the all programs window is not used as fallback. The Program will not run. ServiceWindowManager 09/09/2015 08:13:54 2272 (0x08E0)
ServiceWindowManager 09/09/2015 08:13:54 2272 (0x08E0)

After Deleting Maintenance Window.....

CServiceWindowManager::OnPolicyChange- Policy __InstanceDeletionEvent notification received ServiceWindowManager 09/09/2015 08:16:08 692 (0x02B4)
Service Window Policy Deletion notification received. ServiceWindowManager 09/09/2015 08:16:08 692 (0x02B4)
CCM::ServiceWindowManager::CServiceWindowHandler::OnPolicyDeleted - A policy change has occurred. Policy has been deleted. ServiceWindowManager 09/09/2015 08:16:08 692 (0x02B4)
The service window being deleted is not active. Just Deleting... ServiceWindowManager 09/09/2015 08:16:08 692 (0x02B4)
    Sending Message SERVICEWINDOWEVENT:DELETE event ServiceWindowManager 09/09/2015 08:16:08 692 (0x02B4)
    Inactive Service Windows List has 8 windows ServiceWindowManager 09/09/2015 08:16:08 692 (0x02B4)
        Service Window with ID = 7cb56688-692f-4fae-b398-0e3ff4413adb having Starttime=01/01/2038 00:00:00 ServiceWindowManager 09/09/2015 08:16:08 692 (0x02B4)
            Duration is 0 days, 00 hours, 00 mins, 00 secs ServiceWindowManager 09/09/2015 08:16:08 692 (0x02B4)
        Service Window with ID = 90a5f436-364c-48c7-8dc7-c5014abcbea8 having Starttime=13/09/2015 00:00:00 ServiceWindowManager 09/09/2015 08:16:08 692 (0x02B4)
            Duration is 1 days, 05 hours, 00 mins, 00 secs ServiceWindowManager 09/09/2015 08:16:08 692 (0x02B4)
        Service Window with ID = 45dca355-3249-4845-b8aa-72d0e604548e having Starttime=09/09/2015 22:00:00 ServiceWindowManager 09/09/2015 08:16:08 692 (0x02B4)
            Duration is 0 days, 07 hours, 00 mins, 00 secs ServiceWindowManager 09/09/2015 08:16:08 692 (0x02B4)
        Service Window with ID = 87e4759c-2884-45e6-9261-c33ba53f596c having Starttime=10/09/2015 22:00:00 ServiceWindowManager 09/09/2015 08:16:08 692 (0x02B4)
            Duration is 0 days, 07 hours, 00 mins, 00 secs ServiceWindowManager 09/09/2015 08:16:08 692 (0x02B4)
        Service Window with ID = 36da6950-3d1e-4027-be0e-7b16a4daee7e having Starttime=11/09/2015 22:00:00 ServiceWindowManager 09/09/2015 08:16:08 692 (0x02B4)
            Duration is 0 days, 02 hours, 00 mins, 00 secs ServiceWindowManager 09/09/2015 08:16:08 692 (0x02B4)
        Service Window with ID = 028bfbc0-7120-4081-a268-0e664a92ac4a having Starttime=12/09/2015 00:00:00 ServiceWindowManager 09/09/2015 08:16:08 692 (0x02B4)
            Duration is 1 days, 00 hours, 00 mins, 00 secs ServiceWindowManager 09/09/2015 08:16:08 692 (0x02B4)
        Service Window with ID = ad27b0ca-8c74-43c7-8200-1f601880bd75 having Starttime=14/09/2015 22:00:00 ServiceWindowManager 09/09/2015 08:16:08 692 (0x02B4)
            Duration is 0 days, 07 hours, 00 mins, 00 secs ServiceWindowManager 09/09/2015 08:16:08 692 (0x02B4)
        Service Window with ID = 49fd80be-ac4b-4877-974d-ecd09958926d having Starttime=15/09/2015 22:00:00 ServiceWindowManager 09/09/2015 08:16:08 692 (0x02B4)
            Duration is 0 days, 07 hours, 00 mins, 00 secs ServiceWindowManager 09/09/2015 08:16:08 692 (0x02B4)
ServiceWindowManager 09/09/2015 08:16:08 692 (0x02B4)
    Active Service Windows List has 0 windows ServiceWindowManager 09/09/2015 08:16:08 692 (0x02B4)
ServiceWindowManager 09/09/2015 08:16:08 692 (0x02B4)
    Active schedule is accurate, no need to reschedule ServiceWindowManager 09/09/2015 08:16:08 692 (0x02B4)
ServiceWindowManager 09/09/2015 08:16:08 692 (0x02B4)
OnIsServiceWindowAvailable called with: Runtime:900, Type:2 ServiceWindowManager 09/09/2015 08:16:08 5980 (0x175C)
No Restricting Service Windows exist. It can therefore run... ServiceWindowManager 09/09/2015 08:16:08 5980 (0x175C)

Logs Suggesting Updates will install

OnIsServiceWindowAvailable called with: Runtime:900, Type:2 ServiceWindowManager 09/09/2015 08:16:08 5980 (0x175C)
No Restricting Service Windows exist. It can therefore run... ServiceWindowManager 09/09/2015 08:16:08 5980 (0x175C)
OnIsServiceWindowAvailable called with: Runtime:1, Type:4 ServiceWindowManager 09/09/2015 08:16:08 7152 (0x1BF0)
No Restricting Service Windows exist. It can therefore run... ServiceWindowManager 09/09/2015 08:16:08 7152 (0x1BF0)
OnIsServiceWindowAvailable called with: Runtime:1800, Type:4 ServiceWindowManager 09/09/2015 08:16:08 7152 (0x1BF0)
No Restricting Service Windows exist. It can therefore run... ServiceWindowManager 09/09/2015 08:16:08 7152 (0x1BF0)
OnIsServiceWindowAvailable called with: Runtime:900, Type:6 ServiceWindowManager 09/09/2015 08:16:12 5980 (0x175C)
        Biggest Active Service Window for Type=6 not found ServiceWindowManager 09/09/2015 08:16:12 5980 (0x175C)
Program cannot Run! Setting *canProgramRun to FALSE ServiceWindowManager 09/09/2015 08:16:12 5980 (0x175C)
OnIsServiceWindowAvailable called with: Runtime:1, Type:4 ServiceWindowManager 09/09/2015 08:16:15 1696 (0x06A0)
No Restricting Service Windows exist. It can therefore run... ServiceWindowManager 09/09/2015 08:16:15 1696 (0x06A0)
OnIsServiceWindowAvailable called with: Runtime:1, Type:6 ServiceWindowManager 09/09/2015 08:16:15 1696 (0x06A0)
        Biggest Active Service Window for Type=6 not found ServiceWindowManager 09/09/2015 08:16:15 1696 (0x06A0)
Program cannot Run! Setting *canProgramRun to FALSE ServiceWindowManager 09/09/2015 08:16:15 1696 (0x06A0)
WillProgramRun called with: Runtime:1, Type:6 ServiceWindowManager 09/09/2015 08:16:15 1696 (0x06A0)
A Service Window of this type exists. ServiceWindowManager 09/09/2015 08:16:15 1696 (0x06A0)
There exists a Service Window of this Type, for this duration. The Program will run eventually. ServiceWindowManager 09/09/2015 08:16:15 1696 (0x06A0

Thank you in Advance

September 9th, 2015 7:20am

What does the monitoring node tell for that deployment and device?
Free Windows Admin Tool Kit Click here and download it now
September 9th, 2015 7:34am

However this time round the servers started to update as per normal when the Maintenance Window and Stopped when the window closed.  As the window is not re-occurring and thus not needed, I decided to delete the Window, soon after this servers that were not fully compliant started installing and servers restarting.  I have re-applied the back-dated Maintenance Window and this has put a stop to updates and restarts occurring. 

From reviewing the collections that have Maintenance Windows set, non apply for the servers in question.

Can anyone please explain why this would occur? and possible fixes

How many MW do you have for these server? Did you delete the only MW for these server?

If so, this is normal, NO MW mean install everything at the deadline.

September 9th, 2015 9:08am

Said another way, having no maintenance windows configured means there are no restriction and is effectively equivalent to having a maintenance window in effect all of the time 24x7x365.
Free Windows Admin Tool Kit Click here and download it now
September 9th, 2015 9:21am

Thank you for the clarification.  I have set up a future (20 years) maintenance window on All Clients so they have at least one window. This will give me the ability to delete expired windows as and when.

Thanks again.

September 11th, 2015 10:21am

I would not put the MW that far ahead, 2020 is a good year or even better, Feb 14 2006!
Free Windows Admin Tool Kit Click here and download it now
September 11th, 2015 7:21pm

Once a device has a maintenance window applied whether it be in the future or in the past, ConfigMgr considers the device to have a maintenance window and will not process any deployments for that machine unless the deployment is set to ignore maintenance windows.

When maintenance windows are deleted, ConfigMgr considers the device not to have a maintenance window and any deployment that has reached its deadline will be executed on the device (for deployments that are still pending)

Setting a maintenance window for all clients way in the future means no deployments will run on any client unless you do one of the following:

  • Create a new maintenance window specifically for each deployment
  • Set the deployments to ignore maintenance windows
  • Delete the maintenance window applied to all clients

If you created the future maintenance window specifically to prevent deployments when other maintenance windows are deleted then I would suggest creating the window in the past rather than the future, the effect is still the same, but the risk of a future maintenance window is that one day it will become available and execute deployments.

I've written a small best practice guide on configuring maintenance windows, I'd recommend using dedicated collections to manage maintenance windows making them easier to manage:
http://blog.krissmilne.tech/configmgr/best-practice-tips-configmgr-maintenance-windows

September 11th, 2015 11:35pm

Once a device has a maintenance window applied whether it be in the future or in the past, ConfigMgr considers the device to have a maintenance window and will not process any deployments for that machine unless the deployment is set to ignore maintenance windows.

When maintenance windows are deleted, ConfigMgr considers the device not to have a maintenance window and any deployment that has reached its deadline will be executed on the device (for deployments that are still pending)

Setting a maintenance window for all clients way in the future means no deployments will run on any client unless you do one of the following:

  • Create a new maintenance window specifically for each deployment
  • Set the deployments to ignore maintenance windows
  • Delete the maintenance window applied to all clients

If you created the future maintenance window specifically to prevent deployments when other maintenance windows are deleted then I would suggest creating the window in the past rather than the future, the effect is still the same, but the risk of a future maintenance window is that one day it will become available and execute deployments.

I've written a small best practice guide on configuring maintenance windows, I'd recommend using dedicated collections to manage maintenance windows making them easier to manage:

blog.krissmilne.tech - Best Practice Tips! ConfigMgr Maintenance Windo

September 12th, 2015 3:34am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics