Software Deployment Question
Custom Inventory Rule RegistryValueEquals Not Working on 64-bit Clients
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?