New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 888694 link

Starred by 4 users
Status: Fixed
Owner:
pastarmovj@chromium.org
Closed: Sep 25
Cc:
█ vkhabarov@chromium.org
vkasatkin@google.com
marchuk@chromium.org
█ jayhlee@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug
LBS



Sign in to add a comment

For LBS Enterprise mode, Aletrnative Browser Arguments policy does not get pushed

Project Member Reported by vkasatkin@google.com, Sep 24 
Chrome version: 68.0.3440.84, 69.0.3497.100  
OS version: Windows 7 Enterprise, Windows Server
Case#:16988103

Description:
Any value for AlternativeBrowserArguments policy for enterprise LBS, does not get pushed to Chrome browser.   


Steps to reproduce: 
1. Download and install the ADM or ADMX template for Windows Group Policy Editor (per https://support.google.com/chrome/a/answer/3062039?hl=en&ref_topic=3062034)
2. Configure AlternativeBrowserArguments policy
(example: https://drive.google.com/open?id=1jQsahVLe2WH3G6Y-4ZWrpa-SuT2dM7Zc)
3. Check Chrome policy on user machine. There is no AlternativeBrowserArguments in the list of LBS extension policies. Other policies are present (e.g. alternative_browser_path) 

Current Behavior / Reproduction: 
Could not set value for AlternativeBrowserArguments LBS policy

Expected Behavior: 
AlternativeBrowserArguments should be availiable

Drive link to logs: 
Policies for test reproduction:
https://drive.google.com/open?id=1SB5LgFsNO593QMXa9VH6Uk-NHQJb-pgI

Comment 1 by jayhlee@google.com, Sep 24

Owner: pastarmovj@chromium.org
Julian, any thoughts on this one?

@vkhabarov: can we confirm if this worked with older Chrome versions? When did it break?

Comment 2 by vkasatkin@google.com, Sep 24 

@jayhlee - Customer is having this issue on Chrome version 65.0.3325.181. As I understand, they did not try setting up AlternativeBrowserArguments before. 
LBS Version is 5.4.

Comment 3 by pastarmovj@chromium.org, Sep 25

Labels: LBS
Status: Fixed (was: Untriaged)
In either case this bug is fixed on the current beta channel (v5.5) and the fix will make it to the stable pretty soon. I would advice to test the fix on the beta to make sure it covers the observed issue.

Comment 4 by eguerin@google.com, Oct 1 

Hi, do we have an ETA when the fix will make it to the Stable channel? (Question from customer who raised this bug). Thanks

Comment 5 by pastarmovj@chromium.org, Oct 2 

We are verifying with a customer one other issue that is supposed to be fixed with this release and once we have the confirmation (hopefully this week, or early next week) we will promote 5.5 to stable.
►

Sign in to add a comment