Sccm collections not updating update collection membership
At pm on Tuesday, the client moves into the “Dallas Devices” collection.At pm on Wednesday, the client moves into the “IBM Laptop Devices” collection. The update times are get earlier as we move closer to the “IBM Laptop Devices” collection.Cause: There are too many collections with incremental update cycles.Think of the SCCM collection update process as a line for a ride at Disneyland.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.
By default, the collection update time is the same as the time it was created.
This is a topic I haven’t seen much covered around but is quite important, especially if you’re managing an environment with a lot of clients, regular changes and a lot of collections.
According to Technet ( Collections in System Center 2012 Configuration Manager provide a method of managing groups of computers, mobile devices, users, and other resources in your organization.
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.
Search for sccm collections not updating update collection membership:
The last group that could cause an issue is collections with an incremental evaluation time.