Add a application deployment type "Default" along side "Available" and "Required"
Applications deployed through configuration manger can be configured to be available (in which case, the user must act to install the app, but the user can also remove and install at their convienence) or required (installed and enforced at every deployment reevaluation period).
there is a missing category for applications that should be installed (or removed) without user intervention at a specific deadline time, but that install or removal should not be enforced.
consider an application that is part of the standard software load of the organization, but users are permitted to remove it if they prefer to work without it. In this example, something like security software would be required. Something like a time tracking app would be available if the user acted, but something that is expected on the machine but has no enforcement implications would be default, like a document viewer for a standard company format
if it is packaged as an application, it can either be "required" where the user is not permitted to remove it, or it can be "available" where the user must take action to install it. this new third deployment method would automatically install the application once and only once, and then permit the user to remove (or reinstall) as if it was available.
If the application is superseded, the superseding application should respect the previous removal of the old version of the app, and systems that had the old version should upgrade as normal, but new machines (that never had the old app) should receive the new application as soon as the deployment is received by the client.
In order to achieve this behavior currently, administrators must configure the application as both a application and a package, then advertise the application as available and the package as a deadline install. A single deployment method that encompasses automatic installation without enforcement would reduce this complexity.