The need to detect and prevent downgrades (if desired) is so obviously an engineering logic flaw that resolving this issue should be considered a bug-fix, rather than an enhancement request. This logic-loop is preventing me from using MI for a majority of our distribution needs.

Please consider this suggestion. There are many applications that can be updated by the end user, or that self-update automatically. KACE should be able to determine when a newer version of an application is installed and prevent the MI from running. What happens now is the MI runs, the MSI detects a new version of the software and stops. Next time the machine inventories the process repeats. It drives the users crazy with repeated prompts.

I don't mean to get all snippy, but we decided to give up on KACE after 3 years. It has fantastic potential. I originally thought that it was a great piece of software with some really obvious flaws that would be fixed in time. Unfortunately, nothing has changed in 3 years. The managed installs are a great example. Most software has version numbers. It really shouldn't be that hard to have an option where KACE doesn't mess with upgraded software.

+1000! Even something as simple as a checkbox "Don't downgrade if newer version found". We have a number of software packages that once installed get updated from a different source (SEP for example), and if we have an MI applied to a set of machines it will try to downgrade because the version number doesn't match exactly, usually breaking the install.

Also, we have cases where we need to test a newer version/hotfix/etc. of a piece of software just on a handful of machines, but again the MI will downgrade them on next check-in.

This needs to happen, AD can do it so I don't see any reason Kace can't pull it off. This is my number one complaint about this product.