Study your flashcards anywhere!

Download the official Cram app for free >

  • Shuffle
    Toggle On
    Toggle Off
  • Alphabetize
    Toggle On
    Toggle Off
  • Front First
    Toggle On
    Toggle Off
  • Both Sides
    Toggle On
    Toggle Off
  • Read
    Toggle On
    Toggle Off
Reading...
Front

How to study your flashcards.

Right/Left arrow keys: Navigate between flashcards.right arrow keyleft arrow key

Up/Down arrow keys: Flip the card between the front and back.down keyup key

H key: Show hint (3rd side).h key

A key: Read text to speech.a key

image

Play button

image

Play button

image

Progress

1/52

Click to flip

52 Cards in this Set

  • Front
  • Back
You have a VHD file which contains a Windows 7 Enterprise installation and other data files. You want to view, but no modify the installation and data files in the VHD file.

What should you do?
- Use Wime2VHD
- Use Disk Management to attach the VHD file as read-only.
- Run imagex.exe and specify the /mount option.
- Run sysprep with the /generalize option
- Use Disk Management to attach the VHD file as read-only.

Explanation
When you attach a VHD file using Disk Management, you can specify to attach the disk as read-only.
Run imagex.exe with the /mount option to mount a read-only version of an image file. WIM2VHD creates VHD images from any Windows 7 installation source. When preparing an installation for imaging, run the sysprep /generalize command to remove machine-specific information from the installation.
Describe each command line switch for the Sysprep utility.

/audit
/generalize
/oobe
/reboot
/unattend: answerfile
/audit = Allows you to add additional drivers or applications and test your image.
/generalize = Removes machine-specific information from the installation.
/oobe = Starts the computer in the Windows Welcome mode.
/reboot = Restarts the computer when sysprep completes.
/unattend: answerfile = Applies settings in an answer file.
You need to install Windows 7 Enterprise on multiple new computers.
You decide to use Windows Deployment Services (WDS) to help automate the installation. You have installed and configured Windows 7 on the reference computer.
You need to create an install image using the reference computer.

What should you do?(Select two. Each choice is a complete solution.)
- Boot the reference computer using a capture image.
- Run dism.exe
- Run imagex.exe
- Boot the reference computer using a discover image
- Boot the reference computer using a capture image.
- Run imagex.exe

Explanation
To capture images from WDS deployment, you can boot the computer using a capture image, or you can run ImageX.
Use a discover image to boot a computer from media instead of the network to connect to the WDS server and install the operating system. Use Deployment Image Servicing and Management (DISM) to mange and maintain system images. DISM does not capture images.
You decide to use a system image to deploy Windows 7 to multiple computers.
You have installed Windows on a reference computer. You need to restart Windows and manually install applications and make other changes prior to capturing the image.
You want to prevent the Windows Welcome screen from showing when the system reboots prior to customizing the installation. You do not want any changes you make to prevent the end-user from seeing the full Out-of_Box Experience after the image is applied.

What should you do?
- Run Sysprep with the /audit option
- Run Sysprep with the /unattend option
- Run Sysprep with the /oobe option
- Run Sysprep with the /generalize option
- Run Sysprep with the /audit option

Explanation
/audit forces the computer to start in Audit mode instead of Windows Welcome mode. In Audit mode, also known as reseal mode, you can add additional drivers or applications and test your image after deploying it.
Run the Sysprep /generalize command to remove machine-specific information from the installation. This process runs the generalize pass of Windows Setup which removes the SID, clears logs and restore points, and removes other machine-specific information.
/oobe starts the computer in the Windows Welcome or out-of-box experience mode. This allows a user to customize their system, such as creating accounts and setting the computer name.
/unattend followed by the path and filename specifies the answer file to use when Windows Setup resumes at the next restart. Use this option if you are using a custom answer file (not named Autounattend.xml or Unattend.xml) for specific installation stage or a file in a location that is not searched automatically
You need to deploy Windows 7 Enterprise to multiple new computers. You have an image that you have previously captured.You have mounted and dismounted the image several times. You want to reduce the overall size of the image file by removing unnecessary resource files from the image file.

What should you do?
- Run imagex /export.
- Run imagex /capture /split.
- Run imagex /apply /ref.
- Run imagex /capture.
- Run imagex /export.

Explanation
Use the imagex /export command to delete unnecessary resources from the image file, reducing its size.
Run imagex /capture on the reference computer to capture the image. Run imagex /split to split the captured image into multiple files. Run imagex /apply /ref to deploy the image using the split files. You run this command once and identify the names of the split files.
You need to deploy Windows 7 Enterprise to multiple new computers using a previously-captured system image.
Before deploying the image, you need to append several files to the image. You want to compress the append files to minimize disk space.

What should you do? (Choose the most correct answer.)
- Use the fast compression type.
- Use the same compression type as the initial capture.
- Use the none compression type.
- Use the maximum compression type.
- Use the same compression type as the initial capture.

Explanation
You can use only a single compression type for a .wim file. Append image files must use the same compression type as the initial capture. The imagex /compress command specifies the type of compression used for the initial capture operation.

The maximum options provides the best compression but takes the longest time to capture the image
The fast option provides faster image compression but the resulting files are larger than those compressed with the maximum option. This is also the default compression type, used if you leave this parameter blank.
The none option does not compress the captured image at all.
You want to deploy Windows 7 Enterprise to multiple computers from a previously-captured system image.
You have received an updated application and would like to add the application to the existing install image without recapturing the entire image.

What should you do?
- Run DISM with the /add-apps option.
- Run Windows SIM with install.wim
- Run MDT 2010 with the Distribution share.
- Run Sysprep with the /unattend option
- Run MDT 2010 with the Distribution share.

Explanation
If you have a previously-captured system image, you can use Microsoft Deployment toolkit (MDT 2010) to install applications to the image. Use the Distribution share of MDT to add, remove, and configure the following:
*Operating systems
*Applications
*Operating system packages, including updates and language packs
*Out-of-box (third-party) device drivers

Use Sysprep and the /unattend option to specify the answer file to use when Windows Setup resumes at the next restart. When creating a custom install image, you run Sysprep on the reference computer before capturing the operating system image. Use Windows SIM and the install.wim file to create and manage response files used for unattended installations. Use Deployment Image Servicing and Management (DISM) to add drivers or operating system updates to a previously-captured system image.
You have a computer that runs Windows 7 Ultimate and a VHD file which contains a Windows 7 installation.
You need to boot the computer from the VHD file.

What should you do?
- Press F8 at startup and wait for the option to boot from a VHD.
- From Diskpart, run select vdisk.
- Run BCDEdit and modify the BCD boot entries.
- Run Bootcfg.exe and specify the /default parameter
- Run BCDEdit and modify the BCD boot entries.

