If you are unfamiliar with this process, please read up before continuing. Each environment will vary on how long it takes to execute this query, and how many members the collection has once it has updated. Client from SMS_R_System inner join SMS_G_System_ADD_REMOVE_PROGRAMS_64 on SMS_G_System_ADD_REMOVE_PROGRAMS_64. Resource Id where SMS_G_System_ADD_REMOVE_PROGRAMS_64. Display Name = "Microsoft Visio Professional 2016" Now if we evaluate collection membership and go back to CEViewer, we can see that the evaluation time has drastically been reduced to well within our artificially defined “threshold”.
Lets say your environment has 10,000 clients and you need to define a collection of systems that have Microsoft Visio Professional 2016 installed. The Collection Evaluator is the Site System component responsible for executing Collection Membership Queries and ultimately keeping your collections up to date. To recap, use CEViewer to keep an eye on your Collection Evaluations.
Like many of you, my SCCM environment contains a rather large number of collections (1000 ).
These collections are used for various purposes from identifying systems with certain Software installed, or identifying systems by Hardware Attributes such as Make, Model or Free Disk Space.
This is my blog where I will share tips and stuff for my own and everyone elses use on Enterprise Mobility and Windows related topics.
For each one of these collections, we have different ways we can populate them with members.
We can use Direct Memberships, Collection Queries, or Collection Include/Exclude rules. Client from SMS_R_System inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS. Resource Id inner join SMS_G_System_ADD_REMOVE_PROGRAMS_64 on SMS_G_System_ADD_REMOVE_PROGRAMS_64. Resource Id where SMS_G_System_ADD_REMOVE_PROGRAMS. Display Name = 'Microsoft Visio Professional 2016' or SMS_G_System_ADD_REMOVE_PROGRAMS_64.
This can be achieved by using a status filter rule together with a VBscript which removes the computer from the collection once the Task Sequence completes successfully.
I have updated the script to search for active computer records in SCCM using the name and then removing the computer from the collection using the Resource ID instead of using the name for matching.