Updating the Deployment Share
The Windows AIK 2.0 comes with Windows PE 3.0, so no additional files are necessary to create Windows PE boot images for MDT 2010. When you update your deployment share in the Deployment Workbench, MDT 2010 automatically generates the following custom Windows PE images (here platform is x86 or x64):
- Lite Touch Windows PE (platform) .wim file
If you want, you can configure the deployment share to also generate the following Windows PE images:
- Generic Windows PE (platform)
You don't need to manually customize Windows PE to add network interface card (NIC) device drivers to it. Deployment Workbench automatically adds the NIC device drivers that you add to the deployment share to the Windows PE boot images. You have the additional option of automatically adding video and system device drivers from the deployment share to the Windows PE boot images. You can also perform additional customizations of your Windows PE images. For example, you can customize the background bitmap, add additional directories, and increase the scratch space size from its default value of 32 megabytes (MB) up to a maximum of 512 MB if needed. To learn more about customizing Windows PE, see the Windows Preinstallation Environment User's Guide for Windows 7 in the Windows AIK.
Updating a deployment share causes Deployment Workbench to update its configuration files, source files, and Windows PE images. Deployment Workbench updates the deployment share's files and generates the Windows PE boot images when you update the deployment share, not when you create it. Deployment Workbench stores these boot images in the deployment share's \Boot folder. After you have updated the deployment share and generated Windows PE images, you can add the .wim image file to Windows Deployment Services. If you want, you can burn the Windows PE .iso images to CD or DVD media by using third-party CD/ DVD-burning software. Windows Deployment Services is the best way to start the Windows PE boot images on lab computers. Updating the boot images is faster than burning media, and booting destination computers is quicker.
Note You must use the same platform edition of Windows PE to start computers for installing each platform edition of Windows. In other words, you must start destination computers using a x86 edition of Windows PE to install a x86 edition of Windows 7. Likewise, you must use a x64 edition of Windows PE to install a x64 edition of Windows 7. If you use mismatched editions, you might see errors indicating that the image is for a different type of computer. Deployment Workbench automatically chooses the correct platform edition of Windows PE to match the operating system you're deploying.
To configure a deployment share for imaging in the lab, perform the following steps:
- In the Deployment Workbench console tree, click Deployment Shares.
- In the details pane, right-click the deployment share you want to configure and then click Properties.
- Click the General tab and then choose the platforms that the deployment share supports. To indicate that the deployment share supports the x86 platform, select the x86 check box. To indicate that the deployment share supports the x64 platform, select the x64 check box. This option determines the platforms for which Deployment Workbench generates Windows PE boot images.
- Click the Rules tab and then edit the deployment share's settings. These settings are located in CustomSettings.ini, which is located in the deployment share's Control folder. For more information about the settings that you can configure on this tab, see the Microsoft Deployment Toolkit Reference in MDT 2010.
- Click the Windows PE Settings (platform) tab for each platform and edit the settings
described in Table below. Then, click OK.
Windows PE Settings Tab
Area Settings Images to Generate Generate A Lite Touch Windows PE WIM file Select this option to generate a customized WIM file that you can use to perform LTI using Windows Deployment Services (this option is selected by default and cannot be cleared).
Generate A Lite Touch Bootable ISO Image Select this option to generate a bootable customized Windows PE ISO image that you can use to perform LTI by starting your destination computers manually (this option is selected by default).
Generate A Generic Windows PE WIM file Select this option to generate a generic WIM file that you can use to perform LTI using Windows Deployment Services.
Generate A Generic Bootable ISO Image Select this option to generate a bootable generic Windows PE ISO image that you can use to perform LTI by starting your destination computers manually.
Windows PE Customizations Custom Background Bitmap File Type the path and file name of a bitmap file to use as the Windows PE background.
Extra Directory To Add Type the path of a folder containing extra files and subfolders to add to the Windows PE bootable images.
Scratch Space Size Select the size of the scratch space for your Windows PE image. The available values are 32, 64, 128, 256, and 512 MB, with 32 being the default.
- Click the Windows PE Components (platform) tab for each platform and edit the settings described in Table below and then click OK.
Windows PE Components Tab
|Feature Packs||ADO Select this option to add the Microsoft ActiveX Data Objects (ADO) optional feature to the Windows PE bootable images.|
|Optional Fonts||Select the font support to add to the Windows PE boot images
that Deployment Workbench generates. You must add these fonts when performing an LTI deployment of Windows Vista
images when the setup files are Japanese, Korean, or Chinese. The Optional Fonts area provides the following options:
|Driver Injection||Selection Profile Use this list box to choose one of the following
selection profiles to include the appropriate device drivers in your Windows PE images:
After creating and configuring a deployment share in Deployment Workbench, you must update it to update the deployment share's configuration files and generate Windows PE boot images in the deployment share's \Boot folder. Deployment Workbench always generates .wim image files, which you can use to start destination computers using Windows Deployment Services. Choose to generate only the Windows PE bootable ISO images that are actually required. If you limit the number of images generated, the updating process is faster.
To update a deployment share, perform the following steps:
- In the Deployment Workbench console tree, click Deployment Shares.
- In the details pane, right-click the deployment share you want to configure and then click Update.
- On the Options page of the Update Deployment Share Wizard, shown on the following
page, select one of the following options:
- Optimize The Boot Image Updating Process Select this option to update existing versions of the image files in the deployment share. Choosing this option reduces the amount of time required to update the boot images. If you select this option, you can also select Compress The Boot Image Contents To Recover Space Used By Removed Or Modified Content if desired. Selecting this suboption reduces the size of the boot images but may increase the time needed to generate the images.
- Completely Regenerate The Boot Images Select this option to create a new version of all the image files in the deployment share. You can choose this option when you want to force the creation of new images. Note that this can take some time to complete.
- Finish the wizard. Depending on how your deployment share is configured and the options you selected in the Update Deployment Share Wizard, generating Windows PE boot images may take some time to complete.
After the deployment share has been updated, Windows PE boot images and other files will be present in the \Boot folder of the deployment share.
Important You must update your deployment share if you make changes to any the settings on the properties sheet of your deployment share. The Windows PE boot images will not contain your updated settings until you update your deployment share.
In this tutorial:
- Developing Disk Images
- Getting Started Developing Disk Images
- Prerequisite Skills and Lab Requirements
- Installation Media
- Capturing Images Using Microsoft Deployment Toolkit
- Creating and Configuring a Deployment Share
- Adding Operating Systems
- Adding Applications
- Specifying Application Dependencies
- Adding Packages
- Creating Task Sequences
- Editing a Task Sequence
- Configuring Group and Task Properties
- Configuring the Options Tab
- Task Sequence Variables
- Operating System Versions
- Updating the Deployment Share
- Capturing a Disk Image for LTI
- Preparing Images Manually
- Customizing Microsoft Deployment Toolkit