Explanation
To configure a computer to boot from a new VHD, use BCDEdit to create a new BCD boot entry and set the default operating system.
Bootcfg.exe served essentially the same purpose as BCDEdit.exe on earlier versions of Windows, and is not available on Windows 7. DiskPart is a text-mode command prompt tool used to manage disks, partitions, or volumes (known as objects). Diskpart does not set the default operating system location. Pressing F8 gives you the advanced startup options including safe mode and debugging mode, but will not display the VHD as an option.
Describe each component of the Windows Automated Installation Kit.

*WinPE
*Windows SIM
*Sysprep
*ImageX
*DISM
*Oscdimg
WinPE = A thin version of Windows
Windows SIM = Creates and manages answer files that are used for automated installations
Sysprep = Removes machine specific information
ImageX = Creates an image file for deployment from a reference (source) computer
DISM = Deployment Image Servicing and Management applies updates, drivers, and language packs to Windows image
Oscdimg = Creates ISO images
You want to make custom modification to the installation such as installing applications and modifying desktop settings. You then want to create an image of the installation while retaining the custom changes.

What should you do?
-
1. Add the install image from the Windows 7 installation DVD to WDS.
2. Run the ImageX command with the /mountrw command to mount the image to an empty directory.
3. Run the Peimg /inf command to customize the image.
4. Run the ImageX /unmount command with the /commit switch
-
1. Create a discover image and burn it to a DVD.
2. Install the operating system on the reference computer. Customize the installation.
3. Run Sysprep on the reference computer.
4. Boot the reference computer using the discover image DVD
-
1. Add the install image from the Windows 7 installation DVD to WDS.
2. Boot the reference computer using the install image.
3. Customize the installation.
4. Create a capture image from the reference computer.
-
1. Create a capture image in WDS.
2. Install the operating system on the reference computer. Customize the installation.
3. Run sysprep on the reference computer.
4. PXE boot the reference computer and select the capture image.
1. Create a capture image in WDS.
2. Install the operating system on the reference computer. Customize the installation.
3. Run sysprep on the reference computer.
4. PXE boot the reference computer and select the capture image.

Explanation
1. Create and capture image and add the capture image back into the WDS console.
2. Install the operating system on the reference computer. Customize the installation.
3. Run sysprep on the reference computer to prepare it for imaging.
4. When the reference computer reboots, it connects to the WDS server. select the capture image to start the Capture Image Wizard. This wizard creates the install image based on the reference computer and adds it back to the console.

Use ImageX to add drivers or operating system updates without recapturing the install image. However, you cannot use this tool to install applications into an existing image. Use discover image to boot a computer that is not PXE-capable so it can connect to the WDS server.
You have a single computer without an operating system installed.
The computer will eventually store sensitive information and will require the encryption of the operating system partition.
You have a previously-captured image which contains a Windows 7 Enterprise installations. The image is on a network share. You want to manually deploy the image to the computer.

What should you do?
-
1. Boot the new computer using the Windows 7 installation DVD.
2. Use Diskpart to create a system partition for the Windows 7 image.
3. Use ImageX to apply the image to the local drive.

-
1. Boot the new computer using the Windows 7 installation DVD.
2. Use Diskpart to create a BitLocker partition.
3. Use Diskpart to create a system partiion for the Windows 7 image.
4. Use ImageX to apply the image to the local drive.

-
1. Boot the new computer using WinPE.
2. Use Diskpart to create a BitLocker partition.
3. Use Diskpart to create a system partition for the Windows 7 image.
4. Use ImageX to apply the image to the local drive.
-
1. Boot the new computer using WinPE.
2. Use Diskpart to create a system partition for the Windows 7 image.
3. Use ImageX to apply the image to the local drive.
1. Boot the new computer using WinPE.
2. Use Diskpart to create a BitLocker partition.
3. Use Diskpart to create a system partition for the Windows 7 image.
4. Use ImageX to apply the image to the local drive.

Explanation
1. Boot the new computer using WinPE
2. Use Diskpart to create a BitLocker partition. BitLocker will encrypt the entire contents of the operating system partition.
3. Use Diskpart to create a system partition for the Windows 7 image.
4. Use ImageX to apply the image to the local drive

Boot the computer to Windows 7 DVD for clean (custom) and upgrade installations, or to the repair the installation.
You have a computer running Windows 7 Ultimate.
To deploy Windows 7, you want to use the Windows 7 installation on this computer as a system image.
After removing the machine-specific information from the computer, you are ready to capture the image as a WIM file.

What should you do?
- Boot to Windows PE and use ImageX to capture the Windows installation onto a network share.
- Boot to Windows 7 and use DISM to capture the Windows installation onto a network share.
- Boot to Windows 7 and use ImageX to capture the Windows installation onto a network share.
- Boot to Windows 7 and use Windows SIM to capture the Windows installation onto a network share.
- Boot to Windows PE and use ImageX to capture the Windows installation onto a network share.

Explanation
In this scenario, you should boot to Windows PE and use ImageX to capture the Windows installation onto a network share. Windows PE is a thin version of Windows 7 that you can use to install and troubleshoot a Windows 7 installation. When you create the Windows PE boot disc, you include the ImageX tool. Once booted into Windows PE, you use ImageX to create the image from a reference computer. ImageX saves the reference computer's installation as a Windows Image (WIM) file.
You cannot capture a system image while the computer is running the installation you want to capture. use Windows System Image Manager (Windows SIM) to create and manage answer files that are used for automated installations. use Deployment Image Servicing and Management (DISM) to apply updates, drivers, and language packs to a Windows image.
You need to deploy Windows 7 Professional to multiple new computers using a previously-captured system image.
You mount the image and use Dism to make several changes to the image.
You decide not to keep any of the changes you have made to the image. The image is still attached.
You want to undo the changes with the least amount of effort.

What should you do?
- Create an Unattend file. Edit the offlineServicing section to undo the changes. Apply the Unattend file to the image.
- Run Dism with the /cleanup-wim option
- Run Dism with the /remount-wim option
- Run Dism with the /unmount-wim and /discard options
- Run Dism with the /unmount-wim and /discard options

Explanation
Changes made to an image using Dism are not saved until they are committed. To undo all changes made since the last changes were committed, unmount the image using the /discard option.
While you might be able to undo changes using an Unattend file, it would take more time than just dismounting the image. use the /cleanup-wim option to delete resources associated with an abandoned image. use the /remount-wim option to remount a WIM file that has become inaccessible.
You need to install Windows 7 on 20 computers.
You would like to automate the installation process as much as possible. After booting each destination computer, you would like to complete all of the following automatically (in this order):
1. Partition and format the hard disk
2. Install Windows from a custom image
3. Following installation of the image, applying Windows updates
4. Install applications
5. Enable BitLocker

