Config Manager 2012 Slow Updating Collection Membership

Hi All,

I have been experiencing a problem with slow updating of collection memberships.

The problem is that when adding a device to a Device Collection using direct membership, and then performing an Update Collection Membership, it takes approximately 5 minutes before the collection is updated, which was not a problem I experienced in Config Manger 2007.

I have looked at the views in SQL for the collections, and this is what I found.

The view called v_CM_RES_COLL_C000000C (where C000000C is the collection ID), is the actual collection membership.

The view called v_CollectionRuleDirect is where Config Manager stores it's direct membership collection rules.

Upon adding a device to the collection as a direct member, Config Manager immediately updates the view v_CollectionRuleDirect with the direct membership for the collection.  Meanwhile the view v_CM_RES_COLL_C000000C does not reflect this added direct membership.

Performing a Update Collection Membership then in theory should force Config Manager to review v_CollectionDirectRule and update the actual members in v_CM_RES_COLL_C000000C, but this does not happen for about 5 mins for some reason, no matter how many times you update the collection membership.

Once v_CM_RES_COLL_C000000C is updated, then the console is updated also, as for OSD and Package deployment it is considered a member of the collection.

Any idea's on how we can speed up this process?

Regards,

Sally

June 5th, 2012 2:19am

have you already checked colleval.log for more details?

Also, you will get Some tips from Greg's blog post - http://gregramsey.wordpress.com/2012/02/15/how-to-enable-incremental-collection-updates-with-powershell/

Free Windows Admin Tool Kit Click here and download it now
June 5th, 2012 5:34am

Are you using a standalone primary site or a CAS + primary?
June 5th, 2012 7:02am

Just out of interest, are you using the Import Computer Information wizard to create your computer object? I have seen the exact same delay in multiple CM12 environments but only when using this method to create a computer object in the site database (and yes it is quite frustrating! :))
Free Windows Admin Tool Kit Click here and download it now
June 5th, 2012 7:50am

Are you updating collection membership at the CAS or Primary?

If updating at the CAS, then the delay is expected as the evaluation is done on the Primary and everything is replicated back up.

ThanksMoiz

June 12th, 2012 5:17am

Just out of interest, are you using the Import Computer Information wizard to create your computer object? I have seen the exact same delay in multiple CM12 environments but only when using this method to create a computer object in the site database (and yes it is quite frustrating! :))
Did you ever work out why this might be happening? I am seeing very slow collection update times on a virgin CM2012 install.
Free Windows Admin Tool Kit Click here and download it now
July 24th, 2012 6:12pm

I had to learn patience with SMS/SCCM, it appears that we have to learn even more patience with SCCM 2012.  I've seen the collection membership be stretched out with both collection query rules and with imports, but imports seem to be worse.

This is going to cause us problems since we use a just in time approach to OSD where the computer is added to the collection just as it's needed.  The tech can then trigger the deployment by simply doing a machine policy refresh.  With SCCM 2007 the delay was usually less than 30 seconds.  With 2012, this is going to likely affect our process and how we go about doing things.

This is also going to impact administration since we are going to be going for coffee a lot while we wait for the SCCM 2012 collections to finally update so we can validate that what we have set is correct.

Overall, I've been very disappointed by the responsiveness of SCCM 2012.  I'm using a CAS and Primary, and no matter where I make changes they take a long time to update in the collections.  I think I'll go check on Connect and see if anyone else has bugged this, if not I'll enter one.  The SCCM group has to figure out how to make this work faster.
August 8th, 2012 4:00pm

There was an entry under the beta/RC levels that was closed by design.  I created a new one under the title "Collection Update speed unacceptable" if anyone wants to vote on it.  I understand why it happens, largely because of the replicated database issue and the time those replications take to happen and get picked up by the site controllers. In an ivory tower situation that's fine, but in the real world the delays are extremely annoying, it sounds like they need to add a high speed communications alert system to the product or some other way to get the system to be more responsive.

Free Windows Admin Tool Kit Click here and download it now
August 8th, 2012 4:13pm

There was an entry under the beta/RC levels that was closed by design.  I created a new one under the title "Collection Update speed unacceptable" if anyone wants to vote on it.  I understand why it happens, largely because of the replicated database issue and the time those replications take to happen and get picked up by the site controllers. In an ivory tower situation that's fine, but in the real world the delays are extremely annoying, it sounds like they need to add a high speed communications alert system to the product or some other way to get the system to be more respo

October 4th, 2012 10:20am

Did anybody figure this out?  I've got this problem now in a brand new CM 2012 SP1 environment.  Stand-alone primary site server, using a stand alone SQL 2008 R2 SP2 server.

I'm experiencing 5-10min delays for collections to update (sometimes up to 30 minutes).  But mostly around 5-10min.

Free Windows Admin Tool Kit Click here and download it now
January 29th, 2013 5:27am

colleval.log will tell details.
January 29th, 2013 7:12am

You have a lot of chance to get a 5, 10 min delay. 

I m SCCM admin, we have 35 000 PC world wide, 1 CAS, 1 PS, 26 DP, 4 MP. 

