Don’t be fooled by the new Site Server Servicing Window in ConfigMgr 1511

In ConfigMgr 1511 you have a new maintenance windows when you open the site server properties. That’s NOT for traditional software updates but for the new ConfigMgr Updates and Servicing model. You get to the maintenance windows in the Administration workspace, Site Configuration, Sites. Right the primary site and select properties. In the Maintenance Window tab, create a maintenance window (and make sure you call it something like ConfigMgr Dynamic update Only).


I did a few tests and the maintenance window do not apply to traditional software updates. According to my tests normal software software updates will still apply unless you create a collection based maintenance windows.

By | 2015-12-09T19:43:25+00:00 December 9th, 2015|Configuration Manager (SCCM)|3 Comments

About the Author:

Kent Agerlund
Microsoft Regional Director, Enterprise Mobility MVP. Microsoft Certified Trainer and Principal consultant. I have been working with Enterprise client management since 1992. Co-founder of System Center User Group Denmark in 2009. Certified MCITP: Enterprise Administrator, MCSA+Messaing, and much more. Member of: Microsoft Denmark System Center Partner Expert Team The Danish Technet Influencers program System Center Influencers Program.


  1. […] As mentioned here from Kent Agerlund (… This Maintenance Windows is only used when it comes to Install ConfigMgr Updates or Upgrades within […]

  2. Amanda January 19, 2016 at 3:58 - Reply

    Hi Kent, Thanks for the heads-up I have a scheduled maintenance next week and might come across that update if i wasn’t informed. Thanks a lot.

  3. kevin June 8, 2016 at 11:40 - Reply

    Hi Kent

    I posted this on the current branch forums as well, but was seeking in particular your thoughts.

    I work in an environment that has a CAS, 8 child primary sites and a LOT of dp’s.

    I tested successfully in a lab the use of maintenance windows to suppress the automated child primary site upgrade.

    When I went to upgrade in production I applied the maintenance windows (set in the far future no recurrance) on all sites except one site I wanted to upgrade in the same night as the CAS.

    Unfortunately after the CAS was upgraded the maintenance windows (now called service windows in 1602) were gone which then triggered off all child primary sites to upgrade and then send out stuff to their dp’s…

    There was one exception where one site did manage to keep the maintenance window and did suppress the upgrade!

    Have you had any experience along these lines of missing maintenance windows?? Is there any logs I can check to do some investigation as to why all but 1 maintenance window wasn’t migrated across during the CAS upgrade.

Leave A Comment