KACE Product Support

We had this problem with some in-house software when trying to do software distribution of newer versions. The cause, for us at least, was left over registry entries. On 5.1 if it found multiple registry entries for the same product, it would show them all in the computer's inventory, but since 5.3, it only picks the first registry entry it comes across in the "Uninstall" registry folder. This causes problems if your programs aren't cleaning up after themselves.

I would check under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and see if there are leftover registry entries for a previous version of Flash in there.

Sorry I didn't go into greater detail. We're in the middle of an AD migration throughout our school district. The thing is, a VAST majority of these machines are brand spanking new installations of Windows pushed down by Windows Deployment Services so there aren't any old applications at all. Clean images, just customized to join our domain after the imagine process is complete. I sent some information to KACE support and as of right now, they don't have a clue what the problem is. They didn't realize version 5.3 of KACE was so buggy.

So your custom rule is used for a smart label applied to a managed install, script, or a patch schedule? We use patching for Adobe products and it detects the need for an approved patch and then deploys it where needed and stops. A managed install doesn't keep trying to install once the software has been detected. Is there a problem with your smart label criteria or is it a script re-installing?

After upgrading to 5.3 two of our three custom inventory rules are working. The working ones are just detecting the OS version and IE version. The one that doesn't work any more is for displaying the local admins from this post:
http://itninja.com/question/silent-uninstall-oracle-8-cilent1192

We're creating software inventory packages and manually populating it with the Display Name, Publisher, and Display Version based on exactly what is in Add/Remove Programs. We then upload the associated install for that software package, MSI, EXE, ZIP. We have a good mixture of all.We then create a custom inventory rule that states to only install if the version of "example.exe" is less than the version we are attempting to install.

Once that is set, we create a Managed Install based on that software package we manually created and we populate it with switches and commands to make sure it installs with no user interaction. After the Managed Install is created, we target it to computer smart labels.

I can send you a screenshot of what exactly is happening if needed.

Here is the response I received from KACE support

Hi Adrian,

From testing this, it doesn't look like you are doing anything wrong. The
"ProductVersionGreaterThan(path, version)' Is not functioning properly. I
suggest using one of these in place of it:

ProductVersionEquals(path, version)
FileInfoGreaterThan(fullpath, attribute, type, value)
FileInfoLessThan(fullpath, attribute, type, value)
FleInfoEquals(fullpath, attribute, type, value)

RegistryKeyExists(registryPath)
RegistryValueEquals(registryPath, valueName, value)
RegistryValueLessThan(registryPath, valueName, value)
RegistryValueGreaterThan(registryPath, valueName, value)

If you can instead. I'm working on a bug number.

Thanks,
Brian