What should you do?
- Use Microsoft Deployment Toolkit (MDT)
- Use Windows Deployment Services (WDS)
- Use Deployment Image Servicing and Management (DISM)
- Use ImageX with a custom Unattend.xml file
- Use Microsoft Deployment Toolkit (MDT)

Explanation
Microsoft Deployment Toolkit (MDT 2010) is a tool used to deploy operating systems and applications. You can use MDT to help create Unattend files used for Windows installations, as well as automate tasks that occur before and after installation or after applying an image. MDT uses tasks and task sequences to define the actions to take. MDT is often used in conjunction with WDS; MDT runs scripts before the image is applied, WDS then applies the image to the computer, and then MDT performs additional tasks following the application of the image.
Use WDS to apply images to computers; WDS does not run tasks following applying the image. Use DISM to manage and update system images. You can use an Unattend file to automate the installation process; however, the file does not perform tasks following installation.
You have a computer without an operating system installed.
You have a previously-captured image which contains a Windows 7 Enterprise installation. The image is on the following network share: \\imgserv\images.
You need to manually deploy the image onto the computer.
You boot the computer using WinPE and map a drive to the network share.

What should you do next?
- Run Diskpart to partition and format the disk.
- Use imagex.exe with the /mount option to apply (mount) the image to the local drive.
- Run oscdimg.exe \\imgserv\images to create an ISO from the system image.
- Use imagex.exe with the /apply option to copy the image from the network share to the local drive.
- Run Diskpart to partition and format the disk.

Explanation
Before you can apply the image to the computer, you need to partition and format the hard disk. Then you apply the install image to the disk using the ImageX command.
To make the contents of an image accessible for viewing, use imagex.exe with the /mount option. use oscdimg.exe to create an ISO image for bootable Windows PE disc.
You need to deploy Windows 7 Enterprise to multiple new computers using a previously-captured system image.
Before deploying the image, you insert the third-party drivers from the C:\Drivers\Network and C:\Drivers\Custom directories into the image.

What should you do? (Select two. Both answers are complete solutions.)
- At the command prompt, run dism /get-drivers /driver:c:\drivers /recurse
- At the command prompts, run dism /add-driver /driver:c:\drivers\network /driver:c:\drivers\custom
- At the command prompt, run dism /add-driver /driver:c:\drivers /recurse
- At the command prompt, run dism /get-drivers /all /driver:c:\drivers
- At the command prompts, run dism /add-driver /driver:c:\drivers\network /driver:c:\drivers\custom
- At the command prompt, run dism /add-driver /driver:c:\drivers /recurse

use /get-drivers to display basic information about all out-of-box drivers on the image. use /get-drivers /all to display basic information about all drivers on the image, in addition to the all out-of-box drivers
Section 2.5
Explanation
To update a previously-captured image with third-party drivers, use the following dism command options:
/add-driver /driver:(path); adds all of the drivers in the directory
/add-driver /driver:(path) /recurse adds all of the drivers in the directory and its subdirectories
You have a computer that runs Windows 7 Enterprise.
You want to configure the computer to boot to a Windows 7 installation on a VHD file.
You have downloaded the Windows AIK tools. you create and attach a virtual disk file using Disk Management.

What should you do next?
- Run ImageX to apply the install.wim image to the VHD.
- Run BCDBoot to copy boot files to the VHD file.
- Run Diskpart and configure the partition in the VHD as active.
- Run ImageX to apply the boot.wim image to the VHD.
- Run ImageX to apply the install.wim image to the VHD.

Explanation
After the VHD file is created and attached, use ImageX to apply the .wim file to the virtual disk. The install.wim file contains the Windows operating system. The boot.wim file contains a Windows PE boot environment; however, you cannot boot to Windows PE using an attached VHD file.
You do not need to run BCDBoot to copy boot files to the VHD file or make the partition inside the VHD file active because the computer does not run the BOOTMGR file from the VHD (BOOTMGR runs from the current disk partition). To boot to the installation on the VHD file, you will need to modify the BCD store to point o the installation in the VHD file.
Section 2.6
You have a computer tha runs Windows 7 Enterpirse.
You have a VHD file that contains a Windows 7 image. You need to perform offline servicing of the image in the VHD file.
You attach the VHD file and use Dism to make several changes.
You decide not to keep any of the changes you have made to the image on the VHD file. The VHD file is still attached.

What should you do?
- Run Diskpart, then detach.
- Create an Unattend file. Edit the offlineServicing section to undo the changes. Apply the Unattend file to the image.
- Run Dism /unmount-wim with the /discard option.
- Run Diskpart, then detach. Restore the VHD file from a backup.
- Run Diskpart, then detach. Restore the VHD file from a backup.

Explanation
Changes you make to the VHD file are saved immediately and cannot be undone using the /unmount-wim option with Dism. To undo changes, you will need to use Dism to remove the changes, or restore the .vhd file from a backup after detaching the VHD file.
When running Dism to make offline changes to an image that is not part of a VHD file, you can simply unmount the image without committing the changes ( only committed changes are saved).
Section 2.6
Last month you deployed Windows 7 Enterprise to all of the desktop computers in your company using a single system image. To install this image, you created a WinPE boot CD.
You recently received new desktop computers, and one of your colleagues is not able to install the image using the WinPE CD. The WinPE Cd cannot boot to the network drive.

What should you do?
- Create a new WinPE image using one of the new desktop computers.
- Manually install Windows 7 Enterprise from the product DVD on the new desktop computers.
- Manually install Windows 7 Enterprise from the product DVD on one of these new desktop computers. Create a new image. use this image for all the other new desktop computers.
- Install the latest hardware drivers for these new desktop computers on the WinPE image.
- Install the latest hardware drivers for these new desktop computers on the WinPE image.

Explanation
You need to add the latest hardware drivers to the WinPE image. The WinPE image supports only a limited number of network cards. If these new desktop computers contain a new network card that is currently not supported, you need to add this new driver to your WinPE image.
Taking this action is the quickest way to modify the image to include the necessary files. Reinstalling 7 Enterprise requires extra work, while installing manually will not use the image file.

Section 2.2
You need to deploy Windows 7 Professional to multiple new computers using a previously-captured system image.
Before deploying the image, you need to make sure there is a specific Windows application on the image.

What should you do? (Select two. Both answers are complete solutions.)
- At the command prompt, run dism /get-apppatches
- At the command prompt, run dism /get-apppatchinfo
- At the command prompt, run dism /get-apps
- At the command prompt, run dism /get-appinfo
- At the command prompt, run dism /get-apps
- At the command prompt, run dism /get-appinfo

