Allow Superseding / Upgrade of app or program not installed via SCCM
It would be great if an supersedence could be created for programs not deployed via SCCM (or previously deployed via packages). I find myself creating "dummy" applications just for a detection, so that we can automatically upgrade applications that are "Available". In other words, often times we don't care that you installed a specific program, but we do care that if it is installed it's up to date. Maybe when selecting the Application and Deployment type to supersede an additional option to supersede base on a detection rule set could be added?
Justin Hoover commented
I agree, this would be very helpful!