Important:
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
4/8/2010

This configuration service provider uninstalls applications from the device. A provisioning document that contains XML to uninstall an application should contain onlythat XML and no other provisioning information. Following this practice is the cleanest way to uninstall an application under the transactioning model for Windows Mobile devices.

Note:
This configuration service provider can be managed over the OMA Client Provisioning protocol only.
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 Rolesand 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.

Characteristics

application name

The name of the application can be used as a characteristic type.

Parameters

uninstall

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 namecharacteristic use this parm.

The following table shows the default settings.

Permissions

read/write

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 (uninstall parm always returns 0)

noparm

No

nocharacteristic

No

characteristic-query

Yes

Recursive: Yes

Root level of the configuration service provider: Yes

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

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

See Also