I am seeing this with all collections in our environment. It even happens to collections with only 10 members in it. We do not have a CAS only one primary site.
From: [email protected] [mailto:[email protected]] On Behalf Of Nick Sent: Friday, September 11, 2015 11:09 AM To: [email protected] Subject: RE: [mssms] Collection Eval Slow Updating How many members are in the collections that you’re seeing this with? Is it all collections or just one? How many deployments are targeted to those collections. For each deployment, there are two policy entries per member of the collection. There are tons of SQL triggers and stored procedures running when collection membership changes. If you’re using a CAS, your hour-glass will only go away once the primary sites are done processing all the policy changes for those deployments/members and updating the collection additions/removals. If you have distant child primaries, and also pending your replication times, it may take a bit for the hour glass to go away and for your membership to report properly. So, lots of members with many deployments can take a while to process an update if there are large membership changes. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Denzik, Josh Sent: Friday, September 11, 2015 7:54 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] Collection Eval Slow Updating All, We recently updated our server to SCCM 2012 R2 SP1 (CU1). This past Friday we I started noticing long collection eval times. I would manually update a collection and it would take 30-45 minutes to eval the collection. The collection eval logs do not move during those 30-45 minutes its stopped at “PF: Looking for candidates for incremental evaluation” Then the system will act normal and process collection evaluations for 45 minutes straight without a hiccup. This pattern happens over and over. I don’t see any errors in the colleval.log and; I don’t see anything wrong with the SMS_COLLECTION_EVALUATOR component either. We also have less than 100 collections with incremental updates set as well. Server has been rebooted as well. I did find one post on TechNet from one person who seems to be having the issue but never actually got it resolved. Logs are attached. https://social.technet.microsoft.com/Forums/msonline/fr-FR/39f1740e-904e-44a7-834e-c455f4607e70/all-systems-collection-does-not-auto-populate?forum=configmanagergeneral Thanks, Joshua Denzik Senior Systems Engineer | Managed Desktop Team | Medical University of South Carolina
