Mbee,
Basically, if 64-bit software (or a 64-bit process) is what wrote the registry keys/values, then they'll be under the default HKLM, HKCU, HKU hives on a 64-bit Windows OS. If, however, it was 32-bit software (or a 32-bit process) that wrote the registry keys/values, then they'll be under the WOW64 (32-bit) sub-keys (i.e. HKLMSOFTWAREWow6432Node; HKCUSoftwareWow6432Node; etc.) on a 64-bit Windows OS. In my experience, you'll see this more under the HKLM hive than under the user-level hives (HKCU & HKU).
And if you don't know what bitness created/wrote to the registry, you'll just have to look in both places to see where they are located. Worst case, you can always code for both as a catch-all. However, I usually find out where they are actually located and code accordingly.
You can read more about this here:
Scripting, Migrating and Managing Registry Data In 64-bit Windows, by Darwin Sanoy (March 3, 2011) [CSI-Windows]
And, you can find a comprehensive reference of what all is involved (including redirections) here:
WOW64 - A Comprehensive Reference, by Darwin Sanoy (November 18, 2013) [CSI-Windows]
dachammer,
You need to include the /i switch before you provide the MSI folderpath, like this:
ShellExecute("msiexec.exe", "/i " & @ScriptDir & "\KeyViewComponent1080.msi /qb /l*v C:\sccm\msi_logs\KeyViewComponent1080.log")
You might even need to include quotes around your MSI folderpath if there are spaces in the folder path.
