By linking applications to security groups, you can move software deployment tasks to Active Directory.
This will save time as you do not have to jump between MMCs as often, and you can easily delegate app management.
Linking security groups to SCCM deployments will give your environment flexibility with application installations.
There are quite a few different ways to setup Device Collections.
I am going to focus on creating a collection based on OU's in Active Directory which in my opinion is one of the best ways to manage device collections long term as long as the device has the client installed on it.
Head back to the Configuration Manager console and navigate to Assets and Compliance/Device Collections. For standardization, name your new collection the same as your security group. In the screenshot below, my APP_Adobe Flash Player collection is limited to All Desktop and Server Clients: Create Device Collection Wizard On the Membership Rules page, select Add Rule – Query Rule. Because you likely won’t have multiple query rules, you don’t need to get very specific with the name.
Under Edit Query Statement, select Criteria and Add (star button), and then press Select.
He is a Microsoft Most Valuable Professional (MVP) in Cloud and Datacenter Management and blogs at Deploy It is a software deploying, application packing, OS installing, and cappuccino making machine (currently in testing, expected in System Center 2015).
This complexity can make it difficult to use, especially when you just want to deploy an application.You will be presented with all of the available OU's in your Active Directory structure.In the case of this lab we only have Domain Controllers and Servers (manually created).I also added a Power Shell script that helps create AD group-based SCCM collections.Joseph Moody is a network admin for a public school system and helps manage 5,500 PCs.For easy reference, I like to prefix any application deployment group with APP_ .