From the "Inventory and Asset Management" presentation at the 2011 Konference, I pulled this new information (that I can't find in the K1000 manual):
"Support was added for appending a 32 or 64 to the HKEY name as a clear way to know which hives is being used by the registry call. For example we can look for the status of automatic updates on each machine:
\CurrentVersion\WindowsUpdate\Auto Update,AUOptions, TEXT)
32 bit: RegistryValueReturn(HKEY_LOCAL_MACHINE32\SOFTWARE\Microsoft
\Windows\CurrentVersion\WindowsUpdate\Auto Update,AUOptions, TEXT)
64 bit: RegistryValueReturn(HKEY_LOCAL_MACHINE64\SOFTWARE\Microsoft
\Windows\CurrentVersion\WindowsUpdate\Auto Update,AUOptions, TEXT)"
So I have some questions:
- Do these new terms, HKEY_LOCAL_MACHINE64 and HKEY_LOCAL_MACHINE32, work with the 5.1.38724 agent as well as the new 5.3 agents?
- The example shows HKEY_LOCAL_MACHINE64 and HKEY_LOCAL_MACHINE32 being used with the custom inventory field RegistryValueReturn function. Can they also be used in scripting? If so, logically they should work in the Verify section with all "Verify a registry..." steps, and in the other sections with all 5 of the "...registry..." steps. Is this true?
- In scripting, HKLM can be typed in place of HKEY_LOCAL_MACHINE, and the script editor expands it to the longer form. So can HKLM64 be used in place of HKEY_LOCAL_MACHINE64, and HKLM32 be used in place of HKEY_LOCAL_MACHINE32?
- Are other analogous registry keys supported, like HKEY_CURRENT_USER64 and HKEY_CURRENT_USER32? Any others?
Yes, I could learn all this by trial and error, but that would take quite a bit of time. I'm hoping one of the KACE gurus already knows the answers, and will share them! Sande
Hey, Dell KACE: Sure would like to see an answer to this! Other postings have also asked about HKLM64. How about we get all the answers in one place?
There are no answers at this time
so that the conversation will remain readable.