We have 32 bit and 64 bit machines and we have software distributions that have 32 bit versions for the 32 bit machines and 64 bit software versions for the 64 bit machines. Instead of having to switch the packages around 1-2 times a week  I was trying to create a custom inventory rule that looks at the registry and if the folder exists than it is the 64 bit version and if the folder exists in another location than that would be the 32 bit version as the software is in the following locations depending if it is 32 bit or 64 bit.
Win 7 x64
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cisco Systems\VPN Client

Win 7 x86

My custom inventory rule is RegistryFolderExists(HKLM\SOFTWARE\Wow6432Node\Cisco Systems\VPN Client)for the 64 bit version but no 64 bit machines with the Cisco VPN 64 bit version installed are falling under the Custom inventory software rule.

Im running the latest K1000 6.2 version. Can anyone help or tell me what the correct rue is to look for a folder in the registry location or how to have 32 bit and 64 bit version loaded into the Kace distribution section, apparently Kace cant determine the difference between the two

4 Comments   [ - ] Hide Comments


  • I don't think that RegistryFolderExists is a valid custom inventory rule.
  • The way I have seen this implemented, even though I have not done it myself, is to use VB or batch file for the install and package both 64 and 32 bit programs in the software as a zip. Then the VB or batch file checks if the folder Program Files (x86) exists. If it does then install 64 bit. If not then install 32 bit.
  • You need to use
    RegistryKeyExists(registryPath) for the registry
    DirectoryExists(path) for the file structure
  • Take out the wow6432node in the reg key since the kace agent is 32-bit.
Please log in to comment

Answer this question or Comment on this question for clarity


This is because:
Does not exist from a 32 bit perspective.
To verify, on a 64bit os, go to start -> run -> \windows\SysWOW64\regedit.exe
Answered 10/21/2014 by: briancollins
White Belt

Please log in to comment
I've run into this in the past and it is because the KACE agent is a 32bit program.  If you want to access the 64bit part of the registry, you have to do it like this.

RegistryFolderExists(HKLM64\SOFTWARE\Wow6432Node\Cisco Systems\VPN Client)

I've had this come up in other places where I've had to use the sysnative flag, but I can't remember off the top of my head.

If you run into other problems like this, hopefully this gives you a head start.
Answered 10/28/2014 by: johnbags401
Senior White Belt

Please log in to comment