An error occurred while saving the commentDave Wall commented
Hi, I have just been through the painful exercise of reducing the number of Incremental collections and had to do a deep dive on this subject i.e. try to understand from scratch. Originally I found the forum reply from Wally Mead which is correct but is very old:
"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."
When I tested this at face value I found this was NOT the case (in 2020).
I managed to find this article from Nathan Zeihnert it is a quick & worthwhile read dated April 2019.
I found this statement from the above web site matched what I saw in my testing:
"When a collection flagged for incremental updates detects changes, it causes collections using it as a limiting collection (child collections) to be updated ONLY WHEN THAT COLLECTION IS ALSO FLAGGED FOR INCREMENTAL UPDATES." i.e. A parent collection with incremental updates enabled will only update a child collection if that child collection also has Incremental updates enabled. Otherwise the child is not updated.
I am voting for this as the documentation for Collection management does not go into enough detail for admins to understand what they need to do, and the process is very restrictive, especially if you want to use SCCM for application deployment by linking collections to AD Security groups via WQL.