Preparing the Deployment Environment

Before deploying images to target computers, ensure that that the deployment environment is properly prepared to run LTI. Some of these steps may already be complete in the environment. In those instances, skip steps that are complete.

To prepare the deployment environment to run LTI

  1. Install BDD 2007, any required support files, and USMT 3.0.

  2. Create the BDD 2007 deployment point.

  3. Add applications.

  4. Add operating systems.

  5. Add packages.

  6. Add drivers.

  7. Add builds.

On This Page

Installing BDD 2007 Installing BDD 2007
Creating the Deployment Point Creating the Deployment Point
Adding Applications Adding Applications
Adding Operating Systems Adding Operating Systems
Adding OS Packages Adding OS Packages
Adding Drivers Adding Drivers
Adding Builds Adding Builds

Installing BDD 2007

In most instances, BDD 2007 should already be installed on the deployment server. In instances where this task is not complete and for more information on how to install BDD 2007 on the deployment server, see “Installing BDD 2007” in the Getting Started Guide.

Creating the Deployment Point

After BDD 2007 is installed, create the deployment point by using the Deployment Point Wizard in Deployment Workbench. By using the Deployment Point Wizard, team members can manage the following types of deployment points:

  • Lab or single-server deployment (LAB). By default, Deployment Workbench creates a distribution point (shared as Distribution$). Select this option to use the Distribution$ share as the deployment point.

  • Separate deployment share (Network). Select this option to create a new network share to use as a new distribution point. Create the network on the same computer on which Deployment Workbench is running or on another computer.

  • Removable media (Media). Use this option to create a shared folder to use to create images for deployment on removable media. This includes deploying from DVDs, external hard disks, or USB storage devices.

  • SMS 2003 Operating System Deployment (OSD) Feature Pack (OSD). Select this option to create a shared folder to use to create SMS OSD Feature Pack–managed images. This option should be used only for ZTI-based deployments.

Depending on the type of BDD 2007 deployment point created, the Windows Deployment Wizard displays different wizard pages. Figure 1 illustrates the wizard pages that are displayed depending on the deployment type selected.

Figure 1. Deployment Point Wizard pages and when they are displayed

Figure 1. Deployment Point Wizard pages and when they are displayed

To create the deployment point, complete the following steps (while skipping any wizard pages that are not displayed based on the deployment point type selected):

  1. Start Deployment Workbench.

  2. In the console tree, right-click Deploy, and then click New.

    The Windows Deployment Wizard starts.

  3. On the Builds can be deployed in several ways. Choose which you would like to configure or create page, select one of the options in Table 3 based on the requirements, and then click Next.

    Table 3. Deployment Point Type Options

    Option

    Select this option when

    Lab or single-server deployment

    Using a share created on the same computer on which Deployment Workbench is running.

    Separate deployment share

    Creating a new deployment share on the same computer on which Deployment Workbench is running or on another computer.

    Removable media

    Creating folders (and, optionally, an .iso image file) to deploy images by using removable media.

    SMS 2003 OSD Feature Pack

    Creating a shared folder containing all the files that the SMS 2003 OSD Feature Pack requires to create OSD images for use by ZTI only.

  4. On the Specify a descriptive name page, in the Deployment point name box, type deployment_point_name (where deployment_point_name is the descriptive name selected), and then click Next.

  5. On the Allow Application Selection during Upgrade page, clear or select the Allow users to select additional applications on Upgrade check box based on the information in Table 4, and then click Next.

    Table 4. Allow Users to Select Additional Applications on Upgrade Check Box Options

    Check box

    Select this option to

    Enabled

    Display the page in the Windows Deployment Wizard that prompts users to select additional applications to be installed at the same time they are upgrading. The wizard page is displayed in Windows Deployment Wizard when performing an Upgrade scenario.

    Cleared

    Suppress the page in the Windows Deployment Wizard.

  6. On the Specify whether to prompt for image capture page, select the Ask if an image should be captured check box based on the information in Table 5, and then click Next.

    Table 5. Ask If an Image Should Be Captured Check Box Options

    Check box

    Select this option to

    Enabled

    Display the page in the Windows Deployment Wizard that prompts users to capture an image of the target computer. The wizard page is displayed in Windows Deployment Wizard when performing a New Computer scenario and the target computer is joining a workgroup.

    Cleared

    Suppress the page in the Windows Deployment Wizard.

  7. On the Allow user to set Administrator Password page, select the Ask user to set the local Administrator Password check box based on the information in Table 6, and then click Next.

    Table 6. Ask User to Set the Local Administrator Password Check Box Options

    Check box

    Select this option to

    Enabled

    Display the page in the Windows Deployment Wizard that prompts users to provide the local Administrator password for the target computer.

    Cleared

    Suppress the page in the Windows Deployment Wizard.

  8. On the Allow user to specify a product key page, select the Ask user for a product key check box based on the information in Table 7, and then click Next.

    Table 7. Ask User for a Product Key Check Box Options

    Check box

    Select this option to

    Enabled

    Display the page in the Windows Deployment Wizard that prompts users to provide a product key for the target computer.

    Cleared

    Suppress the page in the Windows Deployment Wizard.

  9. Complete the Specify the location of the network share to hold the files and folders necessary for this deployment type page based on the information in Table 8, and then click Next.

    Table 8. Configuration Options for the Specify the location of the network share to hold the files and folders necessary for this deployment type Wizard Page

    In this box

    Type

    Server name

    computer_name (where computer_name is the name of the computer that will host the shared folder)

    Share name

    share_name (where share_name is the name of the share to be created on the computer that will host the shared folder)

    Path for share

    path_name (where path_name is the fully qualified path folder to share on the computer that will host the shared folder)

  10. On the Specify user data defaults page, select one of the options in Table 9 based on the requirements, and then click Finish.

    Table 9. User Data Defaults Options

    Option

    Select this option to

    Allow the user to configure user state options

    Display the page in the Windows Deployment Wizard that prompts users to configure user state migration options.

    Automatically determine the location

    Allow the BDD 2007 deployment scripts and process rules to automatically determine the best location based on local available disk space on the target computer.

    Optionally, select the Allow data and settings to be stored locally when possible check box to give preference to storing the data locally.

    Specify a location

    Save the user state migration data to a specific location.

    In the Location box, type location (where location is the fully qualified path to the location for storing the user state migration data).

    Do not save data and settings

    Discard any existing user state migration data. Or, team members are deploying a new computer with no existing data.

