SCCM best practices for collections

User collections should be based on AD user groups. Common scenario is to name group for the name of application which users in specific group use, e.g. APP - Autocad. Then the collection name should be the same as AD group. Thanks for user collections You can deploy software on any computer on which user is or will be working on

Device collections - good practice is to create folders under each You can get collections designed for specific purpose

IsInstalled contain collection based on Configuration Baseline, e.g. PowerShell 3.0_All Windows 7 Computers Active_Compliant
Thanks for this approach You can schedule deployment of specific software to such collections, e.g. App-V 5.0 client needs PowerShell 3.0 as prerequisite so we scheduled App-V deployment for PowerShell 3.0_All Windows 7 Computers Active_Compliant collection. The easiest way to create such collections based on Configuration Baseline is shown below

Another approach to create collection for specific software installed is based on query, below sample for Citrix Reciver 3.4 IsInstalled 

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceId = SMS_R_System.ResourceId where SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName = "Citrix Receiver (Enterprise)" and SMS_G_System_ADD_REMOVE_PROGRAMS.Version = "13.4.0.25"

or for AutoCAD

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_ADD_REMOVE_PROGRAMS_64 on SMS_G_System_ADD_REMOVE_PROGRAMS_64.ResourceId = SMS_R_System.ResourceId where LOWER(SMS_G_System_ADD_REMOVE_PROGRAMS_64.DisplayName) like "AutoCAD%" and SMS_R_System.Obsolete = 0

IsNotInstalled can be based on similar like above examples or another approach is to use rules Include Collections and Exclude Collections

UnwantedSoftware can store collections with software which should be automatically uninstalled when detected, e.g. specific version of Java or torrent software.

You create a package with data source files and associate with it some programs like Uninstall Java Auto Updater which contains:
msiexec /x {4A03706F-666A-4037-7777-5F2748764D10} /qn /norestart

Collection for computers with Java Auto Updater can be based on query like below:

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceId = SMS_R_System.ResourceId where SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName = "Java Auto Updater"

Collection for computers with specific network card:
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_NETWORK_ADAPTER on SMS_G_System_NETWORK_ADAPTER.ResourceId = SMS_R_System.ResourceId where SMS_G_System_NETWORK_ADAPTER.Description = "Intel(R) 82567LM-3 Gigabit Network Connection"

Maintenance - can store another collections which are build on already created (e.g. All Windows 7) in another place but have setup maintenance window

Power Plan - similar like Maintenance folder but have a power management configured, like wakeup time