Set the startup type to Delayed Start and then reboot the system after the change.
We tried to get more information from Microsoft Support to better understand the root cause.
For Collections, this is usually due to a high number of scheduled updates taking place together.
By default, the collection update time is the same as the time it was created.
This is just an example, the report can be tweaked to group the results by Company, Solution, or any other grouping criteria.
Here is one example of a simple fix: In the scenario above, clients will now move from “All Systems” to “IBM Laptop Devices” somewhere in the range of 2 hours if added before pm, and as many as 24 hours if added after pm. 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.Here is an example: In the scenario above, let’s say that a new SCCM client is added to SCCM at pm on Monday.It will fall into the “All Systems” collection within 30 minutes, so about pm.