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

If the provisioning XML file is in a signed .cab or .cpf file, it can be pulled OTA by the device in response to an e-mail message.

Note:
Security roles can impact the configuration result. For information on role-based access control, see OMA Client Provisioning Security Best Practices.

The following illustration shows a graphical view of how the provisioning XML is pulled to the device by using e-mail.

To deliver a provisioning XML file

  1. Put the .cab or .cpf file that contains the provisioning XML file on a Web site from which the user can download the file.

  2. To alert the user that an update is available, send an e-mail message that contains a link to the Web site.

  3. When the user clicks on the link in the e-mail, Internet Explorer Mobile opens the Web page that contains the .cab or .cpf file that has the provisioning XML file.

  4. The user downloads the file from the Web site.

    When the download is complete, the device installs the provisioning .cab file. The device is configured.

See Also

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.