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

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/

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

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! :))

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.

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

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.

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 ! 

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

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

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

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....

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. 

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

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. 

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

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'

• Edited by andrewjohnporter 3 hours 24 minutes ago

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

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]

• Edited by andrewjohnporter 1 hour 45 minutes ago