Windows 7 / Getting Started

---

Adding Packages

Packages include operating system updates and language packs. The Windows Deployment Wizard can automatically install operating system updates during deployment. Users can also choose which language packs to install during LTI deployment. The following sections include more information about updates and languages.

To add a package to the deployment share, perform the following steps:

1. In Deployment Workbench, right-click the Packages folder (or a subfolder you created under this folder) in your deployment share and select Import OS Packages to start the Import Package Wizard.
2. On the Specify Directory page, type the path containing the package files you want to add to the deployment share, or click Browse to open it, and then click Finish. Deployment Workbench adds all the packages it finds in the folder and all its subfolders.
3. Finish the wizard. Deployment Workbench adds all the packages it finds in the folder and its subfolders.

After you add a package to the deployment share, it appears in the details pane when the Packages folder (or a subfolder of this folder) is selected in the console tree. It also appears in the deployment share in Packages\subfolder[\subfolder], where subfolder[\subfolder] is the destination specified when adding the package.

To disable a package and prevent its installation, perform the following steps:

1. In the Deployment Workbench console tree, select the Packages folder (or a subfolder) in your deployment share.
2. In the details pane, right-click the package you want to disable and then click Properties.
3. Click the General tab and clear the Enable (Approve) This Package check box to disable the package.

To remove a package from the deployment share, perform the following steps:

1. In the Deployment Workbench console tree, select the Packages folder (or a subfolder) in your deployment share.
2. In the details pane, right-click the package you want to remove and then click Delete.

When a package is deleted from Deployment Workbench, it is also removed from the Packages folder in the deployment share. In other words, removing a package from Deployment Workbench also removes it from the file system.

Adding Updates

Operating system updates are distributed as Microsoft Standalone Update (.msu) files.

When you are developing an image, take care to ensure that all critical security updates are included in the image so that computers deployed with the image are as up to date as possible. Table below describes different approaches to performing these updates. (When you use MDT 2010, the first method is recommended.)

Updating Windows 7 Images

Method	Benefits	Drawbacks
Download the security updates from the Microsoft Web site and then install them as part of the image build process. You can search for updates in the Knowledge Base and on the Download Center.	The process is very easy to perform; you can install updates simply by adding them to the deployment share.	The process can be time consuming.
Use Windows Server Update Services (WSUS) or System Center Configuration Manager 2007 SP2 to install the security update post-deployment.	The process is easy to perform and picks up new updates as soon as they are approved.	The image is vulnerable before the updates are installed and the computer is restarted, providing an opportunity for exploitation; the application process can also be time consuming. Depending on the System Center Configuration Manager 2007 SP2 server configuration, it may takean hour or more before all updates are applied; having the System Center Configuration Manager 2007 SP2 client included in the image and communicating with a specific site may result in all computers built from the image communicating with only that site.
Download the security updates from the Microsoft Web site and then integrate them into the Windows installation source before beginning the unattended build process.	The image is protected at all times from known security exploits, and the image build process completes faster because all security updates are installed before buildingthe image.	Integrating the security updates takes some effort. It may not be obvious which updates you can integrate; you will need to install some as part of the unattended build process.

Note Download the required Windows security updates from the Microsoft Knowledge Base or Download Center. You can also download updates from the Microsoft Update Catalog at http://catalog.update.microsoft.com/v7/site/.

Adding Language Packs

Language packs make possible a multilingual Windows environment. Windows 7 is language neutral; all language and locale resources are added to Windows 7 through language packs (Lp.cab files). By adding one or more language packs to Windows 7, you can enable those languages when installing the operating system. As a result, you can deploy the same Windows 7 image to regions with different language and locale settings, reducing development and deployment time.

The following resources provide additional information about language packs in Windows Vista:

• The Microsoft Deployment Toolkit Reference in the MDT 2010 documentation lists the properties that you can configure to install language packs automatically.
• The topic, "Understanding Multilingual Deployments," in the Windows Automated Installation Kit User's Guide for Windows 7 includes more information about Windows Vista language packs.

Adding Out-of-Box Drivers

Depending on the type of computer in the environment and the hardware it contains, you require software from the hardware vendors to make computers in the production environment fully functional. Some of this software may be provided on a CD-ROM or DVD-ROM by the hardware manufacturer; other software must be downloaded from the vendor's Web site.

Deployment Workbench makes adding device drivers to the deployment share an easy process. You simply specify a folder containing one or more device drivers, and Deployment Workbench copies them to the deployment share and organizes them into folders as appropriate. However, you must make sure that you've extracted device drivers from any compressed files containing them. In other words, Deployment Workbench looks for each device driver's .inf file and any related files.

In MDT 2008 you could create driver groups to group together device drivers. You could then associate a driver group with a task sequence. In MDT 2010, you can no longer create driver groups. Instead, you can now create subfolders under the Out-Of-Box Drivers folder in your distribution share. You can import different drivers into different subfolders and then associate each subfolder with a task sequence.

Note Windows Deployment Services in Windows Server 2008 R2 also includes new features that make it simpler to ensure that the appropriate drivers are available during a deployment. You can add driver packages to a Windows Deployment Services server and deploy these driver packages to different client computers based on filtering criteria. You can also add boot-critical driver packages to boot images (supported for Windows 7 and Windows Server 2008 R2 images only).

To add device drivers to the deployment share, perform the following steps:

1. In Deployment Workbench, right-click the Out-Of-Box Drivers folder (or a subfolder you created under this folder) in your deployment share and select Import Drivers to start the Import Driver Wizard.
2. On the Specify Directory page, type the path containing the device drivers you want to add to the deployment share or click Browse to open it.
3. If you want, select the Import Drivers Even If They Are Duplicates Of An Existing Driver check box. Choosing this option allows Deployment Workbench to import duplicate drivers, if they exist, but Microsoft recommends against this.
4. Finish the wizard. Deployment Workbench adds all the device drivers it finds in the folder and its subfolders.

After you add a device driver to the deployment share, it appears in the details pane when the Out-Of-Box Drivers folder (or a subfolder of this folder) is selected in the console tree. It also appears in the deployment share in Out-Of-Box Drivers\subfolder[\subfolder], where subfolder[\subfolder] is the destination specified when adding the driver.

To disable a device driver, perform the following steps:

1. In the Deployment Workbench console tree, click Out-Of-Box Drivers (or a subfolder) in your deployment share.
2. In the details pane, right-click the device driver you want to disable and then click Properties.
3. Click the General tab, clear the Enable This Driver check box, and then click OK.

To remove a device driver from the deployment share, perform the following steps:

1. In the Deployment Workbench console tree, click Out-Of-Box Drivers (or a subfolder) in your deployment share.
2. In the details pane, right-click the device driver you want to remove and then click Delete.

When a device driver is deleted from Deployment Workbench, it is also removed from the Out-Of-Box Drivers folder in the deployment share. In other words, removing a device driver from Deployment Workbench also removes it from the file system.