ConfigMgr Collections: Dos and Don’ts

Collections are very important in ConfigMgr, though there are some limits. We will explore some of those limits and I will provide some PowerShell commands to help you.

Collection Limits

First, there is a limit to the number of collections that you have. It’s dependent on the resources that you allocate to your SQL server. The more resources, the more collections you can have. Remember that for every collection you create, two corresponding views are created in the database. This can make your database very large and can consume a lot of resources.

Collection Updates

Second, collection updates is the most resource intensive process that ConfigMgr performs. You should really think about whether or not you need incremental updates turned on and how often your collections reevaluate their membership. You should come up with a strategy as to what collections need both of these options.

To determine which collections have incremental updates enabled, run this PowerShell command (be sure to input the primary site server name and site code where indicated):

 (get-wmiobject -computername <primary site server” -namespace root\sms\site_<site code> -class SMS_Collection | where-object -filterscript {$_.RefreshType -eq “4” -or $_.RefreshType -eq “6”}).Name

Continue reading more here https://www.windowsmanagementexperts.com/configmgr-collections-dos-and-donts/configmgr-collections-dos-and-donts.htm