UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:45.0) Gecko/20100101 Firefox/45.0

Steps to reproduce the problem:
1. Install Google Chrome ADMX/ADML files and Google Update ADMX/ADML files.
2. Create new or open existing GPO object for editing.
3. Expand "Computer Configuration" -> "Administrative Templates".
4. Observe "Google" folders.

What is the expected behavior?
There should be only one folder "Google", settings for both Chrome and Omaha should be grouped under it. 

What went wrong?
Two sibling "Google" folders are seen.

Did this work before? No 

Chrome version: <Copy from: 'about:version'>  Channel: n/a
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 23.0 r0

The root category with display name "Google" should not be located in main ADMX files for Chrome and Omaha. Instead, it should be put into a separate ADMX file and referenced from main ADMX files of Chrome and Omaha. Currently Chrome and Omaha ADMX files have root categories with the same display name "Google", but with different internal names: "google" for Chrome and "Cat_Google" for Omaha. To make both sets of Administrative Templates use same root category, the common name must be choosen. In the set of instructions below it is assumed that name "Cat_Google" is choosen.

---New root category file---
1. New ADMX file should be created, preferred name "google.admx", together with corresponding ADML file(s).
2. The "google.admx" file must contain root namespace, preferred name "Google.Policies".
3. The root category with name "Cat_Google" must be put into "google.admx".
4. The root category name "Google" must be put into "google.adml" file(s).

---Chrome ADMX update---
1. The root category "google" must be removed from "chrome.admx".
2. The root category display name must be removed from "chrome.adml" file(s).
3. File "chrome.admx" must reference namespace "Google.Policies".
4. Second-level categories "googlechrome" and "googlechrome_recommended" must be modified to use root category "Cat_Google" from namespace "Google.Policies" as parent.

---Omaha ADMX update---
1. The root category "Cat_Google" must be removed from "GoogleUpdate.admx".
2. The root category display name must be removed from "GoogleUpdate.adml" file(s).
3. File "GoogleUpdate.admx" must reference namespace "Google.Policies".
4. Second-level category "Cat_GoogleUpdate" must be modified to use root category "Cat_Google" from namespace "Google.Policies" as parent.

Then new "google.admx" and its ADML file(s) should be distributed together with ADMX files for both Chrome and Google Update.
 

Deleted: Google ADMX problem.png 25.6 KB

	Google ADMX problem.png 25.6 KB View Download