Using the option 'this collection and subcollections', I was able keep these updates available for successive maintenance windows after the advertisement reached the top. (The week's delay is a testing/proving period required by administration.) And then on successive days, I'd retarget the advertisement to the collection above it on successive days util reaching the top, collection 3.

With this design, I was able to create a single package and advertisement each month, applying it to the test collection on the first week, and after a week's delay moving the same advertisement to the collection above it after a weeks delay. Collection 2 has a Friday maintenance window and collection 3, one on Saturday. The test collection and the collection above it, collection 1, have Thursday maintenance windows. Each collection has a maintenance window.

Nested at the bottom is a test collection of systems. My SCCM 2007 collection hierarchy is four collections deep. I was wondering how others have dealt with this issue. I made extensive use of subcollections in SCCM 2007 and I'm in the process of prototyping our new SCCM 2012 environment which has eliminated subcollections.

Sccm patching