SCCM2012 SP1 - Maintenance Windows in Orphaned State

I have created a number of collections in SCCM2012 SP1 with maintenance windows set. These are used to schedule installation of Software Updates. All has been working fine, until I needed to amend the times set on a maintenance window on a collection. The old maintenance windows was deleted and a new one created. Everything looked to be working fine, until I noticed days later that servers were still rebooting during the old schedule that has been deleted.

Running the "Maintenance windows available to a specified client" report shows that clients in this collection have 2 maintenance windows available. The original one and the new one. I checked which collections that the client is a member of using the right click tools, and checked each of those collections for any maintenance windows - there are none.

I have tried deleteding the maintenance window collection and creating with no maintenance window set, but the report still shows that the clients have 2 maintenance windows set, even though there are now none.

I have tried uninstalling the configuration manager client from the affected machines, deleting the client object in the SCCM Console and reinstalling, but after a while the maintenance windows show in the report once again.

I can only find one other instance of orphaned maintenance windows during a search on Google, but that occured in SCCM 2007 when a user had multiple sites. This is a fairly simple set up - single site, single server with the SQL database on a separate box. Really need some help on this one!

Thanks!

August 22nd, 2013 11:42pm

There is a good writeup posted here:

http://blog.tyang.org/2011/08/16/orphaned-maintenance-windows-for-sccm-clients/

Basically the policies still exist in the database and need to be fished out manually with SELECT and DELETE statements. Would be nice if anyone had a cleaner solution?

Free Windows Admin Tool Kit Click here and download it now
October 27th, 2014 8:49pm

Keep in mind that editing the database is unsupported and you should always open a support case with CSS for this type of thing.
February 1st, 2015 11:06am

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

Other recent topics Other recent topics