The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform2/+/ea8bd25cba9042c685b497a1b8e79ea2d6da679d

commit ea8bd25cba9042c685b497a1b8e79ea2d6da679d
Author: Lutz Justen <ljusten@chromium.org>
Date: Wed Sep 13 11:06:52 2017

authpolicy: Always use Chrome branded policy key

Always use Software\Policies\Google\ChromeOS to load GPO policy.
Reasoning:
- This behavior matches the Chrome client when it loads Windows registry.
- We only distribute Chrome-branded ADMX templates.
- It has been a constant hassle in the past to make sure that the
  proper ADMX templates are installed on the server and a source of
  issues where policy wasn't loaded because of wrong branding.

BUG= chromium:764319 
TEST=Tested on device

Change-Id: I3fd69325eaa1adb6990fd81a1b5ddda472362f2a
Reviewed-on: https://chromium-review.googlesource.com/663538
Commit-Ready: Lutz Justen <ljusten@chromium.org>
Tested-by: Lutz Justen <ljusten@chromium.org>
Reviewed-by: Lutz Justen <ljusten@chromium.org>

[modify] https://crrev.com/ea8bd25cba9042c685b497a1b8e79ea2d6da679d/authpolicy/policy/policy_encoder_helper.cc

Verified, authpolicy uses Software\Policies\Google\ChromeOS to load GPO policy. Attached policies.json and Windows registry screenshot.

Chrome OS: 10575.12.0
Chrome: 67.0.3396.16
Device: Santa

Deleted: policies.json 6.1 KB

policies.json 6.1 KB View Download

Deleted: Screenshot from 2018-04-26 13-51-55.png 24.9 KB

	Screenshot from 2018-04-26 13-51-55.png 24.9 KB View Download