Deploy from an Image (Standard 8)
7/8/2014
Review how to deploy Windows Embedded 8 Standard (Standard 8) from your base image.
This deployment method gives you the most flexibility in your manufacturing environment, and enables you to quickly duplicate the development installation image on multiple computers. By creating a base image, you can apply it to multiple computers that use an identical configuration.
You can also customize the base image to meet the requirements of a specific order or customer, also known as build-to-plan (BTP) or build-to-order (BTO). The BTP approach is used to deploy an image without customizing the destination computers. The BTO approach is used to deploy an image to the destination computers, which are started in audit mode and then customized to order.
When you adjust this method for your specific manufacturing environment, it can significantly reduce 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 of these applications in the development installation. In audit mode (sysprep /audit), you can install the required applications and delete the remaining ones. This approach is faster than installing each required application at the factory..
Every time you build a device by using this method, you start from a known, tested development installation. When the components change within your manufacturing environment, you need test only those modifications in addition to the known development installation, significantly reducing the time required to build and test a new development installation.
By using various implementations of the Unattend.xml configuration file, you can automate all or part of the installation process. However, fully implementing an automated version does require more preparation time. For more information about Unattend.xml, see Unattended Servicing Command-Line Options.
Deploying from an image
The basic process is as follows:
Build a development installation that uses as many customizations as necessary, whether those customizations apply across a product line or across all of the devices that you manufacture. Thoroughly test this installation.
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 /auditto start the destination computers in audit mode.Use ImageX to capture an image of the development installation, and then store the image in a catalog that Image Configuration Editor (ICE) specifies.
Assemble the hardware for the device on which you want to install this image.
Start the destination device in Windows Preinstallation Environment (Windows PE) 4.0.
Configure the hard disk of the destination device.
(Optional) If you ran the
sysprep /auditcommand, customize the installation manually or automatically by using Unattend.xml. In this mode, you can add applications and configurations. Run thesysprep /oobe /generalize /shutdowncommand when you are finished.Note
This method requires that each destination device have an installed network adapter.
Deploy the image using Image Builder Wizard (IBW) or Deployment Image Servicing and Management (DISM).
OEMs who manufacture many devices can automate some or all of this process, or build a customized version of Windows PE 4.0 by using the tools provided in the Windows Embedded 8 Standard Toolkit (Standard 8 Toolkit).
You can modify this process to duplicate the development installation onto separate hard disks and then later install those hard disks into fully assembled devices, depending on your device hardware.
Warning
The default image file (Install.wim) included with the product DVD works only with IBW. Do not deploy this default image directly with DISM.
See Also
Tasks
Deploy an Image from a WIM Using Image Builder Wizard
Deploy an Image from a USB Flash Drive Using ImageX