Issue 471905 in chromium: Is option NOGOOGLEUPDATEPING=1 still supported for MSI installer?

[chro...@googlecode.com]

Status: Untriaged
Owner: ----
Labels: Type-Bug Pri-2 Cr-Internals-Installer OS-Windows Hotlist-Enterprise
Cr-Enterprise

New issue 471905 by s...@chromium.org: Is option NOGOOGLEUPDATEPING=1 still
supported for MSI installer?
https://code.google.com/p/chromium/issues/detail?id=471905

Version: M31, M41
OS: Windows

What steps will reproduce the problem?
1. Download Chrome MSI from: https://www.google.com/work/chrome/browser/
2. Run command 'msiexec /i GoogleChromeStandaloneEnterprise.msi
NOGOOGLEUPDATEPING=1 /l*v log.txt'
3. Installer is stuck there. From router, I can see it tries to contact
Google server.

What is the expected output? What do you see instead?

1. Per https://www.chromium.org/administrators/common-problems-and-solutions

Appending 'NOGOOGLEUPDATEPING=1' to MSI command will instruct the installer
to not contact google update server. However, per tests above, it still
does so.

2. Doing a code search on https://code.google.com/p/chromium/codesearch#/,
it returns no result for 'NOGOOGLEUPDATEPING', which makes me wondering
whether this option is still supported.

Can you clarify:
- Whether option 'NOGOOGLEUPDATEPING=1' to MSI installer is still supported?
- If yes, how to explain the behavior of test above?
- If not, we need to revise articles to correct the outdated information.
Here's some links for our records:
* https://support.google.com/chrome/a/answer/1628156?hl=en
* https://www.chromium.org/administrators/common-problems-and-solutions
* https://support.google.com/chrome/a/answer/3204698?hl=en


--
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]

Updates:
Cc: lafo...@chromium.org

Comment #1 on issue 471905 by roy...@chromium.org: Is option

NOGOOGLEUPDATEPING=1 still supported for MSI installer?
https://code.google.com/p/chromium/issues/detail?id=471905

(No comment was entered for this change.)

[chro...@googlecode.com]

Comment #2 on issue 471905 by s...@chromium.org: Is option

NOGOOGLEUPDATEPING=1 still supported for MSI installer?
https://code.google.com/p/chromium/issues/detail?id=471905

FYI:

In my testing lab, I dropped all outgoing traffic from windows sandbox to
Google network blocks defined by 'dig +short -t txt _spf.google.com'.

[chro...@googlecode.com]

Comment #4 on issue 471905 by s...@chromium.org: Is option

NOGOOGLEUPDATEPING=1 still supported for MSI installer?
https://code.google.com/p/chromium/issues/detail?id=471905

Reference bug:

crbug.com/80567
Chrome Business installer fails when GoogleUpdater has no internet
connection

[chro...@googlecode.com]

Updates:
Cc: so...@chromium.org g...@chromium.org

Comment #5 on issue 471905 by s...@chromium.org: Is option

NOGOOGLEUPDATEPING=1 still supported for MSI installer?
https://code.google.com/p/chromium/issues/detail?id=471905

(No comment was entered for this change.)

[chro...@googlecode.com]

Updates:
Labels: Enterprise-Triaged

Comment #6 on issue 471905 by mnis...@chromium.org: Is option

NOGOOGLEUPDATEPING=1 still supported for MSI installer?
https://code.google.com/p/chromium/issues/detail?id=471905

The installer wizards have been cc'ed, so removing this from the enterprise
triage queue.

[chro...@googlecode.com]

Updates:
Labels: Needs-Feedback

Comment #9 on issue 471905 by smok...@chromium.org: Is option

NOGOOGLEUPDATEPING=1 still supported for MSI installer?
https://code.google.com/p/chromium/issues/detail?id=471905

grt@ Can you please review above comment and update the bug with your
findings ?

[chro...@googlecode.com]

Comment #10 on issue 471905 by g...@chromium.org: Is option

NOGOOGLEUPDATEPING=1 still supported for MSI installer?
https://code.google.com/p/chromium/issues/detail?id=471905

I get the same results: installing the .msi with NOGOOGLEUPDATEPING=1
completes quickly on a machine with no network connection. syao: can you
provide more details as to what network connections are attempted?

[chro...@googlecode.com]

Updates:
Labels: TE-NeedsFurtherTriage

Comment #11 on issue 471905 by tkonch...@chromium.org: Is option

NOGOOGLEUPDATEPING=1 still supported for MSI installer?
https://code.google.com/p/chromium/issues/detail?id=471905

(No comment was entered for this change.)

[chro...@googlecode.com]

Updates:
Status: Assigned
Owner: yye...@google.com
Labels: -TE-NeedsFurtherTriage

Comment #12 on issue 471905 by s...@chromium.org: Is option

[chro...@googlecode.com]

Comment #13 on issue 471905 by yye...@google.com: Is option

NOGOOGLEUPDATEPING=1 still supported for MSI installer?
https://code.google.com/p/chromium/issues/detail?id=471905

Tested Chrome MSI installation with NOGOOGLEUPDATEPING=1 flag on Windows 8.1

Steps taken:
1) disabled all NIC's
2) blocked all TCP and UDP outgoing traffic in Firewall
3) command used:
msiexec /i googlechromestandaloneenterprise.msi NOGOOGLEUPDATEPING=1 /l*v
log.txt

Result: Chrome successfully installed.

Images attached.


Attachments:
Screen Shot 2015-07-16 at 3.39.09 PM.png 775 KB
Screen Shot 2015-07-16 at 3.40.08 PM.png 300 KB

[chro...@googlecode.com]

Comment #14 on issue 471905 by s...@google.com: Is option

NOGOOGLEUPDATEPING=1 still supported for MSI installer?
https://code.google.com/p/chromium/issues/detail?id=471905

Here's a test on latest MSI installer:

Run command 'msiexec /i GoogleChromeStandaloneEnterprise.msi

NOGOOGLEUPDATEPING=1 /l*v log.txt'. No network connection at all. This is
expected behavior.

[chro...@googlecode.com]

Updates:
Status: WontFix
Owner: ---
Cc: yye...@google.com

Comment #15 on issue 471905 by s...@chromium.org: Is option