Registry Configuration Service Provider
Although the registry is directly accessible, accessing the registry through the Registry Configuration Service Provider is the preferred method for updating registry settings. You should use the Registry Configuration Service Provider, or the Configuration Service Provider specific to the settings that require an update.
**Note **Characteristics or parameters for the FileOperation Configuration Service Provider, Metabase Configuration Service Provider, and Registry Configuration Service Provider can contain an additional attribute called "translation". The two values for this attribute are "filesystem" and "install". A translation of type "filesystem" causes all file paths to be canonicalized (that is, double backslashes are removed). A translation of type "install" includes all the translations done for "filesystem", but also translates all CE Strings (for example, %CE2%) into the correct file path for the device. Cabwiz will automatically add the appropriate translation to file operations and registry keys in an .inf file.
Note This Configuration Service Provider can be managed over both the OMA Client Provisioning (formerly WAP) and the OMA DM protocol.
Note When using OMA DM to add a registry key, a child registry value must also be added in the XML code.
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.
Note CAB files and the Registry Configuration Service Provider fail if a registry value is set outside the range of signed integers.
For OMA Client Provisioning, the follows notes apply:
- Querying the registry at the top level is not allowed. All parameters must be queried individually. The underlying data store of the Registry is typed. Be sure to use the datatype attribute of the <parm> tag.
- This documentation describes the default characteristics. Additional characteristics may be added.
- Because the Registry Configuration Service Provider uses the backslash (\) character as a separator between key names, backslashes which occur in the name of a registry key must be escaped. Backslashes can be escaped by using two sequential backslashes (\\).
The default security role maps to each subnode unless specific permission is granted to the subnode. The following table shows the default settings:
| Permissions | Read/write |
| Roles allowed to query and update setting | Manager |
The security role for subnodes is implementation specific, and can be changed by OEMs and Mobile Operators. To see the permission granted to specific subnodes, see Metabase Settings for Registry Configuration Service Provider.
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 | Yes |
| nocharacteristic | Yes |
| characteristic-query | Yes
Recursive query: Yes Top level query: No |
Use these elements to build standard OMA Client Provisioning (formerly WAP) 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.
See Also
Configuration Service Provider Reference for Windows Mobile-Based Devices | Registry Configuration Service Provider Examples for OMA Client Provisioning
Send Feedback on this topic to the authors