System management patches that write to the registry write to wrong section on Win7x64 devices

Question

I have entered a SR on this but just seeing if everyone else is running into
this on Win7x64 devices.
As an example if i try to deploy remediation of the 'System Management -
Disable Java Update for Java JRE (Disabled)' patch on a Win7x64 device I end
up with EnableJavaUpdate value in the wrong registry area.
HKLM\SOFTWARE\JavaSoft\Java Update\Policy\EnableJavaUpdate
I should say this would disable 64bit java update but not 32bit java update
but if you look in the patch management debug.log you see it is looking in
the Wow6432Node(32bit) key area for detection of this patch.
For this patch to be totally correct and disable updates for 64 and 32 bit
java both of the following values would need to be wrote.
HKLM\SOFTWARE\JavaSoft\Java Update\Policy\EnableJavaUpdate
HKLM\SOFTWARE\Wow6432Node\JavaSoft\Java Update\PolicyEnableJavaUpdate
This disconnect between where values are wrote to the registry and what is
being looked for by patch management seems to hold true for most of the
system management patches I have tried so far on 64bit machines.
Windows Event Application Log shows the following:
Log Name: Application
Source: WSH
Date: 4/19/2012 1:25:16 PM
Event ID: 4
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: JKoerner-LT.internal.reimelt.com
Description:
UPDATE SERVER DEPLOYMENT: Information
INSTALL COMMAND(Key1): RegWrite(HKLM\SOFTWARE\JavaSoft\Java
Update\Policy\EnableJavaUpdate,0,REG_DWORD)
Debug.log section relating to patch:
Opening file:
System Management - Disable Java Update for Java JRE (Disabled).pls
Importing
Filename : [System Management - Disable Java Update for Java JRE
(Disabled).pls]
OS Platform : [Microsoft Windows 7 Professional x64]
Library Build : [5.2.2][Jan 11 2012 17:10:20]
Finished Importing
Detecting
Looking In: [HKEY_LOCAL_MACHINE][SOFTWARE\Wow6432Node\JavaSoft\Java
Update\Policy]
Key NOT found
Finished Detecting
Another example:
Windows Event Application Log entries for the 'System Management - Disable
Adobe Updater for Shockwave Player 10 and 11 (Enabled)' patch
Log Name: Application
Source: WSH
Date: 4/19/2012 1:46:42 PM
Event ID: 4
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: JKoerner-LT.internal.reimelt.com
Description:
UPDATE SERVER DEPLOYMENT: Information
INSTALL COMMAND(Key1): RegWrite(HKLM\Software\Adobe\Shockwave
11\AutoUpdate\,n,REG_SZ)
Log Name: Application
Source: WSH
Date: 4/19/2012 1:46:42 PM
Event ID: 4
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: JKoerner-LT.internal.reimelt.com
Description:
UPDATE SERVER DEPLOYMENT: Information
INSTALL COMMAND(Key2): RegWrite(HKLM\Software\Macromedia\Shockwave
10\AutoUpdate\,n,REG_SZ)
Server - ZCM 11.2 on Win2008R2x64
Clients - ZCM 11.2 on Win7x64
Jim Koerner

Answer 1

To drag up a old thread and SR (gee it has been more than 7 months). Looks
like there is finally some work on this as I got a real preliminary test
file that seems to have fixed this issue but didn't get a timeframe on an
actual release and the SR is still open.
Jim Koerner
"Jim Koerner" wrote in message
news:ZExmr.10001$[email protected]. .
My SR just got pushed along to Lumension. The one thing I am concerned
about is the one example I gave 'System Management - Disable Java Update for
Java JRE (Disabled)' will be the only one fixed. There is a fundamental
flaw in how most of the System Management patches interact with 64-bit
machines. Looking at where registry entries get wrote and what is detected
from the scan I would say there were not even tested on 64bit machines. I
did note my concern in the SR.
Jim Koerner
"Shaun Pond" <[email protected]> wrote in message
news:[email protected]..
> Jim,
>
> no - tell them that I have seen this, it should speed things up for
> you...
>
> --
>
> Shaun Pond
>
>