This blog is owned and operated by the ANZ ConfigMgr Premier Field Engineer team.
Ian BartlettMatt ShadboltGeorge Smpyrakis
Dynamic Collection Updates and Delta Discovery were features introduced in SCCM 2007 R3 and promised a lot. Finally, admins thought they could limit their full Collection updates to 1 per day, their AD System Group Discovery to 1 per day and use the Dynamic Updates/Delta Discovery to run every 5 minutes to pick up changes. Problem is, Dynamic Collection Updates/Delta Discovery do not work as we had hoped. In the end, Dynamic Collection Updates only worked on *newly* discovered systems… whether that’s a first time AD System Discover, OSD or manual client install. And hey, that’s great if your doing OSD!
If you want your Advertisements to be available as soon as a machine has been built, then Dynamic Collection Updates are for you. But for alleviating the need to run your collection schedules every 15 minutes (against MS Best Practice) for software distribution, Dynamic Updates didn’t hit the mark.
I’m happy to say that ConfigMgr 2012 now does Dynamic Updates and Delta Discovery in the way we had all hoped!
And here’s the proof.
Firstly, lets look at enabling CM12 Delta Discovery, creating a new group, adding a computer to the group and letting ConfigMgr 2012 do its thing:
CM12 AD Group Discovery Settings
SCCM 2007 AD System Group Discovery Settings
Before Delta Discovery is run:
SELECT * FROM v_R_System_SystemGroupName
From the Computer Object in SCCM
After Delta Discovery is run:
And for final proof – the adsgdis.log
So that’s great news! The Delta Discovery now works with System Group membership!
One last thing we need to check – whether or not the Dynamic Collection Membership now picks up changes to existing machines… not just new objects created by DDRs. To check this, we’re going to create a Collection with a membership query looking for an AD group. If all goes well, within MAX 10 minutes, the computer should become a member of the new Collection.
This time, we’re going to watch two logs – adsgdis.log and colleval.log and we should see the updates pretty soon.
And now, within about 6 minutes we can see the Collection is now populated with the object!
Is it true that you cannot have more then 200 collections with the dynamic update feature?
See Best practices for collections
the Threshold for incremental updates is 200 dependant on
The total number of collections
The frequency of new resources being added and changed in the hierarchy
The number of clients in your hierarchy
The complexity of collection membership rules in your hierarchy