Sccm collection membership not updating
The wrong naming of sites codes on creation of a site can encounter errors in relation to the long waiting time for collections to be ready on membership-refresh.
Be very careful when you plan your site codes and site names before deploying the Configuration Manager 2007 hierarchy!
This means, every time you manually refresh collection membership, you are the very first in line to get the job done.
This will result in less or none waiting time for the collection to update the membership.
Although big collections like “All Systems” or “All Computers” containing 500 or maybe 5000 computers may require up to 1 hour for a membership refresh depending on how long the queue is.
You will just keep building up the queue ´cause to the many scheduled requests and every time you want to do a manual collection membership update, you end up in the back of the line.
Configuration Manager has built-in collections for common operations, and you can also create custom collections.
By default, Configuration Manager includes the following collections, which cannot be modified.
You can create collections to match your client management needs, and to perform operations on multiple resources at one time.
If you are having problems with collections taking a long time to refresh membership, it is very possible that you have incremental updates or collection membership evaluation schedule set of happen frequently on a large number of collections.