Software Deployment Question

Custom Inventory Rule RegistryValueEquals Not Working on 64-bit Clients

06/23/2015 3368 views

Some time ago KACE had an issue where 64-bit clients would not return registry values from Custom Inventory Rules. The workaround consisted of adding a 64 after HKLM in the registry path; so you would use HKLM64 if you wanted to query the non Wow6432Node on 64-bit clients. This is no longer working for me and I think this stopped working when the latest KBOX patch was applied.

Here is the Custom Inventory Rule I am using to detect whether a client is running Autodesk Inventor with a network license:

RegistryValueEquals(HKLM64\SOFTWARE\Autodesk\Inventor\RegistryVersion19.0,LicenseMode,1) OR RegistryValueEquals(HKLM\SOFTWARE\Autodesk\Inventor\RegistryVersion19.0,LicenseMode,1)

Testing this on a 32-bit client returns the intended result and correctly detects if the registry key is set to 1. Testing on a 64-bit client acts as though no registry key exists. I had our KBOX admin contact KACE and the only response received was a link to the old article about the HKLM64 path workaround I shared above; and is exactly what I am already doing and have done for a number of other items.

Does anyone know how to get this working? Has anyone else been experiencing this since the last KBOX patch?

2 Comments   [ + ] Show comments


  • I have had exactly the same issue with detecting registry entries ever since out upgrade to 6.3, custom detection rules that previously worked just stopped. My KACE box can't see anything in the registry on windows x64 clients at all
  • Sorry to hear that Andy. There has been no change and I am finding a number of other KACE issues since posting this. I resorted to alternate scripting methods and creating two software packages per software product, x86 and x64 since KACE support has done nothing to resolve this yet. They are aware of the problem.

Community Chosen Answer

I have heard that with the latest 6.3.314 client, 64 Bit registry is not working properly. I have seen some say it works for them and others say it is totally broken. One person said that support had confirmed there was an issue. I am still looking into the issue myself.
Answered 06/30/2015 by: gerane
Yellow Belt

All Answers

What if you try: HKEY_LOCAL_MACHINE64? That's what I'm using. Also - leading spaces or returns will cause the rule to fail as well.
Answered 06/23/2015 by: jegolf
Red Belt

  • I did try that, and made sure there are no spaces. Unfortunately using HKEY_LOCAL_MACHINE64 made no difference for me. I even tried it again after your comment in case something magically changed since the last attempt. No solution yet.
This may be a dumb query, but I will ask it anyway: Does the value on 64bit machines exist in the Software\Wow6432Node\RestofRegistryKeyPath?
Answered 06/24/2015 by: jfrank
Blue Belt

  • Unfortunately not in this case. I am about ready to give up and create a key there and manually add it to the clients; but I shouldn't have to do something like that for the KACE product to do what it is supposed to do already. Am I the only person having this issue? It definitely worked until recently.

Don't be a Stranger!

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

Sign up! or login


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