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:
Quote
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.
Did they deploy Chrome using the MSI?
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.
Can you export the "'HKLM\SOFTWARE\WOW6432Node\Google" and "'HKLM\SOFTWARE\Google" and email it via ZIP file using the technical support form?
ZIP file sent. Note that only "HKLM\SOFTWARE\WOW6432Node\Google" is provided as we only use Chrome (x86) on 64-bit OS.
It should be fixed in today's catalog update with Chrome 59.0.3071.86, please let us know if there are any problems :)
Just wanted to follow up here. You still may actually see an issue with the update not showing as applicable. We added a rule to detect when the AP value = multi-version to map to Chrome x86. We are will working on a rules to update Chrome x86 if the AP value doesn't exist at all. We will either revise the Chrome update from yesterday or add it to the next update.
Justin
It is working now. Thank you.