Sccm direct membership collection not updating
Note: I set my updates on collections at 30 minutes. I would in no case set this for a real live production collection.
Most aggressive I would typically go for would be 8 hours.
Note that if the group is not in the list them AD group discovery need to be configured in the Administration tab of the SCCM Console (Administration Active Directory Group Discovery): (Back to where we were) Click Ok: Click Ok: Click Ok: Click Ok: Now you can add the devices to the group in Active Directory.
Go back to the device collection in the SCCM console right click and select Update Membership, after a short while this will update, make sure to give AD enough time to replicate though.
Now, with SCCM 2012 we could create a deployment collection and simply include one of the operation collections and voilà. What I mean by that is if your collection targets 500 workstations, you will always target 500 workstations minus or more the workstations that get added as the query gets updated. We would typically create a collection with a query along the lines of Select all objects where the operating system is like “workstation”. When we create the collection/deployment we will be targeting all workstations.
The membership will of course update itself in due course without the manual intervention.
In this post we will be looking at using SCCM dynamic queries to populate collections in our deployments.
Status Type = “1”)[/su_box]Replace XYZ12345 in the above query with your Deployment ID.
Understanding WQL can be a challenge if you never played around with it.