Web Server Configuration for DUA

5/10/2007

You can host DUA updates from any type of Web server, however when you configure your Web server, it is important to note the following design considerations:

• You must include the .dup extension as a registered MIME type.
• It is strongly recommended that you use HTTPS to improve security when transferring the update. You should create a user account on the Web server that is used exclusively by DUA to access the update file. By using an exclusive user account, you can reduce the risk of tampering with, or interception of, the update.
• The files on the server must have the appropriate access permissions.

For additional information, refer to your Web server documentation.

The following sections provide instructions for Microsoft Internet Information Services (IIS).

In This Section

• How to Configure IIS for DUA
  Describes the end-to-end process for configuring HTTPS on IIS for DUA.

• Assigning a Certificate to your Web Server for HTTPS
  Describes how to obtain and install a certificate to allow for secure HTTPS communications with your device.

• Configuring IIS to Serve the Device Update Program
  Describes how to configure IIS to serve the device update program.

• Configuring IIS Access Permissions for DUA
  Describes how to change IIS access permissions to allow DUA to download the device update program.

• Review the DUA Configuration Settings for HTTPS
  Describes the settings you need to verify before testing DUA with HTTPS.

• Viewing DUA Actions in an IIS Log
  Describes how to troubleshoot DUA by reviewing DUA actions in the IIS event log.

Related Sections

• Device Update Agent
  Describes the Device Update Agent (DUA). You can use DUA to upgrade a run-time image remotely with QFE updates or revised components.