If you are targeting the machine as opposed to the user I wouldn't target all your apps to the same collection.
For a client, I'm using a script to look at the category of the application. If the category of the app is defined in a CSV it creates a collection, sets the refresh schedule, moves it to the right folder, distributes the content, creates the deployment, and sets up the rules based on the category. This could be adapted to your environment pretty easily if the category is the name of the AD security group. I'm planning a blog post on this some day... On Mon, Feb 23, 2015 at 6:29 PM, Robert Spinelli <[email protected]> wrote: > Just trying to figure out how others target using the application model? > I was looking to create a minimal amount of collections and use AD group > membership of the machine as an application requirement but after doing > some research, seems like people are saying that application requirements > shouldn't be used as a targeting method. It can cause performance issue as > all clients would have policies for all applications (ex: 2000 apps) even > if they only need 5 apps. > > Nice long thread/post here: > > > https://social.technet.microsoft.com/Forums/en-US/3a737afa-26e8-4881-9105-a9c42055ca67/how-to-create-a-global-condition-based-on-computersusers-active-directory-group > > If you have 2000 apps for example and have an AD group per app, are you > creating 2000 collections? This is what I used to do for 2007 and 2012 > package model, but thought the benefit of 2012 was less collections. > > Would like to hear what others are doing. > > Rob > >
