Options for Servicing a Run-Time Image (Windows Embedded Standard 2009)

4/23/2012

There are several ways that you can update a deployed run-time image. The following table shows the different servicing options:

Servicing Option Description Benefits Drawbacks

Re-imaging

Completely replace the existing run-time image with an updated run-time image.

Can thoroughly test and verify the updated run-time image before it is redeployed.

Must rebuild and redeploy new run-time images to all existing devices.

Automatic Incremental Updates

Use a servicing mechanism, such as DUA, SUS, or SMS to make incremental updates to an existing run-time image. For more information about supported servicing mechanisms, see Comparison of Servicing Solutions.

Updates are automatically applied to your run-time images.

  • An administrator must set up, configure, and test the servicing mechanism in their environment.
  • Run-time images must be available on the network to receive updates.

Manual Incremental Updates

Manually install files, registry keys, and applications to an existing run-time image.

  • No requirement to rebuild the image.
  • The image is directly updated and requires no additional software agents for update (for example, DUA).
  • The image changes can be limited to specific files, registry keys, and applications.
  • Requires an administrator to update every device.
  • Can be time-consuming.

The appropriate servicing solution depends on the specifications of the device. For example, re-imaging a run-time image is typically suited for devices that do not contain bootable media and must start over a network, such as RAM Boot images.

Automatic incremental updates are most practical for an enterprise environment where scripting resources are available and where the deployed devices are networked. You can use one of the supported servicing solutions (DUA, SMS, or SUS) or you can create your own servicing solution. For more information about device servicing strategies, see Servicing.

Manual incremental updates are useful if you have many different run-time images on multiple device types and a single update will not apply to all your devices. By manually installing the updates, you can verify that each run-time image is updated appropriately.

See Also

Concepts

Systems Management Server (SMS)

Other Resources

Run-Time Image Servicing
Manage and Service a Run-Time Image
Device Update Agent
Software Update Services (SUS)
Deploy a Run-Time Image