If you have a requirement for example that says only install on machines with more than 4GB of ram and you deploy it to all users does it show up in the application catalog as being available to run only on machines with more than 4GB’s of ram or does it show for everyone (even those without 4gb of ram) and not install when the user who has less than 4GB of ram actually clicks to install it.
From: [email protected] [mailto:[email protected]] On Behalf Of Ryan Sent: Tuesday, February 24, 2015 1:12 PM To: [email protected] Subject: Re: [mssms] Application Model / Targeting You would have 2000 apps and 2000 deployments. The categories would be named the security group name (or some other identifying feature) and then the script would create the collection with the name Deploy - AppName, and set up a query rule to add a security group. If you want less overhead, it could be changed to use direct membership rules instead. If a collection doesn't have the auto-create variable, it won't create a collection for it. So that's how you would make sure not all apps have collections and deployments. The current variation of the script is for a school district with multiple buildings. Each category is a RBA collection for different buildings since not all buildings are licensed for all software. It creates one master collection and deploys the app to that TS, then creates a number of collections limited to the RBA collections and adds them as include rules to the master collection. So some apps have one deployment but 10 collections. On Tue, Feb 24, 2015 at 11:40 AM, Robert Spinelli <[email protected]> wrote: I’m hoping someday is today, that would be helpful. J If you need someone to help you with testing, you can send me all your code.. hah. This seems interesting, can you expand on rules based on the category? So using my example off 2000 apps, you would have 2000 collections / 2000 deployments right? Nothing in your process would allow me to limit the amount of collections that need to be created, or am I reading this wrong? Thanks Rob From: [email protected] [mailto:[email protected]] On Behalf Of Ryan Sent: Tuesday, February 24, 2015 9:34 AM To: [email protected] Subject: Re: [mssms] Application Model / Targeting 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
