Add Options to Deployment Type (Application Model) or Deployment to Allow Filtering
When deploying an application to a user based collection (or computer for that matter), it would be nice to be able to filter the deployment based on criteria such as operating system WITHOUT the need to create a second application. Similar to how the requirements section of the application model works but deployment specific.
Proposed Solution 1
Create a requirements or filter for deployments similar to how filters work on group policy objects. Essentially you would be given the option during a deployment to filter the installation – so if those requirements aren’t met the deployment doesn’t take place.
The real downside I see to this solution is additional strain on the workstation for whatever query language is used to determine applicability. This could somewhat be mitigated to limiting requirement/filter scanning to only deployments that utilize a filter.
Proposed Solution 2
Create a flag for application deployment types that either:
1.Limits the type of collections that a deployment type can be deployed to “Machine Only, User Only, or Both” similar to how the OSD advertisement works for PXE, Boot Media, Local Client, or,
2.Limits the type of deployment that is allowed “Only via Task Sequence Step, Only via Collection Deployment, or Both”
The downside to this method is it seems like there would be a great deal of re-architecting across multiple teams to make this work and limits what can and can't be done with filtering, whereas it seems like a good deal of filtering would be covered by the already existing application ‘requirements’ model – just expanded to the deployment model.