Earlier this year I wrote the same but more of a manual method to map drives using Endpoint Manager OMA-URI function and by ingesting the ADMX files in raw form to configure the drives.
After Microsoft announced the Preview of the Import ADMX function, I was thrilled as I wanted to test out a lot of policies for Intune. Ideally, if you need to bring the on-prem GPO capability of applying Administrative Templates of a setting that is not in MEM profile configuration or a non-Microsoft related app that has its own ADMX/ ADML files and if you need to bring the same on-prem feature to Endpoint Manager, this is a good option.
Even though the result was elegant, the previous process was not so elegant. Because there were no way of importing ADMX files, the ingestion had to be done manually and then create another OMA-URI to map the path and the drive letter. The full steps can be seen in my above previous post. And its the same for other ADMX setups as well.
The process is quite simple. Choose the ADMX file you need > Upload the ADMX/ ADML files > Configure profile
- A maximum of 10 ADMX files can be uploaded. Each file must be 1 MB or smaller.
- For each ADMX file, only one ADML file can be uploaded.
- Each ADMX file supports one language.
- Currently, only en-us ADML files are supported.
Lets try this now!
Choose the ADMX file you need – For this use case, I’ll be using the DriveMapping ADMX file.
I used Drivemapping.admx and Drivemapping.adml files from https://www.anoopcnair.com/managing-network-drive-mappings-with-intune/ and credits and thanks to Mark Thomas for creating them.
Because I need to download the DriveMapping.admx and DriveMapping.adml files, I’m using this link
Once downloaded, extract to a location.
Upload the ADMX/ ADML files
Below is uploading any 3rd party or other ADMX files in to Endpoint Manager.
Go to Endpoint Manager > Devices > Configuration Profiles > Import ADMX
Use Import option and import the ADMX and ADML files as below
Status can be seen as below
That’s all for the Importing part of the file.
Now that the ADMX file has been imported, we can use Config Profiles to setup the policy.
Use Devices > Configuration Profiles to create a profile
The settings can be seen in the User Configuration section
Once done, assign it to the relevant user group from the Assignment section.
And you are all good to go!
Importing ADMX option is a much much needed setting and I’m so glad it’s finally here. Still in Preview, meaning it needs more work and feedback before it goes GA. I already see a lot of limitations has been lifted specially with creating polices for non-Microsoft software. Also according top my knowledge this is another reminder that On-Prem GPOs will die soon. The future of the policies are clearly cloud and again, it’s time to plan your GPOs, analyse them using Endpoint Manager GPO Analyser and create them them or use MEM to create them and specially, user this preview feature to test few ADMX files so you know the cloud capabilities.