Sccm 2016 collections not updating
Too many incremental update can really slow down all collection membership evaluation.
You can get more information about Incremental Update and collections here.
After the full update runs you can check the properties of the view which represents that collection in your database and see that it was just newly created.
Speaking SQL it will execute a stored procedure on the database which will rebuild the view for that specific collection.
Imagine that happening in your uber large environment with hundreds of collections with complex queries and such.
So always keep in mind: Don’t limit your collections by ‘All Systems’!
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!
Search for sccm 2016 collections not updating:
;-)Collections have members and members can change, that’s why we need to regularly update our collections.