Explanation
To display a list of all Windows application (.msi) files available on the image, use the following dism command options:
/get-appinfo displays detailed information for all the installed MSI applications.
/get-apps displays all MSI applications installed on the offline image, as well as the GUID.

use /get-apppatches to display a list of application patches (.msp) files that are available on the image. use /get-apppatchinfo to display detailed information about all installed application patches.

Section 2.5
You need to deploy Windows 7 Professional to multiple new computers using a previously-captured system image.
You have created an answer file called Win7ProfAnswer.xml in the E:\Image\AnswerFiles folder. You want to apply the answer file to the image.

What should you do?
- At the command prompt, run dism /apply:e:\images\answerfiles\Win7ProfAnswer.xml
- At the command prompt, run dism /apply-answer:e:\images\answerfiles\Win7ProAnswer.xml
- At the command prompt, run dism /apply-unattend:e:\images\answerfiles\Win7ProfAnswer.xml
- At the command prompt, run dism /cleanup-image:e:\images\answerfiles\Win7ProfAnswer.xml
- At the command prompt, run dism /apply-unattend:e:\images\answerfiles\Win7ProfAnswer.xml

Explanation
use the dism.exe /apply-unattend: option to apply an unattend.xml file to an image. When you use DISM to apply an unattend.xml answer file to an image, the unattended settings in the offlineServicing configuration pass are applied to the Windows image.
Use the /cleanup-image and /revertpendingactions options to revert all pending actions from the previous servicing operations because the actions might be the cause of the boot failure.

Section 2.5
You have a computer without an operating system installed.
You have a previously-captured image which contains a Windows 7 enterprise installation. The image is on the following network share: \\imgserv\images.
You need to manually deploy the image onto the computer.
After booting the computer into WinPE, you partitioned and formatted the local hard drive with DiskPart.

What should you do next? (Select two. Each choice is a required part of the solution.)
- Use imagex.exe with the /mount option to apply (mount) the image to the local drive.
- Run oscdimage.exe \\imgserv\images to create an ISO from the system image.
- Use imagex.exe with the /apply option to copy the image from the network share to the local drive.
- Use the net use command to connect to the network share and map the drive with a letter.
- Use imagex.exe with the /apply option to copy the image from the network share to the local drive.
- Use the net use command to connect to the network share and map the drive with a letter.

Explanation
In this scenario, you should:
1. Use the net use command to connect to the network share and map the drive with a letter.
2. use imagex.exe with the /apply option to copy the image from the network share to the local drive.
To make the contents of an image accessible for viewing, use imagex.exe with the /mount option. use oscdimage.exe to create an ISO image for bootable Windows PE disc

Section 2.4
You want to deploy Windows 7 Enterprise to multiple computers from a previously-captured system image.
You have received some operating system updates and would like to add these to the existing install image without recapturing the entire image.

What should you do?
- Run Sysprep
- Run DISM
- Run Windows SIM
- Run USMT
Explanation
If you have a previously-captured system image, you can use Deployment Image Servicing and Management (DISM) to add drivers or operating system updates without recapturing the install image. use DISM to:
* Apply Windows updates, drivers, and language packs to a WIM file.
*Upgraded a Windows image to a different edition.
*Enable or disable Windows features

Use Sysprep to prepare a Windows installation for imaging by removing machine-specific information. When creating a custom install image, you run Sysprep on the reference computer before capturing the operating system image. use Windows SIM to create an d manage response files used for unattended installations. use User State Migration Tool (USMT) to migrate user profiles and user data to a new computer or back to an old computer once it has been upgraded to Windows 7.

Section 2.5
Describe each option for the ImageX utility.

/capture
/config
/compress
/split
/apply
/verify
/capture = Captures the volume image on the reference computer to a new .wim file
/config = identifies an alternate configuration file name and location (when using a file other than wimscript.ini in the same directory as ImageX).
/compress = Specifies compression when capturing the system image.
/split = Splits the captured image into multiple files.
/apply = deploys the image.
/verify = Checks for errors and file duplication

Section 2.3
You have a computer that runs Windows 7 Enterprise.
You have created a VHD file that contains a Windows 7 image.
You need to perform offline servicing of the image in the VHD file to add a driver and enable some Windows features.
You attach the VHD file. You use Dism to add a driver.
You realize the driver should not have been added to the image. You need to undo the changes you have made using the least amount of effort possible. The VHD file is still attached.

What should you do?
- Run Diskpart, then detach. restore the VHD file from a backup.
- Run Dism /unmount-wim with the /discard option.
- Run Dism /Remove-Driver.
- Run Diskpart, then detach.
- Run Dism /Remove-Driver.

Explanation
Changes you make to the VHD file are saved immediately and cannot be undone using the /unmount-wim option with the Dism. To undo changes, you will need to use Dism to remove the changes, or restore the .vhd file from a backup after detaching the VHD file.
When running Dism to make offline changes to an image that is not part of a VHD file, you can simply unmount the image without committing the changes (only committed changes are saved).

Section 2.6
You have been put in charge of installing Windows 7 on 15 new computers.
You use Windows Deployment Services (WDS) to install the operating system on ten of the computers. You find, however, that the remaining five computers do not have the PXE support.
You need to install Windows 7 on the remaining five computers with as little effort as possible.

What should you do?
- Run Windows SIM to create a custom unattend installation file that includes the necessary settings for the remaining five computers. Add the resulting file to the WDS server. On the remaining five computers, connect to the WDS server and use the unattend file to complete the installation.
- Create a discover boot image and convert it to an ISO image. Burn the ISO image to CD. Boot each computer to the CD, connect to the WDS server, and complete the installation.
- install windows 7 on one of the computers. Create a capture image, and use the capture image to create a custom install image using that computer. On the remaining four computers, connect to the WDS server and use the custom image to complete the installation.
- On each reaming computer, perform a manual installation of Windows 7
- Create a discover boot image and convert it to an ISO image. Burn the ISO image to CD. Boot each computer to the CD, connect to the WDS server, and complete the installation.

Explanation
A computer that is not PXE capable is unable to perform a network boot. Because it can't boot from the network, it can't download a boot image from the WDS server. For non-PXE computers, use a discover image. The discover image is placed on media, such as a CD or USB drive, and is used to boot the computer into Windows PE. The computer can then connect to the WDS server to download the necessary install image.
Creating a custom install image is not necessary, because install images do not depend on minor differences in the hardware (only the architecture is important). Even if you created a custom install image or answ2er file, without PXE capabilities or bootable device, the non-PXE servers will be unable to connect to the WDS server to download the install image.

