Sccm queries not updating

In our environment, we removed the default recurring schedules from about 1750 device collections that use Direct membership rules.

Up until that point, we had seen some strange collection behaviors, but never at the level that we began to experience them post Config Mgr 1810.

If you are using SCCM 1602 or below, follow Now that our classes are enabled, trigger a Machine Policy Retrieval & Evaluation Cycle (to have the latest Client Settings) followed by an Hardware inventory Cycle on a computer that has Office installed.

sccm queries not updating-32

Since it updated everything, Test2 was also added to Child 2 and 3. For our environment, since we have need to add devices to collections during OSD, we have removed Incremental from all limiting collections and added recurring schedules instead.

We are testing performance with the changes, but currently have our All Workstations collection scheduled to refresh every 30 minutes and it takes ~12 minutes for a full update to process through all collections. Also, let me be clear, do what’s best for your environment.

Based in Montreal, Canada, Senior Microsoft SCCM Consultant, 5 times Enterprise Mobility MVP. His specialization is designing, deploying and configuring SCCM, mass deployment of Windows operating systems, Office 365 and Intunes deployments.

About a month ago, I wrote a post for System Center Dudes related to the changes to recurring collection schedules in SCCM 1810.

It is used as the limiting collection for all of our workstation application deployment collections (Child 2 in the example below).

For testing, we added a few additional collections to compare the experience.On the Choose Target Collections step, click Add then select all 3 Child collections then accept the remaining defaults. DON’T manually update ANY collection at this stage or you will corrupt the test.You can monitor and should see the collection ID of your limiting collection added to the Graph for processing. This is the time that the new device was imported and the direct membership rules were created.SCCM 1606 introduces new hardware inventory classes for Office 365 configurations.You no longer need to edit your MOF files to gather Office 365 inventory.Once the incremental evaluation has added the new device to All Systems, check the limiting collection (Parent – Incremental) to verify that the device is now a member of it as well. The Membership Change Time on the full chain from All Systems to Child 1 were all updated as part of the incremental refresh cycle, but Child 2 & 3 did not see any membership changes.

Tags: , ,