Separate content within the application model
Right now, the application is definitely decent and getting better. A major improvement over some other products within the same space. I do however, think that content assignment should be waaaaay better with this simple change.
Applications have Deployment Types, and DeploymentTypes may or may not have content associated with them. If you create two Deployment Types that share the same content, it is confusing because the content appears as if it is separate (Based on the Content ID), although it is the same (Because of the way SCCM handles content > Single Instance File Storage)
I think it should work more like this
Application (You can create 1 application)
Deployment Type (You can create one or more deployment types)
Content (You should be able to specify 1 or more source locations here, and be able to optionally specify destination folder name that would be created under C:\Windows\CCMCache\2B\FolderName, otherwise it gets stored in the root)
Content assignment (You should be able to specify from within the deployment type, which content you want to use for a given action, with a checkbox that says "Use the same content for all actions")
Secondly, allow global conditions to be "Local Conditions" that can specified on a per application/deployment type basis.
Thirdly, make a built-in global condition that says Task Sequence Only, that can True or False.
Lastly, It seems that when deploying an application with two deployment types within a task sequence, it fails to download the content and never tries to even install the application.
I would like to be able to create one application with one set of content, that can be deployed to bare metal systems during a task sequence. The other scenario is deploying the application to systems already in the field with other specific requirements. We have put this together in our current environment, but it always fails during a task sequence with prejudice. Machines in the field always succeed.