Issue metadata
Sign in to add a comment
|
GPO policies won't apply on machine level
Reported by
weaver.j...@gmail.com,
May 13 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 Steps to reproduce the problem: 1. Set policies through GPO under Computer Configuration > Administrative Templates > Google > Google Chrome 2. Run Google Chrome 3. Go to to chrome://policy What is the expected behavior? Those policies set are supposed to say applied to machine What went wrong? None of those policies apply to machine unless if instead of computer configuration you do it under user configuration. This used to work with under computer configuration Did this work before? Yes 56 or 57 as far as i have tested Chrome version: 58.0.3029.110 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 25.0 r0 Could this be fixed or will all GPO policies through Windows only say current user now instead of machine?
,
May 15 2017
,
May 17 2017
Tested this issue on Skytap Environment "Windows GPO Testing - Stable - K" Unable to reproduce the issue as per steps mentioned in the Comment #0 Attaching the screen-cast for reference. weaver.jarod0312@ Could you please look into it and let us know your observations.
,
May 27 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
,
May 30 2017
,
May 30 2017
I'm not able to reproduce this. I can set policies for either the machine or the user. pastarmovj@, any ideas?
,
May 31 2017
Can you provide a screenshot of regedit with the following key opened in it HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome You should see all policies you set there. If you don't see them there as registry keys something is not woriking with your policy propagation. You can try to run "gpupdate /force" from a command prompt to force the GPO application in case it has not happened when you were testing.
,
May 31 2017
Nothing is there. Nothing is even there for Current User in registry as well. The registry wouldn't work because I have non domain system. Group Policy Editor does show the policies have applied however according to its GUI
,
May 31 2017
Even on a non-domain joined machines the Windows GPO system will write those registry keys as part of the local Policy application process. Indeed Chrome in this case reads the GPO files directly but the fact that the registry keys are not created makes be think that something is going wrong with the policy application process. Please run gpupdate /force from the command prompt and paste here the output of this command.
,
May 31 2017
It says policy updated successfully
,
May 31 2017
C:\windows\system32>gpupdate /force Updating Policy... User Policy update has completed successfully. Computer Policy update has completed successfully. C:\windows\system32>pause Press any key to continue . . . Even after this, same thing
,
Jun 1 2018
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ranjitkan@chromium.org
, May 15 2017