Custom OMA settings

The Custom OMA configuration settings push custom policies as OMA configuration files to Windows devices.

Windows custom profiles use Open Mobile Alliance Uniform Resource Identifier (OMA-URI) settings to configure different features that are used by mobile device manufacturers to control features on a device.

The MaaS360 Custom OMA policy includes many built-in settings that allow you to control different features on devices in your organization. Use this policy when you want to use device settings and features that are not built in to the Windows MDM policy. Contact IBM® Support to enable this setting.

Note:

Custom OMA settings are deployed to devices in the form of XML files. This workflow (creating XML files) is intended for advanced administrators. Make sure that you consult the Microsoft documentation when you are creating XML files. The Microsoft Windows CSPs for Desktops and Phones, sample code, and supported values are available from the following links:
- https://docs.microsoft.com/en-us/windows/client-management/mdm/configuration-service-provider-reference
- https://docs.microsoft.com/en-us/windows/client-management/mdm/new-in-windows-mdm-enrollment-management
If a policy setting is already implemented in the Windows MDM policy, do not configure this same setting as a custom OMA setting. For example, you configured the Antivirus policy setting Scan Type > Quick Scan. Do not create a custom OMA XML file for the Antivirus policy setting that implements a different configuration, where Scan Type = Full Scan.

Table 1. Custom OMA settings
Policy setting	Description	Supported devices
Import Custom OMA Settings	Choose whether to allow the user to import custom OMA settings files and apply those files on Windows devices.	Windows Professional, Education, Enterprise Windows HoloLens Windows Team
Custom OMA settings file	Choose from a list of deployed custom OMA settings file to apply. Creating a custom OMA settings file Follow these steps to create and deploy the custom OMA settings file: Create an XML file. For example: Note: Custom OMA settings are deployed in the form of XML files. The Microsoft Windows CSPs for Desktops and Phones, sample code, and supported values are available from the following links: https://docs.microsoft.com/en-us/windows/client-management/mdm/configuration-service-provider-reference https://docs.microsoft.com/en-us/windows/client-management/mdm/new-in-windows-mdm-enrollment-management Go to Security > Policies > More > Policy Files > Upload Content. Enter the following details for the file: Available for: Specifies which devices receive the custom OMA settings. Content name: Specifies the name of the custom policy. Type: Specifies the type of policy. Select Custom OMA Settings from the options. Content: Displays the name of the XML file that you created in step 1. Click Upload Content. From the Policies page, select a Windows MDM policy. Go to Advanced Settings > Custom OMA Settings and select the file that you updated in step 3. Click Save and Publish. Deleting a custom OMA settings file from a device Follow these steps to create a delete XML file that removes the custom OMA settings from a device (use this file if you experience issues after applying the Custom OMA policy to devices): Create a delete XML file. For example: Go to Security > Policies > More > Policy Files > Upload Content. Enter the following details for the file: Available for: Specifies which devices receive the custom OMA settings. Content name: Specifies the name of the custom policy. Type: Specifies the type of policy. Select Custom OMA Settings from the options. Content: Displays the name of the delete XML file that you created in step 1. Click Upload Content. From the Policies page, select a Windows MDM policy. Go to Advanced Settings > Custom OMA Settings and select the delete XML file that you updated in step 3. Click Save and Publish. Note: When you apply the delete XML file to a device, the value of the corresponding attribute is assigned the default value. For example, in the delete XML file sample, the default value for Allow VPN is `1`, indicating that Allow VPN is enabled. When you apply the delete XML file, the value of Allow VPN is assigned `1` in the registry, which is the default value.	Windows Professional, Education, Enterprise Windows HoloLens Windows Team