The way we would like to set it up here is that the users would only see the apps they need for their business function. We have 2000 apps or so, If I’m a secretary I should only be able to see the 10 I need and install them from application catalog. Don’t want them to see the 1990 apps they have no use for.
Thanks for the input, gives me something to think about. From: [email protected] [mailto:[email protected]] On Behalf Of Sean Pomeroy Sent: Monday, February 23, 2015 7:37 PM To: [email protected] Subject: Re: [mssms] Application Model / Targeting For licensed applications we use AD groups tied to collections for the users and UDA to only deploy to the users primary machine. For license free applications we just deploy as available to the all users collection and they use the application catalog. On Mon, Feb 23, 2015, 7:30 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
