Let’s understand more about SCCM Collection Incremental updates not Working because of non Supported WMI Classes. There are a set of WMI classes that are not supported with SCCM collection incremental updates. Let’s check what the not supported SCCM collection incremental updates WMI classes are?
Let’s understand what is the best practice while creating collections. You should not enable incremental updates for all the collections in your SCCM (ConfigMgr) hierarchy. A high number of collections with incremental updates can cause performance issues for the entire Configuration Manager infrastructure.
There are tools within the admin console that can help you analyze the evaluation cycle of collections. One of them is explained ConfigMgr Collection Full Incremental Evaluation Status Summary from Console in the post.
SCCM Collection Incremental updates
An incremental update periodically evaluates new resources and then adds resources that qualify to this collection. This option doesn’t require you to schedule a full update for this collection.
There was an option to have incremental updates during my initial days of device management with SMS 2003 and I think with SCCM 2007. The incremental update for collections got introduced in ConfigMgr 2012 onwards. Let me know whether this is accurate information or not in the comments.
Incremental updates of the SCCM collection are handy to reduce the full collection evaluations for many collections. Full evaluation of collection is more costly in terms of performance. However, an incremental update of collections is just a “delta update” of the collection.
How to Find WMI Classes from ConfigMgr Server
WMI is Windows Management Instrumentation, a sort of database where information is stored locally on Windows devices. You can use the WBEMTEST tool from any Windows device to find out the WMI classes that are supported by SCCM.
The easiest way is to download WMI Explorer Tool from Vinay Pamnani and browse through the WMI classes and more. I have a more detailed post on Windows 10 WMI Explorer Details for Configuration Manager and Intune.
SCCM Collection Incremental updates not Working
Let’s understand why incremental updates not working because of non Supported WMI Classes used in WQL queries.
The following are the Microsoft documented WMI classes that won’t support incremental updates of the collections. Some WMI classes are only applicable to dynamic user collections.
If you use the following WMI classes inside the WQL query for dynamic collection, then the incremental update of those dynamic collections won’t work as expected.
The following table of WMI classes is not supported to use along with incremental collection updates. These are applicable for a generic set of collections.
|WMI Classes Not Supported for SCCM Collection Incremental Updates|
The following two WMI classes are not supported for SCCM dynamic user collections.
|User Collection – WMI Classes Not Supported for SCCM Collection Incremental Updates|
|SMS_G_User_DCMDeploymentCompliantAssetDetails (for collections of users only)|
|SMS_G_User_DCMDeploymentNonCompliantAssetDetails (for collections of users only)|
- SCCM Dynamic Collection – Part 2 | WQL Query | ConfigMgr | Create
- SCCM Query All Active Directory Security Groups Dynamic Collection
Anoop C Nair is Microsoft MVP! He is a Device Management Admin with more than 20 years of experience (calculation done in 2021) in IT. He is Blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. He writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc.