Independend deployment type
Currently, when creating Application and Application´s deployment types, they are mandatory linked to each other.
In production, we need 2 different deployment types. 1st deployment type would be used on-field computers which require complex uninstall script and 2nd would be independend native setup.exe /silent
Currently, the issue is, that we cannot use independend deployment types in Application model.
Rico Rosenheim commented
Independend deployment types would also fix scenarios where an application have post-install deployment types. Say you have Office 365 as an Application, but also need to install Office Templates and Proofing Tools and these must installed after the main Office install. To day I need to deploy the Office Template application (the last application in the chain) as "Microsoft Office 365 ProPlus". I could create a DT for each application in the Office 365 application, but then I loose the uninstall option in "Software Center".
So, Packages has this functionality that you can setup multiple command lines and use them independently, but not in Application.
If you are already making a script for uninstalling, just make your check in the script, so you can run the required uninstall.
Put those computers in different OUs, create two different deployment types and set each deployment type with a Requirement that computers must be member of the different OUs.