The Deployment Point Wizard finishes, and the new deployment point name appears in the details pane.

Adding Applications

Before deploying operating system images to the target computers, add any applications to be installed after the operating system is installed. Add the applications to be installed by using the New Application Wizard in Deployment Workbench. Use the New Application Wizard to add applications by using one of the following methods:

  • Copy applications to the distribution share. Use this option to copy the application source files from their existing location to a distribution share.

  • Install applications without copying files. Use this option to install applications without copying the application source files—for example, when the files are already on the target computer, on a shared folder.

Depending on the type of application added, the New Application Wizard displays different wizard pages. Figure 2 illustrates the wizard pages that are displayed depending on the application type selected.

Figure 2. New Application Wizard pages and when they are displayed

Figure 2. New Application Wizard pages and when they are displayed

To add the new application, complete the following steps (while skipping any wizard pages that are not displayed based on the application type selected):

  1. Start Deployment Workbench.

  2. In the console tree, expand Distribution Share, right-click Applications, and then click New.

    The New Application Wizard starts.

  3. On the Specify type of application to add page, select one of the options in Table 10 based on the requirements, and then click Next.

    Table 10. Application Type Options

    Option

    Select this option to

    Application with source files

    Deploy the application to the target computers from the distribution share. The application source files are copied from another location to an existing distribution share.

    Application without source files or elsewhere on the network

    Deploy the application to the target computers without copying the application source files—for example, when the files are already on the target computer, on a shared folder.

  4. Complete the Specify the details for this application page based on the information in Table 11, and then click Next.

    Table 11. Configuration Options for the Specify Application Details Wizard Page

    In this box

    Perform this action

    Publisher

    Type publisher_name (where publisher_name is the name of the software publisher of the application).

    Application Name

    Type application_name (where application_name is the user-friendly name of the application).

    Version

    Type version (where version is the version of the application).

    Languages(s)

    Type language (where language is the list of languages that the application supports).

    Platforms(s)

    Select platform (where platform is the processor type that the application supports). Options are:

    • All platforms

    • Only X86 platform

    • Only X64 (or amd64) platform

    • Only ia64 platform

  5. On the Select the location of the application files page, in the Source directory box, type source_directory_name (where source_directory_name is the fully qualified path to the application source files), and then click Next.

  6. On the Specify the destination page, in the Specify the name of the directory that should be created box, type destination_directory_name (where destination_directory_name is the fully qualified path to the folder to which the application files will be copied), and then click Next.

  7. Complete the Specify the installation details page based on the information in Table 12, and then click Add.

    Table 12. Configuration Options for the Specify Installation Command Wizard Page

    In this box

    Type

    Command line

    command_line (where command_line is the command, with parameters, to launch the installation of the application).

    Working directory

    working_directory (where working_directory is the folder to use as the default directory when starting the installation by running the command).

