I am attempting to remediate a registry Configuration Item that is associated with a 32-bit application. Here is an example of what I want the registry to look like:
Setting type: Registry value Data type: Integer Hive Name: HKEY_LOCAL_MACHINE Key Name: SOFTWARE\Example Company\Example Application Value Name: ExampleSetting I did not check the box for "This registry value is associated with a 64-bit application". For the Compliance Rule, I specified that the setting should equal 0. I checked the box to remediate noncompliant rules. For Application Detection, I chose "Always assume application is installed". I put this CI into a Baseline and deployed it to a test collection with two computers: one is 32-bit Windows 7, the other is 64-bit Windows 7. Everything looks great on 32-bit Windows. Remediation works as expected. On 64-bit Windows, the desired registry value is in the Wow6432Node path. If the computer is already compliant, everything is fine. But if the registry value does not exist, or it exists and it is wrong (not equal to 0), things get crazy. Instead of creating or updating the registry value I specified, a new value is created at the following path: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Example Company\wow6432node\Example Application\ExampleSetting The remediation step created the second "wow6432node" key. The created value is a REG_QWORD instead of a REG_DWORD, too. Does anyone know if this is a bug, or if I misconfigured something? Thanks, William
