Problem case: Slow collection refresh, up to 30 minutes.
There are two known issues regarding this problem.
1. Schedule refresh rates.
The first possible issue with slow refresh rate on collections could be the schedule on each and every collection in your setup. If you got a bunch of collections and they are scheduled to update frequently, you may run into this problem. To find the collection schedule, right click a collection – click Properties – click the Membership Rules tab – and click schedule… button as shown on the pictures below.
Let me tell you a little bit about how the collection queue works. Configuration Manager got a component called “Collection Evaluator”. This component works with a first-in, first-out (FIFO) queue to handle the collection evaluation requests. Let’s say your setup contains 300 collections refreshing with an interval of 20 minutes. This is OK for collections containing none or a small amount of computers. 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. It is therefore recommended to review all your collection schedules, and plan the update rate carefully.
Note: Troubleshoot the colleval.log on the Central site server for information about the current
The Microsoft KB Hotfix listed at the bottom of the page will change the queue priority. 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.
2. Second, the Configuration Manager site naming.
Because some Configuration Manager 2007 components use the site code in folder names, you should not specify Microsoft Windows reserved names such as:
AUX, CON, NUL, PRN
Note: Configuration Manager Setup does not verify that the site code entered is one of Microsoft Windows reserved names.
Now this is a problem for regular names like CONnecticut(United States) or NULato(United States) e.g.
Review the list below for allowed site code names:
A through Z, 0 through 9 and the hyphen (-)
Note: Changing the site code or site name after installation is not supported.
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!
Schedule and plan your collections refresh rate very carefully.
Check MS KB hotfix for queue to handle collection requests here. Review your site code naming and change if possible.