Section 2.7
You have a computer that runs Windows 7 Enterprise.
You want to configure the computer to boot to a Windows 7 installation on a VHD file. You will use the install.wim image on the Windows installation disc. Your computer does not have the Windows AIK installed.
You create and attach a virtual disk file using Disk Management. You need to apply the Windows image file to the virtual disk.

What should you do?
- Run Diskpart.
- Run the Install-WindowsImage.ps1 PowerShell script.
- Run ImageX.
- Run WIM2VHD.
- Run the Install-WindowsImage.ps1 PowerShell script.

Explanation
You can use the following tools to apply the Windows 7 image to the VHD:
* The Install-WindowsImage.ps1 PowerShell script. using this script does not require the Windows AIK.
* ImageX. You must have the Windows AIK to use ImageX.

In addition to these tools, you can use WIM2VHD to create and attach a VHD file and apply an image to the file. WIM2VHD requires the Windows AIK, and creates a VHD as it runs (you cannot use WIM2VHD to apply an image to an existing VHD file).

Use Diskpart to create and attach the VHD.

Section 2.6
You need to deploy Windows 7 Professional to multiple new comptuers using a previously-captured system image on a network share.
You have updated the offline image with a Windows UPdate Stand-alone Installer (.msu) file.
You believe the new .msu file is causing a problem on the system image.

What should you do?
- Use the dism /cleanup-image and /revertpendingactions options.
- Use the dism /remount-wim option
- Use the dism /remove-package option
- Use the dism /get-mountedwiminfo option
- Use the dism /cleanup-image and /revertpendingactions options.

Explanation
use the dism /cleanup-image and /revertpendingactions options to revert all pending actions from the previous servicing operations if the actions might be the cause of a boot failure. The /revertpendingactions option is not supported on a running operating sytem or a Windows PE image.
use the dism /remove-package options to remove a specific cabinet (.cab) file. This option cannot remove a Windows Update Stand-alone Installer (.msu) file. use the dism /remount-wim option to remount the WIM file if the mount directory is lost or orphaned. use the dism /get-mountedwiminfo option to list all the currently-mounted images and information about each image, such as the mounted path, index, location and read/write permissions.

Section 2.5
You want to deploy Windows 7 to multiple computers using a system image.
You would like to use an answer file to automate the installation process on a reference computer.

What should you do first?
- Run ImageX.
- Run Windows Deployment Services console.
- Run Windows System Image Manager (Windows SIM).
- Run Sysprep
- Run Windows System Image Manager (Windows SIM).

Explanation
use the Windows System Image Manager (Windows SIM) to create and edit answer files. Windows SIM is included int he Windows Automated Installation Kit (WAIK). To create the answer file, run Windows SIM and load an install image. After loading the image, select and edit the responses to the questions presented during production installation.
use ImageX to create an image from a reference computer. use the Windows Deployment Services console to manage images used with WDS installations. use Sysprep to manager system images and Windows installation process.

Section 2.2
You have a comptuer running Windows 7 Ultimate. You will use this comptuer as a reference comptuer to install Windows 7 from a system image.
You have already used Sysprep to remove machine-specific information from the reference computer.
You need to capture the image using compression, but excluding some file types from being compressed.
You create a file named myCaptureSettings.ini to identify the compression settings. You need to edit the compression settings in the file.

What should you do? (Choose the best answer.)
- Identify files to compress using the CompressionList section, and files not to compress using the CompressionExclusionList section.
- Identify files that are not compressed using the CompressionExclusionList section.
- Identify files to compress using the CompressionList section, and files not to compress using the ExclusionList section.
- Identify files to compress using the CompressionList section, and files not to compress using the ExclusionExceptionList section
- Identify files that are not compressed using the CompressionExclusionList section.

Explanation
You can use a configuration file to customize the ImageX capture process. The file uses the .ini format. Use the [CompressionExclusionList] section uncompressed.
use the [ExclusionList] section to identify files not included in the image when it is captured. use the [ExclusionExceptionList] section to identify files that are included, even if they match criteria defined in the ExclusionList section.

Section 2.3
You manage a computer that runs Windows 7 Enterprise edition.
You would like to boot the computer to a VHD file that contains a Windows 7 installation.
You will use the install.wim file from Windows installation disc to create the VHD file. You would also like to apply updates to the image.

What should you do?
- Run WDS
- Run MDT 2010
- Run BCDEdit
- Run WIM2VHD
- Run WIM2VHD

Explanation
WIM21VHD can be used to create a VHD file, apply the .wim image to the VHD, and then apply updates to the VHD.
BCDEdit is a command-line tool used to manage BCD stores. Microsoft Deployment Toolkit (MDT 2010) is a tool used to deploy operating systems and applications. Windows Deployment Services (WDS) is a server role that enables the deployment of Windows operating systems to client and server computers.

Section 2.6
You have a computer running Windows 7 Ultimate. You will use this computer as a reference computer to install Windows 7 from a system image.
You have already used Sysprep to remove machine-specific information from the reference computer.
You need to capture the image using compression, but excluding some file types from being compressed.
You create a file named myCaptureSettings.ini to identify the compression settings.

What should you do?
- Run imagex.exe with the /capture, /compress, and config options
- Run imagex.exe with the /capture and /compress options
- Run imagex.exe with the /capture, /compress, and /exclude options.
- Run imagex.exe with the /capture, /config, and /exclude options
- Run imagex.exe with the /capture, /compress, and config options

Explanation
You can use a configuration file to customize the ImageX capture process. The file uses the .ini format
* use the [CompressionExclusionList] section to identify files that are not compressed. When running ImageX, use the /compress option to use compression when capturing the system image.
* use the [ExclusionList] section to identify files not included in the image when it is captured
* use the [ExclusionExceptionList] section to identify files that are included, even if they match criteria defined int he ExclusionList section.

When you run imagex.exe on the reference computer, it will automatically recognize the wimscript.ini file if you save the wimscript.ini file in the same directory as ImageX. use the /config option to identify an alternate configuration file name and location.
Imagex.exe does not have an /exclude option.

Section 2.3
You have just been put in charge of installing Windows 7 on 30 new workstations.
You decide to use Windows Deployment Services (WDS) to help automate the installation.
You need to create a custom install image from a reference computer that you have configured.

What should you do? (Select two. Each choice is a possible solution.)
- Run RIPrep.
- Boot the reference computer using a capture image.
- Boot the reference computer using a discover image.
- Run ImageX
- Boot the reference computer using a capture image.
- Run ImageX

Explanation
to create images for WDS deployment, you can boot the computer using a capture image, or you can run ImageX.
use a discover image to boot a computer from media instead of the network to connect to the WDS server and install the operating system. use RIPrep to create images for use the Remote Installation Services (RIS)

