I have many computer collections, the set of operational collections, collections by hardware, collections by operating system, collections for various software, collections on OUs, and some of these collections are collections of collections or depend on other collections.  What is the best way to setup the updates for membership rules?  I see two options: Use incremental updates for this collection and schedule a full update on this collection.  When should one be used and not the other or both at the same time?  Is there some sort of recommended hierarchy for nested collections and what to set incremental vs full updates on?  

I unchecked use incremental updates on a bunch of them and changed them to schedule a full update every one day at 7am because I thought I read somewhere that having all of your collections set to incremental was not a good idea.  My question arises because well when you do an OSD and a computer becomes a member of one collection it will need to suddenly become a member of a bunch of collections so that it can get the necessary software deployed to it.

It all depends on your own requirements and goals, what do you want to achieve? When you know what the outcome should be, you configure the collection updates accordingly. Keep in mind that there's a 200 collection threshold for incremental updates so you wouldn't go beyond that.

Check this link: https://technet.microsoft.com/en-us/library/gg699372.aspx

• Edited by Narcoticoo 3 hours 29 minutes ago

It all depends on your own requirements and goals, what do you want to achieve? When you know what the outcome should be, you configure the collection updates accordingly. Keep in mind that there's a 200 collection threshold for incremental updates so you wouldn't go beyond that.

Check this link: https://technet.microsoft.com/en-us/library/gg699372.aspx

• Edited by Narcoticoo 3 hours 27 minutes ago

I think incremental updates are exactly for your scenario (OSD / quickly getting software).

In early days SCCM didn't have this capability, so Full collection update had to be scheduled to occur very often so that new computers could instantly get necessary software.

So incremental updates are meant so that deployed software could be installed to new computers quickly.

It all depends on your own requirements and goals, what do you want to achieve? When you know what the outcome should be, you configure the collection updates accordingly. Keep in mind that there's a 200 collection threshold for incremental updates so you wouldn't go beyond that.

Check this link: https://technet.microsoft.com/en-us/library/gg699372.aspx

• Edited by Narcoticoo Saturday, August 22, 2015 4:18 AM

I am sure I have read a few statements from people saying the 200 limit was removed in a recent version. Can't find the info now though :(