I have a compliance setting that I am trying to set up that will modify\create (with Remediation) a registry setting, in HKEY_LOCAL_MACHINE, the following location:

x86: SOFTWARE\SAP\SAPGUI Front\SAP Frontend Server\Administration
x64: SOFTWARE\WOW6432Node\SAP\SAPGUI Front\SAP Frontend Server\Administration



When I deploy it, it goes fine on x86 machines, but on 64 bit machines it does not re-direct to the Wow6432Node.  I have tried checking the "This registry Value is associated with a 64-bit appliaction." However, I get the same results, it creates the registry in HKLM\Software on x64, and not HKLM\Software\Wow6432Node.  What am I doing wrong?  Can I not have a single CI run check\modify\create on both x64 and x86 machines?

if you have 32bit application installed on 64 bit machine enable the checkbox that says " this registry value is associated with 64 bit application" and just check for SOFTWARE\SAP\SAPGUI Front\SAP Frontend Server\Administration and NOT SOFTWARE\WOW6432Node\SAP\SAPGUI Front\SAP Frontend Server\Administration



Read this should answer all your question:

http://blog.configmgrftw.com/configmgr-2012-and-32-bit-application-installers/

Actually, that's backwards as its not a 64-bit application, it's a 32-bit application -- that's why it creates its key and values under the WOW6432Node key in the registry. Thus, you need to leave the checkbox unchecked.

Okay, I am only checking for "SOFTWARE\SAP\SAPGUI Front\SAP Frontend Server\Administration", and I have the box check for "This Registry value is associated with a 64-bit application.

However, It still adding it to HKLM\SOFTWARE\SAP\SAPGUI Front\SAP Frontend Server\Administration and not to "HKLM\SOFTWARE\WOW6432Node\SAP\SAPGUI Front\SAP Frontend Server\Administration"

Under Report I see this:

As mentioned, don't check this box. The application is *not* a 64-bit application which is what the checkbox is for.

So I re-ran with out the check box, and it worked on my test x86 computers, however x64 computers it is still not working.  On my Windows 8.1 x64 machines if the registry setting does not exists, it will create it incorrectly at HKLM\SOFTWARE\SAP\SAPGUI Front\SAP Frontend Server\Administration, instead of correctly placing it at  HKLM\SOFTWARE\WOW6432Node\SAP\SAPGUI Front\SAP Frontend Server\Administration.  Now however, if that key exists, it will update in the Wow6432Node, if it is not compliant, or leave it as is, if it is already complaint.

• Edited by Evers_mark 14 hours 26 minutes ago

Key or value already exists?

To be clear, for the settings above, ShowAdditionalInfo is a value whereas Administration is a key. Just want to be exact here.

Sorry, where the value already exists.

If the value doesn't exist at all, will it create it (just not under Wow6432Node)? I ask this because I thinks its by design that it won't create values at all, only update them if they already exist and are incorrect.

That is correct.  If the value does not exists it will create it, just not under Wow6432Node.

Honestly, I think this a combination of "by-design" and bug. You should file this as a bug on connect (or open a case with CSS). In the meantime, a simple script will get the job done also.

I will definitely submit a bug report.  

Out of curiosity I made a change, I modified the original and set it to only run on x86 machines.  I copied the original, and set the new one to only run on x64 computers, I changed Key, which I set to "SOFTWARE\WOW6432Node\SAP\SAPGUI Front\SAP Frontend Server\Administration", and checked the "This Registry value is associated with a 64-bit application.  I created a baseline with both the x86 and x64 version and deployed that to my test machines.  It now creates the value if not there on all computers, and corrects it if needed.

• Edited by Evers_mark 11 hours 54 minutes ago