Fix include membership rules so that they properly automatically replicate collection membership changes based on incremental updates
As we discovered via premier call (ticket #:16602356). If you use an include or exclude collection rule it is supposed to automatically update the collection membership of the including collection if the included collection membership changes.
It does this properly if your included collection membership changes due to direct memberships or queries if using a full collection schedule. It also works if you trigger a manual collection update of the included collection or the including collection.
However it does NOT work if your included collection uses solely incremental collection updating. The included collection membership changes itself just fine, however the changes do not propagate to any collection that includes it.
I was informed that this is how the function is designed. But all the best practise documentation for efficient collection updating highlights you should not use too many unnecessary collection update schedules and explains that if you use incremental you do not need to set a full schedule. That is true... except not when your intent is to include the collection and you want changes to replicate to the including collection. This is clearly a design flaw.
No one uses an include rule without the intent of future membership changes getting automatically replicated.
In our case we needed the the included collection to update quickly so it was appropriate to use incremental because it will add changes every 5 minutes typically. Setting full collection schedule would solve the problem of changes not replicating to including except you shouldn't set full schedules that are 5 minutes in frequency (historically Microsoft have stated they don't like anything set more frequent than 1 per day in all SCCM RAPS I have been involved with). So that is less than ideal if you want the changes to replicate fast. The workaround that was advised to us was to set incremental collection updating on the including collection. That works but now you are putting in otherwise unnecessary incremental rules when the advice is you should never exceed 200..
Can we fix the behaviour so that incremental updating triggers the Auxiliary Evaluator which would make this function as you would expect?