locked
ConfigMgr R3 - Dynamic Collection Evaluation RRS feed

  • Question

  • Hi -

    We have enabled Dynamically add new resources (http://technet.microsoft.com/en-us/library/ff977051.aspx) option in all the collections. The collection update cycle is set to 1 day. And most of the collections are based AD system group query.

    We already have a system which is installed, present in SCCM DB and also part of all the other required collections. For testing Dynamic collection evaluation, I have added that system account to a AD application group. AD system group discovery is running every 2 hours and AD System group discovery updated the ad group details in the system record and I can see that group details in the system record properties in SCCM console. However, the collection is not dynamically getting updated. Even I have checked the colleval.log and it says “Incrementally refreshing results for collection %” and “Results refreshed for collection %, 0 entries changed”. When I checked the collection properties it was showing "Last Update" and "Last Membership change" as the same date and time. If I do a manual update of collection then the system will come to the collection immediately.

    What could be the reason for this behavior?

    I have gone through the article “About Dynamic Collection Evaluation in Configuration Manager 2007 R3” http://technet.microsoft.com/en-us/library/ff977097.aspx

     

    And it says

     

    The following resources can be evaluated by dynamic collection evaluation:

    • Resources that have been initially discovered.
    • Resources that have been provisioned with operating system deployment.
    • Resources that have been scanned for initial hardware inventory.
    • Resources that have been upgraded to a newer version of the Configuration Manager 2007 client.

    (If the resource is being discovered for the first time then only dynamic collection evaluation is applicable? And if the resource is already discovered and if we are just adding an application group as explained above then it won’t consider for dynamic collection evaluation?)


    Anoop C Nair
    Tuesday, May 24, 2011 5:13 PM

Answers

  • Dyanmic Collection eval basically only works for systems that ConfigMgr did not previously manage and has just created a new resource record for. If the managed system was in ConfigMgr previously, it is not considered for dynamic collection eval. Changes to an existing system are not considered for dynamic collection eval.
    Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys
    Tuesday, May 24, 2011 8:57 PM
  • Yes and yes - and that can be very easily tested.
    Torsten Meringer | http://www.mssccmfaq.de
    Wednesday, May 25, 2011 6:23 AM

All replies

  • Hi,

    You are right in your conclusion dynamic collection evaluation is linked with "Delta Discovery"

    "The interval by which Delta Discovery searches for new resources can be configured by the user to be a short interval, because only discovering new resources does not affect the performance of the site server as much as discovering a full cycle." http://technet.microsoft.com/en-us/library/ff977086.aspx 

    The delta discovery only discovers newly added computers in the domain and updated computer objects, so in your tests try to change the description for the computer object at the same time you add it to a group, this will make the delta-discovery update the object as the AD-object is modified and then the new group membership is added aswell and you will see that everything is updated.

    Adding the computer to a group updates the group object in AD and not the Computer object. You can see the result of the delta discovery in adsysdis.log there you can see that the Delta discovery now sees that the object is updated and do doscover it.

    I agree that it is not crystal clear how this works in SCCM 2007 R3 and it is not useful in all scenarios.

    Regards,
    Jörgen 


    -- visit my System center blog at http://ccmexec.com --
    Tuesday, May 24, 2011 6:16 PM
  • Hello Jörgen - Thanks for the reply. As I mentioned in the above post we are already aware of the fact that the AD system group delta discovery is not helpful because "Delta Discovery does not collect nonreplicated attributes that are changed, such as the memberof attribute". So we are not kept the option of AD system group delta discovery. We are doing AD system group full discovery and that is scheduled to run every 2 hours. I don't have any problem with that discovery results it's working like a champ.

    I am concerned about the option "Dynamically add new resources" is not functioning properly in my scenario. Every time, we need to wait for full update cycle of collection get the membership updated. So I just wanted to know, we need to meet any special condition for "dynamic collection evaluation" to work as mentioned in the TechNet article.

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

    The following resources can be evaluated by dynamic collection evaluation:

    ·     Resources that have been initially discovered - What does this point mean? (If the resource is being discovered for the first time then only dynamic collection evaluation is applicable? And if the resource is already discovered and if we are just adding an application group as explained above then it won’t consider for dynamic collection evaluation?)

    ·     Resources that have been provisioned with operating system deployment.

    ·     Resources that have been scanned for initial hardware inventory.

    ·     Resources that have been upgraded to a newer version of the Configuration Manager 2007 client.


    Anoop C Nair - This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Tuesday, May 24, 2011 7:10 PM
  • Dyanmic Collection eval basically only works for systems that ConfigMgr did not previously manage and has just created a new resource record for. If the managed system was in ConfigMgr previously, it is not considered for dynamic collection eval. Changes to an existing system are not considered for dynamic collection eval.
    Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys
    Tuesday, May 24, 2011 8:57 PM
  • Hi Jason - Many thanks. So collection eval is only applicable for "Resources that have been initially discovered" as mentioned in the above article and that was the catch. However, if we delete the record from SCCM and then the dynamic collection eval should pickup? 


    Anoop C Nair - This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Wednesday, May 25, 2011 1:56 AM
  • Yes and yes - and that can be very easily tested.
    Torsten Meringer | http://www.mssccmfaq.de
    Wednesday, May 25, 2011 6:23 AM
  • Many thanks Torsten. Yes, I agree it can be tested very easily :)
    Anoop C Nair - This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Wednesday, May 25, 2011 6:26 AM