The New Application Wizard finishes, and the new application name appears in the details pane.

Note   Repeat this step for each application to be added.

Adding Operating Systems

Before deploying operating system images to the target computers, add the operating system to be deployed. Add the operating systems to be installed by using the New OS Wizard in Deployment Workbench. Use the New OS Wizard to add operating systems by using one of the following methods:

  • Add operating system from source files. Use this option to add an operating system when files are the source. These files can be stored on a DVD or other folder structure made from a product DVD. This image contains all the files that are on the product DVD.

  • Add operating system in a WIM file. Use this option to add an operating system when an image file in WIM format is the source. This image is a customized version of an image captured from a target computer.

  • Add operating system in a Windows DS image. Use this option to add an operating system when the source is stored in an image file on a Windows DS server.

Depending on the type of BDD 2007 operating system source, the New OS Wizard displays different wizard pages. Figure 3 illustrates the wizard pages that are displayed depending on the operating system source selected.

Figure 3. New OS Wizard pages and when they are displayed

Figure 3. New OS Wizard pages and when they are displayed

To add the new operating system, complete the following steps (while skipping any wizard pages that are not displayed based on the operating system source selected):

  1. Start Deployment Workbench.

  2. In the console tree, expand Distribution Share, right-click Operating System, and then click New.

    The New OS Wizard starts.

  3. On the Choose the type of operating system to add page, select one of the options in Table 13 based on the requirements, and then click Next.

    Table 13. Operating System Type Options

    Option

    Select this option to add

    Full set of source files

    An operating system when files are the source. These files can be stored on a DVD or other folder structure made from a product DVD.

    Custom image file

    An operating system when an image file in WIM format is the source. This image is a customized version of an image captured from a target computer.

    Windows Deployment Services images

    An operating system when the source is stored in an image file on a Windows DS server.

  4. Based on the option selected in Table 13, complete the steps in Table 14.

    Table 14. Tasks to Perform for the Operating System Type Options

    Option

    Perform these steps

    Full set of source files

    On the Select the location of the operating system files page, in the Source directory box, type source_directory_name (where source_directory_name is the fully qualified path to the operating system source files), and then click Next.

    Custom image file

    On the Select the operating system image file page, in the Source file box, type source_file_name (where source_file_name is the fully qualified path to the WIM file), and then click Next.

    Windows Deployment Services images

    On the Select the Windows Deployment Services server page, in the Server name box, type server_name (where server_name is the name of the Windows DS server on which the image to be added resides), and then click Next.

  5. On the Specify the destination page, in the Destination directory name box, type destination_directory_name (where destination_directory_name is the fully qualified path to the folder into which the operating system will be copied), and then click Copy.

The New OS Wizard finishes, and the new operating system appears in the details pane.

Note   Repeat this procedure for each operating system to be added.

Adding OS Packages

Before deploying operating system images to the target computers, add any packages that need to be installed after the operating system is installed. Add the packages to be installed by using the New Package Wizard in the OS Packages node in Deployment Workbench. The following are some examples of packages that are installed after the operating system is installed:

  • Security updates

  • Service packs

  • Language packs

Note   These packages are different than SMS 2003 Packages and SMS 2003 OSD Feature Pack packages. The Deployment Workbench user interface describes these packages as OS Packages to differentiate them from the packages in SMS 2003 and SMS 2003 OSD Feature Pack.

To add new packages

  1. Start Deployment Workbench.

  2. In the console tree, expand Distribution Share, right-click OS Packages, and then click New.

    The New Package Wizard starts.

  3. On the Select the location of the package files page, in the Package source directory box, type source_directory_name (where source_directory_name is the fully qualified path to the package source files), and then click Add.

    Note   Alternatively, click Browse to locate source_directory_name.

    The New Package Wizard finishes, and the new package name appears in the details pane.

Note   Repeat this procedure for each package to be added, except for other packages that are located beneath source_directory_name.

Adding Drivers

Before deploying operating system images to the target computers, add any device drivers that must be installed with the operating system. Add the drivers to be installed by using the:

  • New Driver Wizard in Deployment Workbench.

  • $OEM$ folder structure for original equipment manufacturer (OEM)–supplied drivers.

Adding Drivers by Using Deployment Workbench

