A little known fact with ConfigMgr is that there is a “soft” limit to the number of incremental collections you can have. It’s actually referenced here in TechNet. The factors that affect where this actual limit is is dependent upon your total number of collections, the frequency of new resources being added, the number of clients in your hierarchy, and the complexity of the collection membership rules.
If you surpass the approx. 200 limit for your incremental collections, then you will experience some interesting behavior with your collections. Some will update, some won’t, it appears to be random. I’ve seen this at a few clients that have had over 200 collections set to incrementally update.
I’ve had a query I’ve been using for awhile at clients, however Steve Thompson demo’d a much prettier query at MMS. His query is shown below:z
Collection eval - incremental updates CASE, ALIAS, ORDER BY SELECT CollectionID, Name as [Collection Name], CASE RefreshType WHEN 1 THEN 'No Scheduled Update' WHEN 2 THEN 'Full Scheduled Update' WHEN 4 THEN 'Incremental Update (only)' WHEN 6 THEN 'Incremental and Full Update Scheduled' ELSE 'Unknown' END AS RefreshType, Comment, LastChangeTime, EvaluationStartTime FROM dbo.v_Collection ORDER BY RefreshType, [Collection Name]
Running this query in SQL Management Studio will produce a list of the collections you have and how they are configured. It’s important to take note of of how many collections you have that are configured for incremental.