Objectives
Use Windows System Image Manager to create a distribution share
Modify a Windows Vista staged image
Create a computer master image using ImageX
Modify a WIM file in an offline scenario
Scenario
Your organization has standardized on Windows Vista as its desktop platform.
You are responsible for creating a standard image that will be distributed to all
clients. Once you have created the standard image it will be given to the
distribution team who will be responsible for it deployment via methods
including Windows Deployment Services (WDS), Image Based Setups (IBS),
network & CD/DVD based installations.
Background Information
The following virtual machines will be used to help you complete the lab”
VistaLabs_DC1: Domain Controller running Server 2003, file server
Prerequisites
You should be familiar with the following products or technologies before you
begin this lab.
Familiarity with Business Desktop Deployment
Understanding of Imaging Technologies such as Ghost or PowerQuest
Understanding of Microsoft deployment technologies including Remote
Installations
Duration
60 minutes
For More Information
Built by HynesITe, Inc
www.hynesite.biz | see what’s possible
Using ImageX to manage Windows Image Files Page 2 of 10
http://www.microsoft.com/technet/windowsvista/deploy/default.mspx
Support Information
This lab is built and supported by HynesITe, Inc. See what’s possible at
www.hynesite.biz.
How To:
Create an image of your Windows Vista installation using ImageX
Important The following steps have been provided for your information but they
will not be performed in the lab.
In this lesson you will learn to use ImageX to create a standard desktop image as a WIM
file. This enables you to distribute the image to teams which will use methods such as
Image Based Setup, WDS, SMS 2003 or other methods defined in Business Desktop
Deployment to deploy the image to client computers. Storing the image in a WIM file
also allows offline editing of the image to add additional startup commands, drivers, or
sysprep instructions.
Prepare & image an existing Windows Vista Machine.
As part of the standard imaging process for Windows Vista, the source machine must
be prepared prior to capturing an image. As part of this process, values such as the
machines unique identifier (SID) and its name are removed and the machine is
configured so that it will run a mini-setup as part of its next boot process.
c:\windows\system32\sysprep\sysprep.exe /quiet
/generalize /reboot /oobe
Note At this point SYSPREP.EXE will now prepare the machine for imaging
and then reboot it when it has completed the process. The /generalize switch is
used to remove the unique information from the machine. The /oobe switch is
used to launch the mini-setup wizard the next time the machine reboots.
• Upon rebooting into WinPE, enter the following command to change to the
C:\Program Files\Windows AIK\Tools\x86 folder
Note IMAGEX.EXE captures the C:\ drive and saves it as a bootable wim file
located in the root of the C: drive. In a real scenario, this WIM file would be
stored on a network share, or a different partition on the same workstation.
This process takes approximately 45 minutes. Upon completion of imaging,
the workstation reboots and the mini-setup wizard is run
Exercise 1
Modifying WIM Images
Once a master installation has been captured to a WIM file, it may be necessary to
modify the contents of the image. Unlike traditional image based technologies, WIM &
IMAGEX.EXE provide the ability to modify an image without first dropping the image
to a physical machine, modifying the contents of the machine and then recapturing it.
In this exercise, you will mount a WIM file, inject a new file and then commit the
changes to the WIM file. For the purposes of the lab, and to reduce wait times, a
WinPE WIM file will be used and the startnet.cmd file will be modified so that
when WinPE boots it will automatically map a network drive and apply a WIM
image to the local drive. The process for injecting a file into a WIM image of
Windows Vista is the same.
1. Once the image has been successfully mounted, open Windows Explorer and
navigate to the C:\winpe\mount\windows\system32 folder and locate the
startnet.cmd file. Open it with Notepad.
2. Add the following commands on separate lines to the Startnet.cmd file then
save the changes
map r: \\dc1\build$
r:\ImageX /apply "r:\basebuild\core.wim" 1 c:
Note: this command is provided an example but does not reflect the lab
environment.
1. Return to the command prompt and enter the following command to commit the
changes to the WIM file
2. Once the changes have been successfully committed, enter the following
command. Once complete note the time stamp on the file shows that it has just
been updated.
dir c:\winpe\winpe.wim
Exercise 2
Using Other ImageX Command-Line Switches
A legacy server is currently being re-provisioned at a remote site to be used as a network
build server for a Windows Vista pilot deployment. Unfortunately the server only has a
CD drive and the local administrator has requested that the Vista Install WIM file be
provided on CD. In this exercise you will use ImageX to split an existing WIM file into
multiple parts of a predetermined size.
ImageX.exe and the WIM file format allow technical staff an enormous range of options
when it comes to managing & manipulating images. The following exercise highlights a
number of the command line options for ImageX and how they can be used in typical
scenarios.
Use Xmage to split your image into multiple files for burning onto CDs
In this task you will use ImageX to split an existing WIM file into 600Mb segments
so that they can be distributed using standard CD-ROMs.
5. Enter the following command to create a new folder to store the files in
and then split the existing WIM file.
md e:\sources\split
6. Once the image split has been completed, review the contents of the
e:\sources\split folder and note the size of the install.wim files. Enter the
following command at the command prompt to retrieve the image
information from the WIM file and compare the Part Number value of
the new file to value returned for the original install.wim
8. In order to confirm that the files have successfully been saved in the
packages.wim file, enter the following command to view a file listing of
the image
9. After the original WIM was distributed, a request was received to add an
additional directory to the file. Enter the following command as a single
line to append a second image file to the existing packages.wim file that
contains the E:\Sources\packages
10. Now that the WIM file has been updated, you would like to get a listing
of the images that it now contains as well as the total number of files and
directories. Enter the following command and then review the output
11. After confirming that the packages.wim file now contains two separate
images, you would like to test that you can extract the files from the
second image before you distribute it. Enter the following commands to
create a new folder and then extract the contents of the second image to
the new folder
md c:\wimdemo
ImageX /apply e:\sources\packages.wim 2
c:\wimdemo
Review the contents of the c:\wimdemo folder to confirm that the files have been
extracted from the WIM file then delete the directory
12. After reviewing the contents of the second image in the packages.wim
file it has been decided that the second image should be maintained as a
separate WIM file. Enter the following command to export the second
image to a separate WIM file
13. Now that the second image has been successfully exported from the
packages.wim file, it can be deleted from the original WIM. Enter the
following command to delete the second image.