Partager via

Obex Configuration Service Provider

  • Article

4/8/2010

The Obex Configuration Service Provider configures the Obex server, which performs Bluetooth and infrared beaming. If the device is being run by the Obex server and has the associated hardware, the device can receive Bluetooth and infrared beams.

Note

This Configuration Service Provider is available only on Windows Mobile Standard.

Note

This Configuration Service Provider can be managed over both the OMA Client Provisioning (formerly WAP Client Provisioning) and the OMA DM protocol.

Note

Access to this Configuration Service Provider is determined by Security roles. Because OEMs and Mobile Operators can selectively disallow access, ask them about the availability of this Configuration Service Provider. For more information about roles, see Security Roles and Default Roles for Configuration Service Providers.

The following image shows the management object used by OMA DM.

Bb737558.cc157bec-1174-437a-af8f-c4aa0b433888(en-us,MSDN.10).gif

The following image shows the Configuration Service Provider in tree format as used by OMA Client Provisioning.

Bb737558.9ff5c5b4-ee44-4bff-a280-f70e95530542(en-us,MSDN.10).gif

Characteristics

  • HKLM\Software\Microsoft\Obex
    This characteristic must be present to change the Obex mode.

Parameters

  • IsEnabled
    This parm is used in the HKLM\Software\Microsoft\Obex characteristic to set the Obex mode. It can be true or false.

    Value Description

    0

    False. Obex is off; the device cannot receive beams.

    1

    True. Obex is on; the device can receive infrared and Bluetooth beams if the relevant hardware is present and turned on.

    The following table shows the default settings.

    Permissions

    Read/write

    Data type

    Boolean

    Roles allowed to query and update setting

    Manager

    AuthenticatedUser

Microsoft Custom Elements

The following table shows the Microsoft custom elements that this Configuration Service Provider supports for OMA Client Provisioning.

Elements Available

parm-query

Yes

noparm

No

nocharacteristic

No

characteristic-query

No

Use these elements to build standard OMA Client Provisioning (formerly WAP Client Provisioning) configuration XML. For information about specific elements, see MSPROV DTD Elements. For examples of how to generally use the Microsoft custom elements, see Provisioning XML File Examples.

For information about OMA Client Provisioning, see OMA Client Provisioning Files.

The following topics provide examples for the Obex Configuration Service Provider:

See Also

Tasks

Obex Configuration Service Provider Examples for OMA Client Provisioning

Concepts

Configuration Service Provider Reference for Windows Mobile Devices