Enter the value you want and search all the resources you want to select.
Once the collection is created only a single resource is a member: A query requires that AD Discovery has updated the group memberships in the database (full or incremental – both will suffice) and once that is completed the collection has to be updated.
The user will not receive any deployments until their kerberos ticket has the AD Security Group membership update reflected.
7.x upgrades are considered minor, and thus less resistant to upgrading/updating.Any deployment i have done on this collection has not reached the machine.I have deleted and recreated the collection and same issue.In the Morning in SCCM 2012, I observed Hour Glass on the collection after adding members for almost 3 hours. Now it is 2 hours and the two machines do not show up when double clicked on the collection. I have directly added two active computers to collection (Right Click on collection Add Resources), with the limited to "all systems".Once the resource is located you can choose to create a new collection and set the limiting collection to “All Users and User Groups”.All updates (full and incremental) can be removed to avoid any type of load. Change the default search for Resource class and Attribute name to User Group Resource and User Group Name. At a minimum it must be longer than the heartbeat frequency of the clients. Note you don't want to set these very short or your client data will be getting deleted due to relatively brief period of inactivity.Quite common (based on all the blog-articles) is to set an Incremental update for all collections that require a fast update.The limit for this is (according to Config Mgr 2012 documentation) roughly 200 collections depending and inaddition the queue will increase with updates.