we have 1300 collections. 

I'm experiencing 30 min delay for collection to update during business hours ! 

Free Windows Admin Tool Kit Click here and download it now
February 20th, 2013 6:24pm

We were experiencing the same thing when we noticed in the colleval.log that incremental updates[Express Evaluator] entries were occurring non-stop and taking up to 8 seconds to perform each express evaluation plus handling those evaluations one at a time (synchronously). We could also see in the log an entry for every time we hit the refresh (F5) which said an evaluation refresh task was already in the queue and would take more than 10 minutes sometimes before it actually ran the refresh. We then realized we had over 200 collections that had the Use incremental updates for this collection enabled. Once we reduced the number of collections using that setting to under 25 using a PowerShell script, refresh times went from minutes to seconds. Here is a link to the Best Practices for Collections which mentions the issue. Not saying it will solve everyones refresh issues but it did solve ours.

  http://technet.microsoft.com/en-us/library/gg699372.aspx

February 22nd, 2013 2:07pm

We are in the testing phase and see this also. Same scenerio: Import new machine into ConfigMgr 2012 "OSDeployment" collection. Direct Membership is seen in the properties of the collection, but the machine never shows up in collection, so OS Deployment Task Sequence never gets a chance to start. "Update Collection Membership" and refreshes done manually the machine eventually shows up after 4 or 5 minutes. If no manual "Update Collection Membership" and refresh, the machine may never show up (over 30 minutes of waiting).
The only thing that works immediately is if we advertiese the Task Sequence to "Unknown Computers", boot the machine and start the OSD process. The task sequence is picked up and a build starts immediately. I don't like having a build process targeting All Unknown Computers for obvious reasons, but I may have to create some checks in the Task Sequence to query WMI for an OS, or prompt (no REQUIRED deployments).
Now ,if the machine is already in SCCM for a while or visable in the collection, there is no issues.
I may import machine information into SCCM in advanced, but then there will be an issue (I think) if someone wants to build new and override the Resource Record that already exists in SCCM 2012.
Free Windows Admin Tool Kit Click here and download it now
February 26th, 2013 2:16pm

Don't forget that if your limiting collection is "All Systems" the device has to exist to in this collection before it will appear in any user defined collection. 

For my automation to work I have to refresh All Systems, wait for a device to appear then refresh the user created device collection. 

Could you all please verify you are not being limited (so to speak) by your limiting collection? 

I have lots and lots of devices and tend to see instantaneous refreshes of any collection, providing the set-up is right. 


  • Proposed as answer by netjim66 Tuesday, February 26, 2013 5:04 PM
February 26th, 2013 2:28pm

Don't forget that if your limiting collection is "All Systems" the device has to exist to in this collection before it will appear in any user defined collection. 

For my automation to work I have to refresh All Systems, wait for a device to appear then refresh the user created device collection. 

Could you all please verify you are not being limited (so to speak) by your limiting collection? 

I have lots and lots of devices and tend to see instantaneous refreshes of any collection, providing the set-up is right. 


  • Proposed as answer by netjim66 Tuesday, February 26, 2013 5:04 PM
Free Windows Admin Tool Kit Click here and download it now
February 26th, 2013 2:28pm

Right now I'm using a runbook with a powershell script to import machine info into a collection.
I'll have the script import the machine into both the "All Systems" and my custom collection, but I have a feeling it will still take just as long to get the machine to show up in "All Systems".

I'll test now...
February 26th, 2013 3:28pm

Seemed to work.

Imported machine info (new machine) into SCCM 2012 (direct-membership to my "OSDeployment" collection).

Immediately update "All Systems" collection. SCCM then sees the new machine.

Then I have to go back and update my "OSDeployment" collection, since it's based on the "All Systems".

Before I would have to wait and wait until the machine would be visible, now it seems to show up within 30 seconds or so....

Free Windows Admin Tool Kit Click here and download it now
February 26th, 2013 4:08pm

Great! 

Glad i could help somewhat. 

This caused me all sorts of pain when i started writing my interface for config manager. I found no mention of it in the documentation, but i suppose it makes sense. What i don't really understand is the need to have so many layers of abstraction, but hey ho. 

I think the irregular automatic updating of All Systems might be why people saw the behaviour they saw. 

February 26th, 2013 4:20pm

Hi netjim66

I am having a similar issue and previously used webservice to add machines to the collections and do the refreshes. The problem I have is that despite the webservice "seeing" the machine as being a member of the collection, when my preexecution hook hands baclk to the sccm task sequence, it doesn't see the machine as a member. It must use a slightly different query mechanism. It shows up usually within 30s of this so currently just runniung with a pause in the script, which I really don't like.

Would it be possible for you to share your ps script since it seems to get the job done more efficiently and perhaps uses the same mechanism as native ts wizard?

Thanks

Free Windows Admin Tool Kit Click here and download it now
March 13th, 2013 9:32am

Don't forget that if your limiting collection is "All Systems" the device has to exist to in this collection before it will appear in any user defined collection. 

