Issue 432018 in chromium: Unable to programmatically check whether the Google Chrome is 32-bit or 64-bit

36 views
Skip to first unread message

chro...@googlecode.com

unread,
Nov 11, 2014, 1:30:10 AM11/11/14
to chromi...@chromium.org
Status: Unconfirmed
Owner: ----
Labels: Type-Bug Pri-2

New issue 432018 by anton.pa...@gmail.com: Unable to programmatically check
whether the Google Chrome is 32-bit or 64-bit
https://code.google.com/p/chromium/issues/detail?id=432018

Chrome Version : 38.0.2125.111 m
URLs (if applicable) : -
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 6: N/A
Firefox 20: N/A
IE 7/8/9/10: N/A

What steps will reproduce the problem?
1. The browser should include its architecture type (32-bit or 64-bit) in
its version or installation name
2. This mentioned architecture type should be seen on e.g. Programs and
Features, so that it can be reached using e.g. WQL

What is the expected result?
I could reach the architecture type of the Google Chrome using SCCM's query
features.

What happens instead?
The architecture type is not mentioned within the Google Chrome's basic
information which could be queried programmatically.

Please provide any additional information below. Attach a screenshot if
possible.

I posted about this on Google Chrome Help forums and was told to ask for
assist from here.
(https://productforums.google.com/forum/#!category-topic/chrome/report-a-problem-and-get-troubleshooting-help/windows8/Stable/nW7C-c5i5Ck)
Here's the complete post:

I'm deploying Google Chrome (the .msi version of it) using SCCM (System
Center Configuration Manager) 2012. I want to do forced installations to
users who have an existing installation of the Google Chrome. There has
been no problems with this, as I can find the devices which have an
installation of "Google Chrome".

However some of the users are nowadays using Chrome 64-bit and we should
start deploying both 32-bit and 64-bit of the Chrome. 32-bit versions to
existing 32-bit users, 64-bit to 64-bit users. The issue is that I can't
query devices as the Google Chrome doesn't register its type of the product
for what I've found.

I am aware that I can see the type of the Google Chrome from Settings ->
About, but that information can't be queried using e.g. WQL.

If one is not aware of the capabilities SCCM has, I'd explain it like this:
I can find the "Programs and Features" information of the devices. If the
Google Chrome would be named as "Google Chrome (32-bit)" for example, or
the version would be "38.0.2125.111 32-bit", there would be no problems.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

chro...@googlecode.com

unread,
Nov 12, 2014, 1:38:40 AM11/12/14
to chromi...@chromium.org
Updates:
Status: Untriaged
Cc: ashej...@chromium.org
Labels: -Type-Bug Type-Feature Cr-Internals-Installer

Comment #1 on issue 432018 by ashej...@chromium.org: Unable to
programmatically check whether the Google Chrome is 32-bit or 64-bit
https://code.google.com/p/chromium/issues/detail?id=432018

Marking this as a feature request and Untriaged. Feel free to change, if
that is not the case.

Thank you!

chro...@googlecode.com

unread,
Nov 12, 2014, 6:04:55 AM11/12/14
to chromi...@chromium.org

Comment #2 on issue 432018 by anton.pa...@gmail.com: Unable to
programmatically check whether the Google Chrome is 32-bit or 64-bit
https://code.google.com/p/chromium/issues/detail?id=432018

Yes, this would be a feature request. Of course it can't be categorized as
high priority change, but nevertheless it should be a small switch... Well,
hoping to see a change one day.

chro...@googlecode.com

unread,
Nov 12, 2014, 9:50:48 AM11/12/14
to chromi...@chromium.org
Updates:
Labels: Cr-Enterprise

Comment #3 on issue 432018 by g...@chromium.org: Unable to programmatically
check whether the Google Chrome is 32-bit or 64-bit
https://code.google.com/p/chromium/issues/detail?id=432018

Why not deploy 64-bit Chrome to machines that are 64-bit capable, and
32-bit Chrome to those that are not? In other words, why do you care which
type of Chrome is already installed?

chro...@googlecode.com

unread,
Nov 26, 2014, 6:19:15 AM11/26/14
to chromi...@chromium.org

Comment #5 on issue 432018 by anton.pa...@gmail.com: Unable to
programmatically check whether the Google Chrome is 32-bit or 64-bit
https://code.google.com/p/chromium/issues/detail?id=432018

@grt. My original answer would've been we'd like to respect the choices the
users do, whether they want to have 32-bit or 64-bit version of a software.
Well that's kind of the case, but the actual main reason is that the 64-bit
Chrome requires e.g. 64-bit JRE (Java Runtime Environments). We are
currently deploying the 32-bit version of the JRE as requested by the
developers. This would cause more issues again, as the Java, and Oracle
overall, is all but an easy partner on software deployments.
Reply all
Reply to author
Forward
0 new messages