Deploy from an Image (Standard 7 SP1)

7/8/2014

This method gives you the most flexibility in your manufacturing environment, and enables you to duplicate multiple computers quickly. By creating a base image, you can apply the image onto multiple computers that use identical configuration. You can also customize the base image to meet the requirements of a specific order or for a specific customer. This method is also known as build-to-plan (BTP) or build-to-order (BTO). The BTP method is used when deploying an image of the development installation without customizing the destination computers. The BTO method is to deploy an image of the development installation to the destination computers. These are started in audit mode and customized to order.

When you adjust this method for your specific manufacturing environment, it significantly reduces the time required to manufacture each computer. For example, if you give your customers a choice from a standardized range of applications, you can stage many or all these applications in the development installation. In audit mode (sysprep /audit), you can install the required applications and delete the remaining applications. This method is faster than installing each required application in the factory. For more information about how to use audit mode, see Customize in Audit Mode.

Every time you build a computer by using this method, you start from a known, tested development installation. When the components change within your manufacturing environment, you must test only those modifications in addition to the known development installation, significantly reducing the testing time that is required for building and testing a new development installation.

By using various implementations of the Unattend.xml answer file, you can automate all or parts of the installation process. However, fully implementing an automated version of this method does require more preparation time. The following illustration shows an image-based deployment.

The basic process of this method is as follows:

1. Build a development installation that uses as many customizations as necessary, where these customizations apply across a product line or all the computers that you manufacture. Thoroughly test this installation.

2. If the installation is ready for deployment and delivery, shut down the operating system by using Sysprep and the sysprep /oobe /generalize /shutdown command. If you plan to customize the installation before delivery, type sysprep /audit.

3. Use ImageX to capture an image of the development installation, and then store the image on a distribution share specified by Image Configuration Editor.

4. Assemble the hardware for the destination computer.

5. Start the destination computer that has Windows Preinstallation Environment (Windows PE) 3.0.

6. Configure the hard disk of the destination computer.

7. (Optional) If you ran the sysprep /audit command, customize the installation manually or automatically by using Unattend.xml. In this mode, you can add applications and configurations. Run the sysprep /oobe /generalize /shutdown command when you have finished.

   Note

   This method requires that each destination computer has an installed network adapter.

8. Deploy the image using ImageX or Image Builder Wizard.

OEMs who manufacture lots of computers can automate some or all this process, or build a customized version of Windows PE by using the tools that are provided with this kit.

You can modify this process to duplicate the development installation onto separate hard disks, and then later put those hard disks into fully assembled computers.

See Also

Tasks

Deploy an Image by Using ImageX
Deploy an Image from a WIM Using Image Builder Wizard

Concepts

Deployment Methods