Oma User Service

Listing Results Oma User Service

Frequently Asked Questions

• How does the OMA DM client communicate with the server?

  The OMA DM client communicates with the server over HTTPS and uses DM Sync (OMA DM v1.2) as the message payload. This topic describes the OMA DM functionality that the DM client supports in general. The full description of the OMA DM protocol v1.2 can be found at the OMA website. The following table shows the OMA DM standards that Windows uses.

• How does InTune send OMA-URIs to Windows clients?

  Intune: After a custom policy is created and assigned to client devices, Intune becomes the delivery mechanism that sends the OMA-URIs to those Windows clients. Intune uses the Open Mobile Alliance Device Management (OMA-DM) protocol to do this. It is a pre-defined standard that uses XML-based SyncML to push the information to the client.

• What is the OMA-Uri and what does it mean?

  The OMA-URI is a path to a specific configuration setting that is supported by a CSP. The OMA-URI: It is a string that represents custom configuration for a Windows 10-based device. The syntax is determined by the CSPs on the client. You can find details about each CSP here. A custom policy: It contains the OMA-URIs to deploy.

• Is there a way to create a custom OMA-Uri policy?

  It is documented in the Windows CSP reference. After you determine the OMA-URI, create a custom policy for it. No matter which method you use, the end result is identical. Here's another example that uses BitLocker. For Windows, Group Policy provides very granular control for management.

• How do I deploy a custom OMA-Uri to target a Windows device?

  To deploy a custom OMA-URI to target a CSP on a Windows device, create a custom policy. The policy must contain the path to the OMA-URI path together with the value that you want to change in the CSP (enable, disable, modify, or delete). After the policy is created, assign it to a security group so that it will take effect.

• How does the windows CSP read the OMA-Uri payload in InTune?

  Typically, it does this by adding, reading, or changing registry values. To summarize: The OMA-URI is the payload, the custom policy is the container, Intune is the delivery mechanism for that container, OMA-DM is the protocol that's used for delivery, and the Windows CSP reads and applies the settings that are configured in the OMA-URI payload.

• How do I configure OMA-Uri policies to work with the CSP?

  Use the built-in policy settings whenever possible, and use custom OMA-URI policies only for options that are otherwise unavailable. To demonstrate this process, you can use a built-in policy to set the lock screen image on a device. You can also deploy an OMA-URI and target the relevant CSP.

• What is the difference between OMA-Uri and custom policy and InTune?

  To summarize: The OMA-URI is the payload, the custom policy is the container, Intune is the delivery mechanism for that container, OMA-DM is the protocol that's used for delivery, and the Windows CSP reads and applies the settings that are configured in the OMA-URI payload.