Section 2.4 and 2.7
You need to install Windows 7 to multiple computers on your network.
You would like to use windows Deployment Services (WDS) to deploy a custom image to all computers. The computers do not have a PXE-compliant network cards.

What should you do?
- Place a capture boot image on the WDS server. Boot each computer using a USB drive that contains a capture boot image with the Windows PE.
- Place an install image on the WDS server. Boot each computer using a CD that contains a discover boot image with Windows PE.
- Place a capture boot image on the WDS server. Boot each computer using a CD that contains a boot image with Windows PE.
- Place an install image on the WDS server. Boot each computer using a USB drive that contains a boot image with Windows PE.
- Place an install image on the WDS server. Boot each computer using a CD that contains a discover boot image with Windows PE.

Explanation
A discover boot image is an image that is placed on removable media (such as a CD, DVD, or USD drive) that can be used by non-PXE clients to boot and locate a WDS server. After the computer boots using the discover image, it contacts the WDS server and installs Windows using the install image.
A boot image is a minimal operating system (Windows PE) that is sent to the client when it is first connects to the WDS server. The boot image is placed on the WDS server and is loaded by computers that can boot from the network using a PXE-compliant network card. A capture boot image is an image that you use to boot a reference computer and capture the installation to create custom install images.

Section 2.7
You have a computer that runs Windows 7 Enterprise.
You want to configure the computer to boot to a Windows 7 installation on a VHD file. You will use the install.wim image on the Windows installation disc.
You have downloaded the Windows AIK tools. You create and attach a virtual disk file using Disk Management. You run ImageX to apply the image to the VHD file.

What should you do next?
- Run BCDBoot to copy boot files to the VHD file.
- Run BCDEdit to create a BCD entry pointing to the VHD file.
- Run ImageX to apply the boot.wim image to the VHD.
- Run Diskpart and configure the partition in the VHD as active
- Run BCDEdit to create a BCD entry pointing to the VHD file.

Explanation
After the VHD file is created and the image is applied, run BCDEdit to create a BCD entry pointing to the VHD file. The computer boots using the BOOTMGR from the existing partition, then looks in the BCD database for available Windows installation. during startup you can select the VHD installation as the operating system to start, or modify the BCD entry to use the VHD file by default.
You do not need to run BCDBoot to copy boot files to the VHD file or make the partition inside the VHD file active because the computer does not run the BOOTMGR file from the VHD (BOOTMBR runs form the current disk partition). The boot.wim file contains a Windows PE boot environment; however, you cannot boot to Windows PE using an attached VHD file.

Section 2.6
As part of your responsibilities, you manage multiple VHD files that contain bootable Windows images.
You need to make multiple changes to the image within each of the VHD files. Each image will get the same list of updates. You want to update the images without booting to each VHD file.
You attach each VHD file.

What should you do next?
- Create an Unattend file with entries in the offlineServicing section. Run Dism to apply the file to each image.
- Create an Unattend file with entries in the auditSystem section. Run Dism to apply the file to each image.
- Create an Unattend file with entries int he specialize section. Run Dism to apply the file to each image.
- Create an Unattend file with entries in the oobeSystem section. Run Dism to apply the file to each image.
- Create an Unattend file with entries in the offlineServicing section. Run Dism to apply the file to each image.

Explanation
You can perform multiple actions by applying an Unattend file to the offline image. When using this method, insert the changes you want to apply in the offlineServicing section of the Unattend file. With the file created, use the /Apply-Unattend option to use the file to update the image

Each of the other sections are only applied while installation is online

Section 2.6
You have a computer tha runs Windows 7 Professional and a VHD file which contains a Windows 7 installation.
You need to boot the computer from the VHD file.

What should you do first?
- Run the Bootcfg.exe and specify the /default parameter.
- Upgrade to Windows 7 Ultimate.
- Use the Disk Management and attach the VHD.
- Press F8 at startup and wait for the option to boot from a VHD.
- Upgrade to Windows 7 Ultimate.

Explanation
Before you can boot to VHD, you must upgrade to the Windows 7 Ultimate edition. Windows 7 Professional does not support booting to VHD.
Pressing F8 gives you the advanced startup options including safe mode and debugging mode, but will not display the VHD as an option

Section 2.6
You want to use the Microsoft Deployment Toolkit (MDT 2010) to deploy Windows 7 to several new computers.
You have a previously-captured image which contains the Windows 7 installation and several custom applications.
if possible, you would like to deploy the image to all of the computers with no intervention required by the user.
You do not have a Microsoft SQL server.

What should you do?
- Use the Zero Touch Installation (ZTI) installation method.
- use unicast to transmit a separate image to each individual client.
- Use the Lite Touch Installation (LTI) installation method.
- Use ImageX to apply the image form the network share.
- Use the Lite Touch Installation (LTI) installation method.

Explanation
In this case, you should use the Lite Touch Installation (LTI) as the distribution method. Lite Touch Installation (LTI) distributes an image with a small amount of user intervention. LTI may be used without requiring any other distribution tools.

Zero Touch Installation (ZTI) is a method of distribution that requires no user intervention; however, to use ZTI you need Microsoft SQL server and Microsoft System Center Configuration Manager (SCCM) 2007 with the Operating System Deployment Feature Pack. Use Image X to capture a Windows 7 installation onto a network share or mount an image so that it can be modified. WDS does not use ImageX to deploy the image to the destination computers.

WDS supports unicast transmissions to deploy images

Section 2.7
You have a computer running Windows 7 Ultimate.
Prior to capturing the system image, you need to remove machine-specific information from the installation

What should you do?
- At the command prompt, run sysprep.exe /oobe
- At the command prompt, run sysprep.exe /quiet
- At the command prompt, run sysprep.exe /generalize
- At the command prompt, run sysprep.exe /unattend
- At the command prompt, run sysprep.exe /generalize

Explanation
use sysprep with the /generalize option to remove machine-specific information from the installation. This removes the SID, clears logs and restore points, and removes other machine-specific information.
Use /unattend to specify the answer file when Windows Setup resumes at the next restart. Use /quiet to suppress on-screen messaging when using an answer file. use /oobe to start the computer in the Windows Welcome or Out-of-box experience mode

Section 2.2
You have a computer running Windows 7 Enterprise.
You plan to capture the installation on this computer and use the image to deploy to other computers.
You create an answer file named win7ent_answers.xml with Windows SIM. You now want to remove computer-specific information and apply the settings in the answer file before you capture the installation.

