I have certainly seen scenarios where delta can take longer to run than full discovery. There was an update released but I think it went into R2
We have had some real issues with discovery processing excessive entries - we had an OU with 7,500 groups of which we were "only" interested in 1800. Sometimes (and for no apparent reason discovery seems to trigger huge TEMPDB activity which then replicates and cascades to the primaries. > On 11 Sep 2015, at 21:11, Juett, Jeffery C. <[email protected]> > wrote: > > Not that I remember. It was an issue that had just been nagging at me for > some time. I was finally able to gather some SQL stats during one of the > pauses in the collection evaluator and was able to narrow it down to the > delta discovery while discussing the issue with a consultant we had on site > for another engagement. I had tried several increasing values in the delta > polling interval, which only seemed to change the frequency with which we saw > the collection evaluator pause. I’ve seen this on both ConfigMgr 2012 SP1, > with every CU released, as well as on ConfigMgr 2012 R2 with CU3, 4, & 5. > > Thank you, > > Jeffery C. Juett > SCCM Administrator, Information Technology > > UnityPoint Health > [email protected] > > From: [email protected] [mailto:[email protected]] > On Behalf Of Denzik, Josh > Sent: Friday, September 11, 2015 2:05 PM > To: [email protected] > Subject: RE: [mssms] Collection Eval Slow Updating > > Was there a catalyst or cause for this? Did something change in your > environment like installing a CU or SP1 that caused the issue? > > From: [email protected] [mailto:[email protected]] > On Behalf Of Juett, Jeffery C. > Sent: Friday, September 11, 2015 1:42 PM > To: [email protected] > Subject: RE: [mssms] Collection Eval Slow Updating > > > > We had seen that same thing in our environment. We were eventually able to > narrow it down to AD system discovery delta discoveries running on our site > server. Our AD environment is also in a bit of a shambles, which didn’t help > the situation. > > We currently have about three dozen enabled for incremental updates. > > We ended up turning off system delta discovery entirely and changed the full > system discovery to run once per hour. We haven’t seen the issue since. > > Thank you, > > Jeffery C. Juett > SCCM Administrator, Information Technology > > UnityPoint Health > [email protected] > > > From: [email protected] [mailto:[email protected]] > On Behalf Of Denzik, Josh > Sent: Friday, September 11, 2015 12:32 PM > To: [email protected] > Subject: RE: [mssms] Collection Eval Slow Updating > > 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]] > On Behalf Of Denzik, Josh > Sent: Friday, September 11, 2015 7:54 AM > To: [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 > > > > > > > > > This message and accompanying documents are covered by the Electronic > Communications Privacy Act, 18 U.S.C. §§ 2510-2521, and contain information > intended for the specified individual(s) only. This information is > confidential. If you are not the intended recipient or an agent responsible > for delivering it to the intended recipient, you are hereby notified that you > have received this document in error and that any review, dissemination, > copying, or the taking of any action based on the contents of this > information is strictly prohibited. If you have received this communication > in error, please notify us immediately by e-mail, and delete the original > message. > > > > > > > This message and accompanying documents are covered by the Electronic > Communications Privacy Act, 18 U.S.C. §§ 2510-2521, and contain information > intended for the specified individual(s) only. This information is > confidential. If you are not the intended recipient or an agent responsible > for delivering it to the intended recipient, you are hereby notified that you > have received this document in error and that any review, dissemination, > copying, or the taking of any action based on the contents of this > information is strictly prohibited. If you have received this communication > in error, please notify us immediately by e-mail, and delete the original > message. > > >