To add new drivers by using Deployment Workbench, complete these steps:

  1. Start Deployment Workbench.

  2. In the console tree, expand Distribution Share, right-click Out-of-Box Drivers, and then click New.

    The New Driver Wizard starts.

  3. On the Select the location of the driver files page, in the Driver source directory box, type source_directory_name (where source_directory_name is the fully qualified path to the driver source files), and then click Finish.

    Note   Alternatively, click Browse to locate source_directory_name.

The New Driver Wizard finishes, and the new driver name appears in the details pane.

Note   Repeat this procedure for each set of drivers to be added, except for other drivers that are located beneath source_directory_name.

Adding Drivers by Using $OEM$ Folder Structure

In addition to the drivers configured in Deployment Workbench, you can add OEM-supplied drivers by adding $OEM$ folder structures to your deployment point. You can include drivers that are typically installed during graphical user interface (GUI)–mode Setup or post-Setup by standard Plug and Play enumeration. This permits you to pre-load OEM Plug and Play drivers that you can use later, when the associated hardware is introduced in the system.

Table 15 lists the methods for providing OEM-supplied device drivers and the corresponding folders where LTIApply.wsf scans for the $OEM$ folders where:

  • distribution_point is the distribution point where you want to add OEM-supplied device drivers.

  • build_id is the Build ID assigned to the target operating system.

  • os_version is the version of the target operating system.

  • architecture is the processor architecture of the target computer (x86 or x64).

Table 15. Methods for Providing OEM Device Drivers and the Corresponding Folders

Supply drivers by

In this folder structure

Build

distribution_point\Control\build_id\$OEM$

Operating system

distribution_point\Operating Systems\os_version\$OEM$

Processor architecture

distribution_point\architecture\$OEM$

Globally

distribution_point\$OEM$

During the LTI deployment process, LTIApply.wsf scans for $OEM$ folders containing drivers in the following order:

  1. Build of the target operating system.

  2. Version of the target operating system.

  3. Processor architecture of the target computer.

  4. Globally for all target computers.

Note   In instance where you have defined multiple $OEM$ folders, the first driver found by LTIApply.wsf is deployed to the target computer.

Adding Builds

Before deploying operating system images to the target computers, define the builds for the operating system images to be deployed. Create the builds to be deployed by using the New Build Wizard in Deployment Workbench.

To add a new build

  1. Start Deployment Workbench.

  2. In the console tree, right-click Builds, and then click New.

  3. The New Build Wizard starts.

  4. Complete the Specify general information about this build page based on the information in Table 16, and then click Next.

    Table 16. Configuration Options for the Specify General Information About This Build Page

    In this box

    Type

    Build ID

    build_id (where build_id is the build number, or identifier, for the image to be deployed).

    Build name

    build_name (where build_name is the user friendly name of the build to be deployed to the target computers).

    Build comments

    build_comments (where build_comments is a text description for any comments relating to the build).

  5. On the Select an operating system image to use with this build page, in the The following operating system images are available to be deployed with this build box, select image (where image is the image to be deployed with this build), and then click Next.

  6. On the Specify the product key for this operating system page, select one of the options in Table 17 based on the requirements, and then click Next.

    Table 17. Specify the Product Key for This Operating System Options

    Option

    Select this option to

    Use the specified product key

    Enter a product key to be used when deploying the build.

    In the Product Key box, type product_key (where product_key is the product key to be used during deployment to the target computer).

    Do not use a product key when installing.

    Use a volume license key or manually specify the product key during the deployment process.

  7. Complete the Specify settings about this build page based on the information in Table 18, and then click Next.

    Table 18. Configuration Options for the Specify Settings About This Build Page

    In this box

    Type

    Organization

    organization (where organization is the name of the organization to be configured during the deployment process).

    Full Name

    full_name (where full_name is the full name of the user to be configured during the deployment process).

    Internet Explorer Home Page

    url (where url is the URL to the Web site to configure as the home page for Windows Internet Explorer® during the deployment process).

  8. Complete the Specify the local Administrator password for this build page based on the information in Table 19, and then click Create.

    Table 19. Configuration Options for the Specify the local Administrator Password for This Build Page

    Option

    Select this option to

    Use the specified local Administrator password

    Specify the local Administrator password for the target computers of the build.

    In the Administrator Password and Please confirm Administrator Password boxes, type password (where password is the password for the local Administrator account on the target computers).

    Do not specify an Administrator password at this time

    Specify the local Administrator password during the deployment of the build.

The New Build Wizard finishes, and the new build name appears in the details pane.

Note   Repeat this procedure for each build to be added.

Download

Get the Microsoft Solution Accelerator for Business Desktop Deployment 2007

Update Notifications

Sign up to learn about updates and new releases

Feedback

Send us your comments or suggestions