The value starts with (or if you like to disable a setting). Than we only need to know what our Value is. The Data type for these settings is always String. We have already seen how to build the OMA-URI for the policy HomepageURL, so let`s start with that one.

These are settings like the Homepage URL and Startpage. We start with managing the settings from the Homepage categorie. If we put al this information together, we have our OMA-URI. The last part of our OMA-URI is the actual policy displayname, in this case HomepageURL. The first categorie we find in the ADMX file is the top category and as we can see that is firefox (name). When we open the ADMX file in a text editor, we can see there are several categories. These categories can be found in the Chrome ADMX file. Between every part we have the ~ sign.Īfter Policy we see the name of two categories. It starts with Firefox (the ADMX file name), like in the ADMXInstall URI, followed by Policy. The part that comes next is not always the same, we need to follow some rules: This is default for managing applications using an ADMX file: Let`s split up the OMA-URI in seperate parts.

Device/Vendor/MSFT/Policy/Config/Firefox~Policy~firefox~Homepage/HomepageURL This is for example the OMA-URI to manage the Homepage URL But the OMA-URI for managing the settings consists of some information we need to collect ourselves from the Firefox ADMX file.

How to build up the OMA-URIĪs with deploying the ADMX file, for the settings to manage we also need to know the OMA-URI. In the next steps we add the settings we manage with Intune to the same policy. The policy to deploy the ADMX file is ready.

Mozilla firefox start page url