Boot and Test the Master Image

5/10/2007

Once you have deployed the image to your device, you need to boot the device.

To test your image

Complete the First Boot Agent (FBA) phase.

Note

For mass deployment, you should reseal the device after completing FBA. This ensures that when the image is deployed, each device has a unique security ID (SID) and computer name. For more information about cloning and resealing, see Cloning Overview.
Uncover possible run-time image or boot errors.
Verify that your device and applications work properly.
Perform additional post-FBA configuration changes or customization, if needed.
Rebuild, boot, and retest until your device functions properly. Your final image should meet the following criteria:
- The image boots successfully and runs correctly on your target device.
- All extraneous applications have been removed, such as internal diagnostic, testing, or debugging applications that you do not want to appear on the customer's device.
- The run-time image has been resealed so that a new and unique SID is created on each device when the image is deployed.
- The image is available offline on a drive accessible from your development computer. This can be a mounted SDI volume, a folder on your development computer, or a Universal Naming Convention (UNC) network path.

Complete the First Boot Agent (FBA) phase.

Note

For mass deployment, you should reseal the device after completing FBA. This ensures that when the image is deployed, each device has a unique security ID (SID) and computer name. For more information about cloning and resealing, see Cloning Overview.
Uncover possible run-time image or boot errors.
Verify that your device and applications work properly.
Perform additional post-FBA configuration changes or customization, if needed.
Rebuild, boot, and retest until your device functions properly. Your final image should meet the following criteria:
- The image boots successfully and runs correctly on your target device.
- All extraneous applications have been removed, such as internal diagnostic, testing, or debugging applications that you do not want to appear on the customer's device.
- The run-time image has been resealed so that a new and unique SID is created on each device when the image is deployed.
- The image is available offline on a drive accessible from your development computer. This can be a mounted SDI volume, a folder on your development computer, or a Universal Naming Convention (UNC) network path.