The last group that could cause an issue is collections with an incremental evaluation time.
However, the updates are not being installed at all or during the configured maintenance window.
There are quite a few "nerd knobs" in SCCM and I have been researching on my own, but hoping a fellow Spicehead may notice something I am missing and point me in the right direction.
In a large environment I was in with many, many collections (thousands) I’ve seen it set as high as 90 minutes. If you are seeing issues with your collection updates, take a look at your environment and see if you have any of the issues I’ve listed. Contact Model to set up some time to chat and don’t hesitate to check out our services for a better idea of how we can help you!
In part 2, I go a little deeper, even giving some SQL queries that can be run against the SCCM database to identify these issues, along with a few new ones.
So every 15 minutes, all the normal collection evaluations have to wait.
When there are a large number of Incremental collections, the evaluator is unable to complete the cycle within 15 minutes, so the normal collections just sit there waiting, and waiting.
They factor into almost everything from deployments to client settings, to… It just so happens that collections are a unique breed of things that are easy to understand but difficult to master.
I’ve had (at least) my fair share of collection issues to troubleshoot in both simple and complex SCCM implementations, so I’ve decided to share with you some of the issues I’ve seen and what you can do about them.
The fix is to make sure that “The Device” in all the collections in the Limiting train.