MDM Bridge WMI Provider and Windows 10 MDM Capabilities

MDM Bridge

MDM WMI Bridge provider is used to map the CSPs to WMI. For WMI, refer to this link:

It is worth noting that OMA-DM {Open Mobile Alliance (OMA) Device Management (DM)} is the protocol in which Windows 10 MDM is based.  See the following link for more details.

Therefore, referring to these terms interchangeably consequently has some differences. Technically, one can refer to Windows 10 MDM as OMA-DM, but it becomes clearer to refer to it as Windows 10 MDM.

MDM Bridge WMI Provider provides a bridge to the capabilities of Windows 10 MDM. When a connection is initiated to the rootcimv2mdmdmmap namespace, this is similar to connecting to the MDM Bridge WMI Provider.
– These Classes in the namespace bundles the Configuration Service Provider (CSP) of Windows 10 MDM.

Note: PowerShell can be used to configure and get information through the MDM

See the following link on how to run and configure Windows 10 MDM:

Here are some vital points to note when employing the MDM Bridge WMI Provider

  • When executing the PowerShell script, ensure to run the MDM Bridge WMI Provider with Administrative privilege.
  • Ensure you have the PSTool downloaded because the local system context is required to view and modify the device settings.
  • This can be achieved by running the download path of the PsTool. Enter the command to launch PsExec in MD or Power Shell.

    – psexec.exe -i -s cmd.exe or
    – psexec.exe -i -s PowerShell.exe
  • Emphasis on the system and user settings cannot be taken for granted. It is necessary to emphasize that, certain user settings won’t show up when connected to the System context, just as specific device settings wot show up in user settings.

Visit the following links to learn more about the capabilities of MDM bridge WMI Provider.

Notify of

Inline Feedbacks
View all comments
Would love your thoughts, please comment.x