Software Deployment Question

Google Chrome 64 bit detection method

10/27/2015 9997 views
I am trying to deploy 64-bit chrome over top of 32-bit chrome via SCCM 2012.  As far as i have been able to tell, there is absolutely no difference in the file structure or the details of chrome.exe.  I need to find a detection method for the 64-bit chrome.  Anyone run into this?
Answer Summary:
0 Comments   [ + ] Show comments


Answer Chosen by the Author


You can set detection to chrome.exe with size KB.  
Also nacl64.exe and nacl_irt_x86_32.nexe for 32 bit version is located in installation directory. 
But these 2 files are not located in installation directory for 64-bit package. 

Answered 10/28/2015 by: zigurds.kreslins
Senior Yellow Belt

  • I went the size route. Thanks for the thought.

All Answers

I don't think you can run both at the same time.  Some quick Googling shows that the only way to run both archs of Chrome is to install the Canary version, the unstable developer version, which can run alongside stable Chrome: https://www.google.com/chrome/browser/canary.html

Or did I misunderstand the nature of your question?
Answered 10/27/2015 by: nheyne
Red Belt

  • The 64 bit will be replacing the 32 version.
I am not sure what the detection method would be for 32bit to 64bit.  In this case, I would perform an upgrade from retail version to enterprise versioning.  If you downloaded the latest version (I have made a posting on ITNinja about how to successfully download Chrome without additional garbage in the MSI), this would have the latest MSI version GUID.  SCCM has the capabilities of upgrading in place.
Create a Device Google Chrome Upgrade collection and create an upgrade query that has the following in it,
select RS.ResourceID,RS.ResourceType,RS.Name,RS.SMSUniqueIdentifier,RS.ResourceDomainORWorkgroup,RS.Client from SMS_R_System as RS inner join SMS_G_System_ADD_REMOVE_PROGRAMS as ARP on ARP.ResourceID = RS.ResourceId where ARP.DisplayName = "Google Chrome" and ARP.Version < "66.77.16449"

Place all (applicable) devices (like All Managed Workstations) in collection, don't place them in the Membership rules
Set collection to required. and schedule full updates no less than 7 days.  Leave incremental updates off.
As the devices are picked up by the server as having less than the ARP.Version, it will upgrade them to your version.  
Or you can use Compliance function in SCCM, I am just learning this myself.

Others might suggest using GPO for deploying Chrome over the top.
Answered 10/27/2015 by: Tempril
Purple Belt

  • We are already on the enterprise version for the 32 bit version.
The 2 products will have different ProductCodes in the registry. Find the 64-bit version's GUID and retrieve a value from that branch, e.g. 'ProductVersion'.
Answered 10/28/2015 by: anonymous_9363
Red Belt

  • when I compared the two, they have the same GUID in the registry. They also install to the same folder
>same path
Well, you're installing the same product, then. If it were a true 64-bit Installer, it wouldn't be writing its metadata to the 64-bit path and vice-versa.
Answered 10/29/2015 by: anonymous_9363
Red Belt

  • It is the 64 bit installer, if it is a true 64 bit installer or not is not really up to me.

Well, you can do a detection method by the ProductID within the Application of SCCM. If you have some issues with discovering by ProductID, please be sure you got the correct ProductID. Sometimes the registery is misleading!

I got a VBS script which shows you all installed ProductID's on a laptop/computer. You can run it with cscript in a Command Prompt. You can also write the output to an TXT file.

Make an VBS file on a computer/laptop where Chrome is installed. Run the script and it will list all the ProductID's. The script simulates the ProductID detection by SCCM 2012. This is the script:

Set objInstaller = CreateObject("WindowsInstaller.Installer")
i = 0
    set Products = objInstaller.products

For Each Product In Products
    i = i + 1
    Productname = objInstaller.ProductInfo(Product, "ProductName")
    wscript.echo i & vbTab & objInstaller.ProductInfo(product, "ProductName")
    GetProductCode ProductName

Function GetProductCode(ProdName)

    If objInstaller.ProductState(ProdName) <> msiInstallStateUnknown Then
        For Each productCode In objInstaller.Products
            If LCase(productName) = LCase(objInstaller.ProductInfo(productCode, "ProductName")) Then
            GetProductCode = productCode
            wscript.echo vbTab & GetProductCode
    End If
        wscript.echo vbTab & "NOT FOUND"
    End If

End Function
Paste it in a Notepad file and save as a .vbs file. Run it, enjoy!

( cscript.exe ListInstalledMSIProductIDs.vbs > test1.txt )


Answered 10/29/2015 by: Markje678
Senior White Belt

>same GUID in the registry
...but different paths! The 32-bit flavour will be in 'HKLM\Software\Wow6432Node\Microsoft...'
Answered 10/28/2015 by: anonymous_9363
Red Belt

  • same registry path as well.
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