Custom Inventory Rule doesn't seem to be working

Do I have a glaringly obvious syntax error here? I'm not sure why this isn't working. Any help would be greatly appreciated.

FileVersionGreaterThan(C:\Program Files\Common Files\Microsoft Shared\ClickToRun\OfficeClickToRun.exe,16) AND RegistryValueEquals(HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration, SharedComputerLicensing,1) AND RegistryValueEquals(HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration, Platform,x86)

EDIT: Here's what is showing up in the KAgent.txt file in the logs:
[2018-05-31.11:09:00][KDeploy:CDeployController::Execu] rule ID [55592] : issuing rule [FileVersionGreaterThan(C:\Program Files\Common Files\Microsoft Shared\ClickToRun\OfficeClickToRun.exe, 16) AND

RegistryValueEquals(HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration, SharedComputerLicensing, 1) AND

RegistryValueEquals(HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration, Platform, x86);]
[2018-05-31.11:09:00][KDeploy:CDeployController::Execu] rule [55592] statement result: "", FALSE

EDIT 2: I expect this custom inventory rule to return "true", as in, "This software is installed" but it is not returning true. I'm using this in a managed installation, so once the software is installed it should show up in these three places. I have checked each rule manually and confirmed that each one evaluates to true, and I have even used each one individually instead of all three together, and they still don't work.

5 Comments   [ + ] Show comments
  • What do you expect it to return ? - AbhayR 3 years ago
    • True. The software is installed, and those keys/values/files exist if you look manually. - pbrandvold 3 years ago
  • What are you expecting to validate here?

    The syntax looks OK, How do you know is not working? - Channeler 3 years ago
    • I updated the question to reflect what I expect and why I know it's not working. - pbrandvold 3 years ago
  • All the queries are BOOLEAN (yes or no), so the result is only a count in the software item (for how many devices this is true) and you can check it in the software item directly (or a report querying this item)
    This will trigger no entry in the Custom Inventory section. - Nico_K 3 years ago
  • Try using HKLM instead of the full Hkey_local etc - Hobbsy 3 years ago
    • Mmmmmm , he may want to check this as well

      https://support.quest.com/kace-systems-management-appliance/kb/118892/scripts-or-custom-inventory-rules-not-running-as-expected-on-x64-64-bit-clients - Channeler 3 years ago
      • This did the trick. - pbrandvold 3 years ago
      • This article helped me to sort my issue as well. - cbosi 1 year ago
  • I've had an open ticket for a few months now, as I have some CI rules that are just not populating the inventory of some systems. Hopefully I'll get it resolved, and I'll report back here of any resolution. - RD94 3 years ago

Answers (1)

Answer Summary:
Posted by: pbrandvold 3 years ago
Orange Belt

Top Answer

@channeler had it right. Following the instructions at this link resolved my problem immediately:

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

View more:


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