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. I was wondering how others have dealt with this issue.
My SCCM 2007 collection hierarchy is four collections deep. Nested at the bottom is a test collection of systems. Each collection has a maintenance window. The test collection and the collection above it, collection 1, have Thursday maintenance windows. Collection 2 has a Friday maintenance window and collection 3, one on Saturday. 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. (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. Using the option 'this collection and subcollections', I was able keep these updates available for successive maintenance windows after the advertisement reached the top.
This design seems pretty common, so I was wondering how others are dealing with the flat design of SCCM 2012 and the elimination of the subcollections.