Forum Discussion
Please explain custom configuration policy oma-uri settings.
Hy,
yes you are right is a little bit confusing...i will try to give you some start points in order for you to be able to have e better overview.
So...
Open Mobile Alliance - Uniform Resources (OMA-URIs), a Microsoft Proprietary Language that describe how custom policies are delivered to a Windows 10-based device with Microsoft Intune.
CSPs - are an interface that is used by mobile device management (MDM) providers to read, set, modify, and delete configuration settings on the device. Typically, it is done through keys and values in the Windows Registry. CSP policies have a scope that defines the level at which a policy can be configured. It is similar to the policies that are available in the Microsoft Intune admin center.
How it Works:
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.
CSPs: After the OMA-URIs reach the client, the CSP reads them and configures the Windows platform accordingly. Typically, it does this by adding, reading, or changing registry values.
Check the Link bellow in order to test that and to better understand it.
Example:
basically delete a configuration for a reboot task
NAME: Task Reboot Delete
OMA-URI: in this Case the Scope, either User, Device in our Case Device:
./Device/Vendor/MSFT/Reboot/Schedule/DailyRecurrent
Data type: is a String (check the link bellow and see Format)
Value: Location,Property or admx Files
Hope it helps you to find a further Path.
Good luck!
Yes, I have read all of these. It's missing something.
What about the examples that don't work? What about when I want to make something happen?
What I mean by this is the docs never truly explain what is needed on the client side for success.
Do I need to add an ADMX file to the local system?
Can I randomly write to the registry where I want?
Why are some things failing? (The logs are BS and not really helpful unless you experience success.)
Am I limited in scope about what can be used? (Docs do mention this but it's annoyingly spotty what does and doesn't work)