What should you do?
- At the command prompt, run sysprep.exe /audit /unattend:win7ent_answer.xml.
- At the command prompt, run sysprep.exe /generalize /oobe win7ent_answer.xml
- At the command prompt, run sysprep.exe /audit /oobe /unattend:win7ent_answer.xml
- At the command prompt, run sysprep.exe /generalize /oobe /unattend:win7ent_answers.xml
- At the command prompt, run sysprep.exe /generalize /oobe /unattend:win7ent_answers.xml

Explanation
For this scenario, use sysprep.exe with the following options:
* Use /generalize remove machine-specific information from the installation. This removes the SID, clears logs and restore points, and removes other machine-specific information.
* use /oobe to start the computer in the Windows Welcome or out-of-box experience mode. This allows the computer to use the answer file during the installation.
* Use /unattened to specify the answer file when Windows Setup resumes at the next restart. You need this option because the answer file is not Autounattend.xml or Unattend.xml.

To force the computer to stat in Audit mode instead of Windows Welcome mode, use the /audit option. In Audit mode, also known as reseal mode, you can add additional drivers or applications and test your image after deploying it.

Section 2.2
You have a computer running Windows 7 Enterprise.
You want to create a VHD file with the following settings:
* Size = 200 GB
* Location = F:\VHDS
* Name = Win7vhd

What should you do?
- Using DiskPart, type create vdisk file=f:\VHDS\Win7vhd maximum=204800
- Using DiskPart, type create vdisk file=f:\VHDS\Win7vhd.vhd maximum=204800
- Using DiskPart, type create vdisk file=f:\VHDS\Win7vhd maximum = 200
- Using DiskPart, type create vdisk file =f:\VHDS\Win7vhd.vhd maximum = 200
- Using DiskPart, type create vdisk file=f:\VHDS\Win7vhd.vhd maximum=204800

Explanation
To create the VHD file according to the scenario, run DiskPart and type create vdisk file=f:\VHDS\WIn7vhd.vhd maximum=204800. Be aware that the name of the VHD file should include the .vhd extension, and the size of the VHD file is expressed in MB

Section 2.6
You have a computer that runs Windows 7 Enterprise.
You have created a VHD file that contains a Windows 7 image.
You would like to perform offline servicing of the image in the VHD file to add a driver and enable some Windows features.

What should you do?
- Use Dism to mount the image. use Dism to modify the image. Use Dism to commit the changes and unmount the image.
- Use Diskpart to attach the VHD file. Use Dism to modify the image. Use Diskpart to detach the image.
- Use ImageX to mount the image. Use ImageX to modify the image. Use ImageX to commit the changes and unmount the image.
- Boot the computer to the VHD file. Use Dism and an Unattend file to service the image. Reboot the computer to another Windows installation.
- Use Diskpart to attach the VHD file. Use Dism to modify the image. Use Diskpart to detach the image.

Explanation
Offline servicing lets you make changes to a Windows image without the operating system running. To update an offline image of Windows that is included in a VHD file:
1. Attach the VHD file using Diskpart or Disk Management
2. Use Dism.exe to modify the image
3. Detach the VHD file.

If you boot to the VHD file, you can perform online servicing but not offline servicing. Use dism or ImageX to service an image that is not part of a VHD file.

Section 2.6
You decide to use a system image to deploy Windows 7 to multiple computers.
You have configured a reference computer with Windows 7 and are ready to capture and deploy the image.
You want to save the image file using three smaller files instead of one large file. Then you need to install the image to the new computers. You want to perform these actions with the least amount of effort possible.

What should you do? (Select two. Each choice is a required part of the solution.)
- On the reference computer, run imagex /capture /split
- On the target computer, run imagex /apply three times, once for each split file.
- On the reference computer, run imagex /capture. After the image is captured, run imagex /split.
- On the reference computer, run imagex /capture. After the image is captured, run imagex /export.
- On the target computer, run imagex /apply /ref
- On the reference computer, run imagex /capture. After the image is captured, run imagex /split.
- On the target computer, run imagex /apply /ref

Explanation
You can split an image file between multiple files. To capture and deploy an image using multiple files:
* Run imagex /capture on the reference computer to capture the image.
* Run imagex /split to split the captured image into multiple files.
* Run imagex /apply /ref to deploy the image using the split files. You run this command once and identify the names of the split files.

Use the /export command to delete unnecessary resources from the image file, reducing its size.

Section 2.3
You want to capture a system image to deploy Windows 7 to multiple computers.
You want to install Windows 7 on the reference computer using an answer file.
You need to create the answer file.

What should you do?
-
1. On a technician computer, insert the Windows 7 product DVD.
2. Run Windows SIM and load a preloaded install image (install.wim) from the DVD.
3. Select and edit the responses to the questions presented during the product installation.
4. Validate the file in Windows SIM,
5. Save the answer file.
-
1. On a technician computer, insert the Windows 7 product DVD.
2. Run imagex /mountrw to mount the preloaded install image (install.wim) from the DVD.
3. Create an unattend.xml file in the root directory.
4. Add the correct switches to the file for the questions presented during the product installation.
5. Run imagex /commit /unmount to save the changes to the install.wim file and dismount the file.
-
1. On a reference computer, insert the Windows 7 product dvd.
2. Run Windows SIM and run the capture feature.
3. Run sysprep.exe from the product DVD and answer the questions presented during product installation.
4. Save the capture answers in the XML format and validate the file in Windows SIM.
-
1. On the technician computer, insert the Windows 7 product DVD.
2. Run Windows SIM and load a preloaded answer file (Unattend.xml) from the DVD.
3. Select and edit the responses to the questions presented during product installation.
4. Validate the file in Windows SIM.
5. Save the answer file.
-
1. On a technician computer, insert the Windows 7 product DVD.
2. Run Windows SIM and load a preloaded install image (install.wim) from the DVD.
3. Select and edit the responses to the questions presented during the product installation.
4. Validate the file in Windows SIM,
5. Save the answer file.

Explanation
use the Windows SIM tool to create and manage answer files that are used for automating installations. To create an answer file, use the following steps:
1. On a technician computer, insert the Windows 7 product DVD.
2. Run Windows Sim and load a preloaded install image (Install.wim) from the DVD
3. Select and edit the responses to the questions presented during product installation.
4. Validate the file in Windows SIM.
5. Save the answer file.

Use ImageX to create an image file for Windows 7 deployment from a reference (source) computer

Section 2.2
You need to deploy Windows 7 Enterprise to multiple new computers using a previously-captured system image.
Before deploying the image, you need to see a list of all drivers included in the image.

What should you do?
- Run driverquery
- Run pnputil
- Run imagex
- Run dism
- Run dism