For my automation to work I have to refresh All Systems, wait for a device to appear then refresh the user created device collection. 

Could you all please verify you are not being limited (so to speak) by your limiting collection? 

I have lots and lots of devices and tend to see instantaneous refreshes of any collection, providing the set-up is right. 


Is there a best practice for a limiting collection when adding systems to SCCM for building purposes?  I would think your best bet would be a default collection, because otherwise you are adding a "middle man" that has its own refresh/update schedule to deal with.  Is there a better limiting collection than All Systems if you are doing a scripted Import Computer Information
January 14th, 2014 5:06pm

Anyone got a good solution for this? Im having the same issue.

Free Windows Admin Tool Kit Click here and download it now
June 30th, 2014 7:58am

How many clients and collections are we talking about?
June 30th, 2014 8:21am

I have had a collection updating for over three hours now and the timer still hasn't stopped going SCCM2012 SP1
Free Windows Admin Tool Kit Click here and download it now
July 1st, 2014 6:48pm

Maybe this will help: 

 - Check the colleval.log and filter by seconds to evaluate how long it's taking.

 - It's not recommended to have more than  200 collections set with incremental evaluation (for example, if you have 250 collections which each take 1.5 seconds to evaluate that adds up to over 6 minutes and the default evaluation time is set to 5 minutes so it never gets time to run through everything) You can change/check this under \Administration\Overview\Site Configuration\Sites - right-click Sites, Configure Site Components > Collection Membership Evaluations

 - Don't use 'Not Like' queries if possible

http://www.sysadmintechnotes.com/2014/02/17/sccm-collection-evaluations-take-a-long-time-to-evaluate/

  -  check C:\Program Files\Microsoft Configuration Manager\inboxes\COLLEVAL.box and the Retries folder. If there are entries under the root folder you may need to archive these somewhere else (stop the service mentioned below first)

 - restart the "sms_collection_evaluator" component from the Configuration Manager Service Manager - see below (Also you have to select Query before the other options are available)

https://social.technet.microsoft.com/Forums/en-US/7dc2e940-8968-4a1a-8b90-2265db28eb1b/collection-evaluation?forum=configmanagergeneral

 - Cut down on the number of collections limited to 'All Systems'

http://www.david-obrien.net/2014/05/configmgr-collection-updates/


June 29th, 2015 11:07pm

I recently had issues with collections not updating correctly/speedily and this is a collection of all the information I found on tings to try/check: 

 - Check the \\%Servername%\D$\Program Files\Microsoft Configuration Manager\Logs\colleval.log and filter by seconds to evaluate how long it's taking.

 - It's not recommended to have more than  200 collections set with incremental evaluation (for example, if you have 250 collections which each take 1.5 seconds to evaluate that adds up to over 6 minutes and the default evaluation time is set to 5 minutes so it never gets time to run through everything) You can change/check this under \Administration\Overview\Site Configuration\Sites - right-click Sites, Configure Site Components > Collection Membership Evaluations.

*For a query which shows all collection update types see the bottom of this post

 - Don't use 'Not Like' queries if possible

http://www.sysadmintechnotes.com/2014/02/17/sccm-collection-evaluations-take-a-long-time-to-evaluate/

  -  check C:\Program Files\Microsoft Configuration Manager\inboxes\COLLEVAL.box and the Retries folder. If there are entries under the root folder you may need to archive these somewhere else (stop the service mentioned below first)

 - restart the "sms_collection_evaluator" component from the Configuration Manager Service Manager - see below (Also you have to select Query before the other options are available)

https://social.technet.microsoft.com/Forums/en-US/7dc2e940-8968-4a1a-8b90-2265db28eb1b/collection-evaluation?forum=configmanagergeneral

 - Cut down on the number of collections limited to 'All Systems'

http://www.david-obrien.net/2014/05/configmgr-collection-updates/

 - Query for a report showing collection update types:

https://social.technet.microsoft.com/Forums/en-US/690611ff-b6f7-4d52-b4cc-2022f983c02c/config-manager-2012-slow-updating-collection-membership?forum=configmanagergeneral

 - Remember that Incremental update collections don't work well if their membership rule is an include/exclude. You may have to add one direct membership rule to the colelction also as a work around or change it to a query rule.

https://social.technet.microsoft.com/Forums/en-US/f773807c-4b7e-45f7-9647-e2c3359f3991/why-do-collection-incremental-updates-dont-work-for-includeexclude-rules

 - Show all collections and their update type

SELECT CollectionID, Name as [Collection Name],

CASE RefreshType

  

WHEN 1 THEN 'No Scheduled Update'

 

WHEN 2 THEN 'Full Scheduled Update'

  

WHEN 4 THEN 'Incremental Update (only)'

  

WHEN 6 THEN 'Incremental and Full Update Scheduled'

  

ELSE 'Unknown'

  

END AS RefreshType,

 

 

Comment, LastChangeTime, EvaluationStartTime

  

FROM  dbo.v_Collection

  

ORDER BY RefreshType, [Collection Name]




Free Windows Admin Tool Kit Click here and download it now
June 30th, 2015 3:03am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics