DefaultBrowserSettingEnabled and DeveloperToolsDisabled flags do not change in browser after being changed in Group Policy
Reported by
jonathan...@gmail.com,
May 16 2016
|
|||
Issue descriptionVersion of Google Chrome (Wrench-> About Google Chrome): 50.0.2661.102 Version of MSI (if applicable): Using group policy settings? Yes 1. Install Google Chrome Enterprise with Group Policy settings DeveloperToolsDisabled = Enabled (GPO: User Configuration > Policies > Classic Administrative Templates (ADM) > Google > Google Chrome > Disable Developer Tools) and DefaultBrowserSettingEnabled = Disabled (GPO: User Configuration > Policies > Classic Administrative Templates (ADM) > Google > Google Chrome > Set Chrome as Default Browser) 2. Change Group Policy so that DeveloperToolsDisabled = Disabled or Not Configured and DefaultBrowserSettingEnabled = Enabled or Not Configured; do gpupdate /force or restart 3. Chrome still does not allow access to Developer Tools or allow user to set as default browser When the above Group Policy settings are changed, users should have access to the Developer Tools and have the ability to set the default browser.
,
May 18 2016
+Matt +Georges
,
May 27 2016
You can close this, it ended up being the same settings in another GPO that were causing this behavior.
,
May 27 2016
Thanks Jon |
|||
►
Sign in to add a comment |
|||
Comment 1 by pelets...@chromium.org
, May 18 2016