GP setting Search Provider is not in effect even though chrome://policy shows correctly |
|||||
Issue descriptionChrome Version: 62.0.3202.0 OS: Win when set search provider in GroupPolicyManagementEditor and push to client machine, even though on client machine, chrome://policy does show newly set search provider (e.g www.bing.com), the actual search provider in use is still default google.com, chrome://settings also shows google as default search provider. What steps will reproduce the problem? (1)under Classic Adminstrative Templates(ADM)-->Google-> Google Chrome-> Default Search Provider Enable the default search provider =>Enabled Default search provider name =>Enabled=>www.bing.com (2) In client machine cmd window, run gpupdate /force in order to push change into effect (3) Launch chrome, verify chrome://policy shows: DefaultSearchProviderEnabled: true DefaultSearchProviderName: www.bing.com (4). enter any word (e.g flower) in omnibox What is the expected result? www.bing.com is used to search flower What happens instead? www.google.com (the default search provider) is used to search flower
,
Oct 25 2017
I have tried steps provided in c#1. I verified chrome://policy shows BingSearch as provider name, search provider url is also set to " https://www.bing.com/search?q={searchTerms} ", however, Google search is still used. In chrome://settings, Search engine has default value Google, this value is also not grayed out with text saying "this value is enforced by administrator."
,
Oct 25 2017
Thank you for providing more feedback. Adding requester "kkaluri@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 26 2017
Could you check on chrome://policy the policy level? Mandatory or Recommended?
,
Oct 26 2017
below is the environment link, the default search provider policy is set in Windows Server, it is also pushed to windows 7 client machine. Chrome version is 62.0.3202.0. https://cloud.skytap.com/configurations/24653608
,
Oct 26 2017
Thank you for providing more feedback. Adding requester "rsorokin@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 26 2017
I figured out what caused this issue. I used chrome-unsigned/.../policy-template.zip which seems incompatible with released chrome. After start a new environment, use chrome-signed/.../GoogleChromeEnterpriseBundle.zip, this bug not repro anymore. I resolved it as Won't Fix. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by kkaluri@chromium.org
, Oct 25 2017Labels: Needs-Triage-M62 Needs-Feedback