Apply Images by Using ImageX

Transcription

1 1 of 5 Apply Images by Using ImageX 9 out of 10 rated this helpful - Rate this topic Published: October 22, 2009 Updated: June 28, 2011 Applies To: Windows 7, Windows Server 2008 R2 This content applies to Windows 7. For Windows 8 content, see Windows Deployment with the Windows ADK. This topic describes how to deploy images captured from your reference computer to one or more destination computers. This process is called build-to-plan. Prerequisites Image-capturing tools, such as a Windows Preinstallation Environment (Windows PE) RAM disk containing the ImageX tool. You can create a Windows PE RAM disk with ImageX by using the process described in Windows PE Walkthroughs. Windows image (.wim) files. You can capture images by using the process described in Capture Images. In This Topic This topic describes the following processes: Booting the Destination Computer by Using Windows PE Connecting to the Network Distribution Share Managing Multiple Hard Disks Creating the Partition Structure for the Hard Disks Applying Your Windows Images Setting up a System Partition Setting up a Recovery Partition Setting up Other Partition Types Preparing the Computer for Shipping Testing and Customizing the Computer You can automate various steps in this process. For example, you can write a Windows PE script to automatically connect to a network and apply an image. The following diagram shows how the fictitious OEM, Fabrikam, deploys the Windows image onto a destination computer, Fabrikam Model FNB1.

2 2 of 5 Booting the Destination Computer by Using Windows PE Boot the destination computer to Windows PE. For more information, see Walkthrough: Boot Windows PE from CD-ROM. Connecting to the Network Distribution Share Connect to the network distribution share where your Windows image is stored. For example, you can use the net use command to do this. net use n: \\server\share If prompted, provide your network credentials. Managing Multiple Hard Disks If you are deploying to a computer that contains multiple hard disks, see these topics for instructions on identifying each disk. Manage Multiple BIOS-based Hard Disks Manage Multiple UEFI-based Hard Disks Prepare to deploy images to a computer with multiple BIOS-based or VDS-based disks. Prepare to deploy images to a computer with multiple Unified Extensible Firmware Interface (UEFI)-based disks. Understanding Disk Location Paths Use the physical location path of the disk to identify each disk. Use this when deploying images to computers with two or more unique non-system disks or to computers with multiple, UEFI-based disks.

3 3 of 5 Creating the Partition Structure for the Hard Disks On the destination computer, create a structure for the partitions where you apply your images. The partition structure on the destination computer must match the partition structure of the reference computer. 1. Start the destination computer by using Windows PE. For more information, see Booting Windows PE. 2. At the Windows PE command prompt, type diskpart to start the DiskPart tool. X:> diskpart 3. Create your partition structure using the diskpart commands. select disk 0cleancreate partition primary size=350format quick fs=ntfs label="system For samples of DiskPart scripts for recommended partition structures, see Sample: Apply Images on a BIOS-based Computer by Using ImageX and Sample: Apply Images on a UEFI-based Computer by Using ImageX. You can automate this task with the diskpart /s <script> command. For more information, see Diskpart Command line syntax. Applying Your Windows Images Use the ImageX tool to apply images to your Windows partition. If you apply an image to a volume with an existing Windows installation, files from the previous installation might not be deleted. Format the volume by using a tool such as DiskPart before applying the new image. For each partition that you apply an image to, run the ImageX/apply <image_file> <image_number image_name> <image_path> command. imagex /apply N:\Images\my-windows-partition.wim 1 W:\ For more information about ImageX, see ImageX Command-Line Options. Setting up a System Partition To set up a basic system partition, you can use the BCDboot tool to copy a simple set of system files to a system partition. These files include boot configuration data (BCD) information used to start Windows. Use the BCDboot tool to copy common system partition files and to initialize boot configuration data: W:\Windows\System32\bcdboot W:\Windows /l en-us For more information on the BCDboot tool, see BCDboot Command-Line Options.

4 4 of 5 You can also set up the system partition by applying an image. Use the ImageX/apply <image_file> <image_number image_name> <image_path> command: imagex /apply N:\Images\my-system-partition.wim 1 S:\ Setting up a Recovery Partition You can set up the computer to reinstall your Windows image in the event of a system failure. For more information, see Deploy a System Recovery Image. Setting up Other Partition Types Microsoft Reserved partitions (MSR) and Extended partitions are managed by the computer. Do not apply an image to these partitions. Preparing the Computer for Shipping When the computer is ready to be shipped, shut down the computer. You can automate the shutdown process by using the wpeutil shutdown command. For more information, see Wpeutil Command-Line Options. The default setting boots the computer to Windows Welcome on its next startup. Testing and Customizing the Computer You can use audit mode to test the computer and to perform further customizations before you ship it to your end user. For more information, see Customize Windows in Audit Mode. You can also perform some customizations to the computer without booting it. For more information, see Walkthrough: Service an Applied Windows Image Offline. See Also Concepts Capture Images Customize Windows in Audit Mode Phase 5: Managing and Servicing Your Windows Image Did you find this helpful? Yes No Community Content diskpart commands provided above will Cause : bcdboot failure when attempting to copy boot files Hi, The diskpart commands provided above will cause an issue that, it will not allow to write BCD ("bcdboot failure when attempting to copy boot files windows 7"), hence would recommend changing it to the below format, I have tested it & found working perfectly.

5 5 of 5 select disk 0 clean create partition primary size=3000 id=27 format quick fs=ntfs label="recovery" assign letter="r" create partition primary size=300 format quick fs=ntfs label="system" Change this to > format quick fs=fat label="system assign letter="s" active create partition primary format quick fs=ntfs label="windows" assign letter="w" exit 4/15/2012 Stanley Roark 5/4/2011 Arvind Sindhu attributes command causes machines to not boot Thanks to Ord_mike You can undo "attributes volume set nodefaultdriveletter" by the selecting the partition and running the command "attributes volume clear nodefaultdriveletter". attributes command causes machines to not boot 3/23/2012 Rob Holt The above example will cause the machine to go into a reboot loop after applying both the System and Windows images to the disk. The machine shows this error, and reboots constantly: autochk program not found skipping AUTOCHECK I found that removing the line 'attributes volume set nodefaultdriveletter' from the diskpart script text file fixes the issue. 9/14/2011 ord_mike 9/13/2011 ord_mike 2012 Microsoft. All rights reserved.