Explanation
use dism with the /get-drivers /all option to display basic information about all drivers, including all out-of-box drivers which are on a system image. Deployment Image servicing and Management (DISM) is a command line tool which manages and maintains system images.
Use imagex to capture a Windows 7 installation onto a network share, and mount an image so that it can be modified. use pnputil to stage device drivers in the driver store. Once a driver is in the driver store, any user can install a device that uses the driver without providing administrative credentials. use driverquery to display all installed device drivers and their properties while running Windows 7. Driverquery.exe will not work on an image.

Section 2.5
You need to automate the installation of Windows 7 to multiple computers. None of the computers will be a member of a domain.
You will use a custom image to install Windows 7 on each computer. Following Windows installation, you want the setup program for an application to run automatically.

What should you do?
- Create a Windows installation package in Group Policy.
- Use dism to add the application to the image.
- Configure a task in MDT.
- Create an Unattend file and use the file with sysprep to deploy the image.
- Configure a task in MDT.

Explanation
Microsoft Deployment Toolkit (MDT 2010) is a tool used to deploy operating systems and applications. You can use MDT to help create Unattend files used for Windows installations, as well as automate tasks that occur before and after installation or after applying an image. MDT uses tasks and task sequences to define the actions to take. MDT is often used in conjunction with WDS; MDT runs scripts before the image is applied, WDS then applies the image to the computer, and then MDT performs additional tasks following the application of the image.
You cannot use an installer package in Group Policy before the computers are not domain members. You cannot use the Deployment Image Servicing and Management (DISM) to add applications to a system image; use dism to add drivers or operating system updates. you can use an Unattend file to automate the installation process; however, the file does not perform tasks following installation.

Section 2.7
You have a computer running Windows 7 Ultimate.
You want to capture the installation as a system image. You have already used Sysprep to remove machine-specific information from the reference computer.
You need to exclude specific files from the ImageX capture operation.
What should you do? (Select two. Each choice is a required part of the solution.)
- Create a wimscript.ini file and include an exclusion list section.
- Run imagex.exe with the /exclude option.
- Run imagex.exe.
- Create an exclusionlist.ini file.
- Create a wimscript.ini file and include an exclusion list section.
- Run imagex.exe.

Explanation
To exclude specific files during the ImageX capture operation, create and use a wimscript.ini configuration file. The wimscript.ini file has an exclusion list section which defines what files and folders to exclude from the capture process. When you run imagex.exe on the reference computer, it will automatically recognize the wimscript.ini file if you save the wimscript.ini file int he same directory as the ImageX tool.
Use the /config option with ImageX to identify a configuration file with a different name or location than the default. Configure Exclusion Exceptions in the file to identify files that are to be included even if they meet the ExclusionList criteria.

Imagex.exe does not have an /exclude option

Section 2.3
You have a computer running Windows 7 Professional.
You want to capture the installation as a system image. you need to remove any computer-specific information from the computer prior to capturing the image.

What should you do?
- Run Windows SIM
- Run Windows PE (WinPE)
- Run ImageX
- Run sysprep
- Run sysprep

Explanation
You should run Sysprep to prepare a Windows installation for imaging by removing machine-specific information.
ImageX is a command-line tool used to create and modify operating system images. WInPE is a minimal installation of Windows that controls the early boot process and starts a limited operating system. WinPE is used with WDS to boot the computer and select the installation image to install on the computer. use Windows SIM to create and manage repose files used for unattend installations.

Section 2.1 and 2.2
You have a computer that runs Windows 7 Enterprise.
You want to configure the computer to boot to a Windows 7 installation on a VHD file. You will use the image on the Windows installation disc.
You have downloaded the Windows AIK tools. You create a virtual disk file using Disk Management.

What should you do next?
- Run ImageX to apply the install.wim image to the VHD.
- Run ImageX to apply the boot.wim image to the VHD.
- Run BCDBoot to copy boot files to the VHD file.
- Run Diskpart and configure the partition in the VHD as active.
- Attach the VHD.
- Attach the VHD.

Explanation
Before you can perform any actions on the VHD file, you must first attach (mount) the file. You can attach the file using Disk Management or Diskpart.
After the VHD file is attached, use ImageX to apply the .wim file to the virtual disk. The install.wim file contains the windows operating system. The boot.wim file contains a Windows PE boot environment; however, you cannot boot to Windows PE using an attached VHD file.
You do not need to run BCDBoot to copy boot files to the VHD file or make the partition inside the VHD file active because the computer does not run the BOOTMGR file from the VHD. BOOTMGR runs from the current disk partition. To boot to the installation ont he VHD file, you will need to modify the BCD store to point to the installation int eh VHD file.

Section 2.6
You have a computer that runs Windows 7 Enterprise.
You have created a VHD file that contains a Windows 7 installation image. The VHD file is currently not attached.
You would like to perform offline servicing of the image int he VHD file to add driver and enable some Windows features.

What should you do first?
-Run Dism with the /mountdir option.
- Boot the computer to the VHD file.
- Attach the VHD file.
- Run ImageX with the /mountrw option.
- Attach the VHD file.

Explanation
Offline servicing lets you make changes to a Windows image without the operating system running. To update an offline image of Windows that is included in a VHD file:
1. Attach the VHD file using Diskpart or Disk Management.
2. use Dism.exe to modify the image.
3. Detach the VHD file

If you boot to the VHD file, you can perform online servicing but not offline servicing. use dism with the /mountdir option or ImageX with the /mountrw option to mount an image that is not part of a VHD file.

Section 2.6
You have a computer running Windows 7 Ultimate.
You need to copy files to an existing VHD file that contains a Windows 7 installation.

What should you do?
- Run dism.exe and use the /wimfile and /commit-wim options.
- Use Windows Explorer, right-click the VHD file and select Open.
- Run diskpart.exe, then use the list, select, and attach commands.
- Run imagex.exe and use the /mountrw and /commit options.
- Run diskpart.exe, then use the list, select, and attach commands.

Explanation
Run diskpart.exe with the list, select, and attach commands. Before using DiskPart commands on a disk, partition, or volume, you must first list and then select the object to give it focus. When an object has focus, any DiskPart commands that you type act on that object, such as attach or detach.
Use the imagex.exe or dism.exe tools to mount image files, not VHD files. You cannot use Windows Explorer to attach (mount) the VHD file. Once attached, you can use Windows Explorer to view, copy, and save files within the VHD file.

Section 2.6
What are the recommended names for an Unattended Installation's answer file name?

What are the default locations the answer file could/should be placed?
- Autounattend.xml or Unattend.xml

-
* The same directory as the Windows Setup program. For example, if you are installing Windows from a network share, copy the answer file to the share in the same directory as the setup program.

* The root directory of removable storage devices (USB drives). If you are installing Windows from the installation disc, copy the installation file to a removable drive and insert the drive before starting the setup program.