The goal of this blog is to clarify some misunderstandings around Collections in System Center Configuration Manager.
There is no right or wrong, the goal is that you understand the impact of the different scenarios.
The following pretty picture (powered by MSPaint) is supposed to show you an easy collection design. If I say ‘Update Membership’ on ‘All Systems’ then the collection evaluation (Coll Eval) process will kick in and check for any new members in All Systems. Coll Eval will now check ALL the collections that are limited by All Systems if these collections are going to be affected by this new member.
What would have been if all your collections were limited to ‘All Systems’?
Right, because of one new member ALL your collections would have been evaluated.
The default value in Config Mgr 2012 R2 is 5 minutes. Machines just wouldn’t pick up any deployments, even after a week of waiting. They were using AD Security groups as targets for their Software Deployments. The threshold is about 200 collections in your hierarchy.
The exact number depends on the following factors: Hierarchy here means that if you have a CAS and several primaries then those 200 collections is a TOTAL over all your sites. Nothing you can directly trigger in any way, but during your collection design this is something you should definitely keep in mind!