I am trying to determine what changes are occurring with our AD objects that cause an average of a 200 incremental changes to occur on the All Systems Collection (SMS00001) every (10 minutes)? Since 200 changes occur on the All Systems collection and we have 80 collections that are limited to the All Systems collection that are also set for incremental, (Well under the 200 max.) all of those collections must also re-evaluate those 200 object changes. I believe one of the attributes in AD System Discovery might be causing all of the incremental collection changes so I was wondering if anyone has any suggestions of identifying what is changing in AD to cause all the incremental collection changes in SCCM?  

"Anytime a parent collection gets updated (by full or incremental) it will trigger an update on all child (limiting) collections below it. So if CollA gets updated, it should trigger an update of CollB."

Please see the following links:

https://social.technet.microsoft.com/Forums/en-US/dc8c2ea6-abbd-4e95-9173-1edff43a6e69/limit-to-collection-how-does-it-work-with-incremental-collection-updates?forum=configmanagergeneral

http://blogs.technet.com/b/configmgrdogs/archive/2012/04/16/configmgr-2012-incremental-collection-update-delta-discovery.aspx

-RG

If I'm reading your question right you're trying to figure out what change is causing the update.  The log to lookat then should be ntsvrdis.log for site system discovery.

https://technet.microsoft.com/en-us/library/bb633276.aspx

Also, I get the impression that your "all systems" probably has too many collections pointed at it.  Create some simple "stop-gates" at the top like "all workstations" and "all servers" then limit 90% of your collections to that.  Not only will it make future RBAC easier but it will keep the "All Systems" from setting off a mountain of replication when it updates.

• Edited by Justin.King 16 hours 16 minutes ago

RG, thank you for your quick response but you do not understand my question. I am well aware of what happens to the limited collections when the parent collection gets updated. That is not what I am asking. Perhaps I can phrase it another way. When the collection evaluator evaluates the "All Systems" collection and finds 200 incremental changes for the "All Systems" collection, how can you determine exactly what changed and where, to cause the 200 incremental changes? Again, I am strictly talking about the "All Systems" collection. Perhaps there is a relationship between AD System Discovery and the attributes that are being discovered which would update the objects in the All Systems collection therefore picked up by the next incremental refresh?  

Hi,

Client attributes are collected by discovery, and membership rules evaluate according to these attributes:

https://technet.microsoft.com/en-us/library/bb632733.aspx

In addition, about heartbeat discovery, Jason has a good blog:

http://blogs.catapultsystems.com/jsandys/archive/2011/04/29/what%E2%80%99s-in-a-heartbeat.aspx

Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.