Sccm direct membership collection not updating
Usually for Collections with Direct membership rule, you really no need to configure any Schedule at all as they are one time created and do not require any update.
so ,you can simply run this SQL Code ,if the count of Direct membership rule is bigger and if any Schedule configured to get the RID of it.
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.
The fix is to make sure that “The Device” in all the collections in the Limiting train.
Cause: Collection Update times are in a reverse time order in the Limiting train.
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.
This script is tested on these platforms by the author. If you try it and find that it works on another platform, please add a note to the script discussion to let others know.
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.
The sample scripts are not supported under any Microsoft standard support program or service.
The sample scripts are provided AS IS without warranty of any kind.