UnInstall Configuration Service Provider
This Configuration Service Provider uninstalls applications from the device. A provisioning document that contains XML to uninstall an application should contain only that XML and no other provisioning information. Following this practice is the cleanest way to uninstall an application under the transactioning model for Windows Mobile Version 5.0 software for Smartphones.
Note This Configuration Service Provider can be managed over the OMA Client Provisioning (formerly WAP) and the OMA DM protocols. However, over the OMA DM protocol, you can only query applications that are installed on the device; you cannot uninstall an application.
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 The LocURI for accessing the Uninstall root node is case sensitive.
The following image shows the Configuration Service Provider in tree format as used by OMA Client Provisioning.
- application name
The name of the application can be used as a characteristic type.
A Boolean value that determines whether to uninstall the application. A value of 0 specifies that the application is not to be uninstalled. A value of 1 indicates to uninstall the application.
The root characteristic and the application name characteristic use this parm.
The following table shows the default settings.
Permissions read/write Roles allowed to query and update setting Manager
Microsoft Custom Elements
The following table shows the Microsoft custom elements that this Configuration Service Provider supports for OMA Client Provisioning.
|parm-query||Yes (uninstall parm always returns 0)|
Root level of the Configuration Service Provider: Yes
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.
Send Feedback on this topic to the authors