Create a Custom Windows MDM (OMA URI) Policy

Admins can configure and deploy custom MDM policies to Windows devices to meet specific needs that are not covered by JumpCloud’s existing MDM policy library. Open Mobile Alliance Uniform Resource Identifier (OMA URI) is used in MDM to configure settings and manage devices through policies.

To create a Custom MDM (OMA URI) policy:

1. Log in to the JumpCloud Admin Portal.
2. Go to DEVICE MANAGEMENT > Policy Management.
3. In the All tab, click (+).
4. On the New Policy panel, select the Windows tab.
5. Search and select Custom MDM (OMA URI) Policy from the list, then click configure.
6. (Optional) In the Policy Name field, enter a new name for the policy or keep the default. Policy names must be unique.
7. (Optional) In the Policy Notes field, enter details like when you created the policy, where you tested it, and where you deployed it.
8. In the Settings section, enter the details as required. For more information, see Group OMA-URI entires by AreaName.
   • Enter the exact value in the OMA URI field. OMA URI is a unique path that targets a specific setting or configuration.
   • Select the Format from the dropdown. The available formats are - integer, string, float, boolean, xml, and base64.
   • In the Value field, enter the exact value.
   • Use the + button to add more identifiers.

9. (Optional) Select the Device Groups tab. Select one or more device groups where you want to apply this policy. For device groups with multiple OS member types, the policy is applied only to the supported OS.
10. (Optional) Select the Devices tab. Select one or more devices where you want to apply this policy.
11. Click Save. If prompted, click Save again. No further action is needed for this policy to take effect. 

Group OMA-URI entries by AreaName

Here are some examples:

To enable policies for education environment:

• OMA URI: ./Vendor/MSFT/SharedPC/SetEduPolicies
• Format: boolean
• Value: true

To create a custom policy to update desktop Image:

• OMA URI: ./Vendor/MSFT/Personalization/DesktopImageUrl
• Format: string
• Value: file:///C:/Windows/desktopimage.png

To create a policy to block bluetooth:

• OMA URI: ./Device/Vendor/MSFT/Policy/Config/Connectivity/AllowBluetooth 
• Format: int
• Value: 0
  
  

Using an ADMX Payload in a Policy

ADMX payloads are XML files that define Group Policy settings for Windows devices, deployed via Group Policy or MDM solutions. In MDM, ADMX-backed policies are used to structure and manage settings, with corresponding payloads specifying the values for each setting, often using OMA URI to configure the device.

The format for ADMX payloads while configuring JumpCloud policies is usually string. Here's an example to create a custom Internet Explorer CSP policy using ADMX payloads.

• OMA URI: ./Device/Vendor/MSFT/Policy/Config/InternetExplorer/DisableUpdateCheck
• Format: string
• Value: <![CDATA[<enabled/>]]>

• OMA URI: ./Device/Vendor/MSFT/Policy/Config/InternetExplorer/AllowDeletingBrowsingHistoryOnExit
• Format: string
• Value: <![CDATA[<enabled/>]]>

• OMA URI: ./Device/Vendor/MSFT/Policy/Config/InternetExplorer/AllowFallbackToSSL3
• Format: string
• Value: <![CDATA[<enabled/><data id="Advanced_EnableSSL3FallbackOptions" value="3"/>]]>