Messages

Thanks.

Yeah, it was new to me too.  The update detected on my machine but failed to the point the program was hosed. (Issue with my machine in particular.) So I had to uninstall, reinstall our base version (2.36) via SCCM, then it wouldn't detect the 2.37 update. Looks like the clean reinstall put everything under Wow6432Node.

KeePass 2.37 is not properly detecting on all of my machines.

What I'm seeing on the problem machines is that the registry keys are different between the Installable Rule and the actual installation.

Installable Rule looks for:

Code Select Expand


HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\KeePassPasswordSafe2_is1


Actual Reg Location on my machine:

Code Select Expand


HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\KeePassPasswordSafe2_is1


Please add the "WOW6432Node" location to both the Installable Rules' and Installed Rules' rulesets.

It is working now.  Thank you.

ZIP file sent.  Note that only "HKLM\SOFTWARE\WOW6432Node\Google" is provided as we only use Chrome (x86) on 64-bit OS.

Yes, the initial install uses the "googlechromestandaloneenterprise.msi" version 55.0.2883.87.  All previous SCUP updates through 57.0.2987.98 detected and installed as expected.

As a test, I rolled a machine back to the 55.0.2883.87 install, and reran detection in SCCM.  57.0.2987.98 detects, but 58.0.3029.96 does not.  Even after installing 57.0.2987.98, 58.0.3029.96 still does not detect.

My SCCM clients are not detecting any of the Google Chrome 58.x.x.x updates.  I see that Installable Rules have changed since the 57.x.x.x updates.  We currently only deploy the x86 version.

There are several "AND" clauses which all have references to one of the following registry strings:

Registry String 'HKLM\SOFTWARE\WOW6432Node\Google\Update\ClientState\{8A69D345-D564-463C-AFF1-A69D9E530F96}\ap' = 'x86-stable'.
Registry String 'HKLM\SOFTWARE\Google\Update\ClientState\{8A69D345-D564-463C-AFF1-A69D9E530F96}\ap' = 'x86-stable'.

The "ap" registry value does not exist in the registry of any of the clients I have checked.