HowTo OMA-URI - something not working

PKlapwijk 

Probably your article would have helped, too.

Just a short addition to your article:

You're building the string together while looking inside of the admx file.

Of course, this is working. But it's much easier, after ingesting the admx file, to have a look at the clients registry. (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PolicyManager\AdmxDefault\)

At this location, every policy ingested by an admx is listed.

Hi PatrickF11 With the help of Oliver you have probably already deployed the policy, otherwise have a look at my article about managing Chrome with intune https://www.inthecloud247.com/manage-google-chrome-settings-with-microsoft-intune/ Maybe it is of any help.

Oliver Kieselbach 

Great, thank you (again).

PatrickF11 

that's correct, 

NAME222

is absolutely free and has no consequence other than representation in registry. Often it is wise to use something like your own prefix or a version MyFile or Filev1

NAME111

has to be used in both OMA-URIs that's why it miss understandingly referred to not free to choose. in fact it is free to choose but must be used in both OMA URIs

your summary is correct! 👍 

Hey Oliver Kieselbach 

there's one last question left open, after i've read through the links recommended by you:

When ingesting an admx, first i have to build the OMA-URI Path.

./Device/Vendor/MSFT/Policy/ConfigOperations/ADMXInstall/NAME111/Policy/NAME222

In one of your earlier replies you've written, that only "NAME222" is a free to choose name.

After i've read though the articles i think that "NAME111" is also free to choose, when ingesting the admx file.

What i know: When configuring an element i need to use "NAME111" of course like in the following example:

./Device/Vendor/MSFT/Policy/Config/NAME111~Policy~RestOfConfigPath/ConfigItem

And of course: i need to look into the registry (PolicyManager\AdmxDefault\...) to find the correct name for the config. ("RestOfConfigPath")

So referrencing to the Subject "Chrome Update":

I could have build the OMA-URI String for ingesting like i mentioned above, with the freely choosen name (NAME111).

Afterwards i could add configurations like that:

./Device/Vendor/MSFT/Policy/Config/NAME111~Policy~RestOfConfigPathFromRegedit/ConfigItem

Did I summarize that correctly?

So the name "NAME111" doesn't matter at all, it just have to be the same in the "ingesting part" and in the "configuration part" of my custom intune profile, right?

Oliver Kieselbach 

Ladys and Gentlemen: THIS is good support! 🙂

Again: Thank you for all the help.

I really don't know which of your answers i should mark as "best response" 😄

And thanks to all the others. 🙂 I really appreciated it.

PatrickF11 

Sure here we go 🙂

Part_ is correct as we reference the policy decimal element id with that:

    <policy name="Pol_AutoUpdateCheckPeriod" class="Machine"
        displayName="$(string.Pol_AutoUpdateCheckPeriod)"
        explainText="$(string.Explain_AutoUpdateCheckPeriod)"
        presentation="$(presentation.Pol_AutoUpdateCheckPeriod)"
        key="Software\Policies\Google\Update">
      <parentCategory ref="Cat_Preferences" />
      <supportedOn ref="Sup_GoogleUpdate1_2_145_5" />
      <elements>
        <decimal id="Part_AutoUpdateCheckPeriod"
            key="Software\Policies\Google\Update"
            valueName="AutoUpdateCheckPeriodMinutes"
            required="true" minValue="0" maxValue="43200" />
      </elements>
    </policy>

with this value and notation we are referencing the value directly not the policy element

<enabled/>
<data id="Part_AutoUpdateCheckPeriod" value="60"/>

This way the MDM client exactly knows which element in the ADMX file it has to use. Tt can also be the case that an policy definition has more than one element for configuration. That's why we exactly reference the value which configures the setting in the end.