Appendix E: Configuring Deployment Points

  • Article

BDD 2007 enables deploying builds using these different deployment points, or methods:

  • Lab or single-server deployment (Lab). Choose this option to deploy builds from the distribution share created on the local computer.

  • Separate deployment share (Network). Choose this option to create another distribution share on the local computer or another computer. The new distribution share will contain a subset of the files contained in the local distribution share.

  • Removable Media (Media). Choose this option to create a DVD ISO image to deploy a build.

  • SMS 2003 OSD (OSD). Choose this option to create a directory containing all the files required to customize an SMS 2003 OSD program. OSD deployment points can only be used to deploy images created by the SMS 2003 Image Capture Wizard, as described in Appendix G, “Capturing a ZTI Image.”

On This Page

Creating Deployment Points Creating Deployment Points
Configuring Deployment Points Configuring Deployment Points
Updating Deployment Points Updating Deployment Points
Removing Deployment Points Removing Deployment Points

Creating Deployment Points

The following sections describe how to create each type of deployment point. Deployment Workbench supports only a single lab deployment point but multiple network, media, and OSD deployment points.

Note The Computer Imaging System feature team must always create a lab deployment point for each platform (x86 and x64) used in Deployment Workbench. BDD 2007 uses the setup files from the lab deployment point for custom and Windows DS images.

Lab

To create a lab deployment point, complete the following steps:

  1. In the Deployment Workbench console tree, right-click Deployment Points, and click New to start the Windows Deployment Wizard.

    Note   Deployment Points resides beneath Deploy.

  2. On the Choose which you would like to configure or create page, shown in Figure 15, select Lab or single-server deployment, and then click Next.

    Figure 15. Windows Deployment Wizard

    Figure 15. Windows Deployment Wizard

  3. On the Specify a descriptive name page, type a name for the deployment point, and then click Next.

  4. On the Allow Application Selection during Upgrade page, perform one of the following tasks, and then click Next:

    • Select the Allow users to select additional applications on upgrade check box to enable users to install applications from the distribution share after upgrading their computers. This is the default.

    • Clear the Allow users to select additional applications on upgrade check box to deny users the option of installing applications after upgrading their computers.

  5. On the Specify whether to prompt for image capture page, perform one of the following tasks, and then click Next:

    • Select the Ask if an image should be captured check box if the Windows Deployment Wizard should ask whether to create an image of the destination computer after installing a build on it. This is the default. See “Appendix F: Capturing a LTI Image” for more information about capturing build images.

    • Clear the Ask if an image should be captured check box if BDD 2007 should not ask whether to create an image of the destination computer after installing a build on it.

  6. On the Allow user to set Administrator password page, perform one of the following tasks, and then click Next:

    • Select the Ask user to set the local Administrator password check box to allow users to set the local Administrator password during installation.

    • Clear the Ask user to set the local Administrator password check box to prevent users from setting the local Administrator password during installation.

  7. On the Allow user to specify a product key page, perform one of the following tasks, and then click Next:

    • Select the Ask user for a product key check box to allow users to specify a product key during installation.

    • Clear the Ask user for a product key check box to prevent users from specifying a product key during installation.

  8. On the Specify the location of the network share to hold the files and folders necessary for this deployment type page, type a name for the share, and then click Next.

    The default name is folder$, where folder is the name of the folder containing the distribution share. The dollar sign ($) hides the share in the network browser list.

  9. On the Specify user data defaults page, shown in Figure 16, select one of the following options, and then click Finish:

    • Allow the user to configure user state options. Select this option if BDD 2007 should prompt users for the location to save user state data.

    • Automatically determine the location. Select this option to allow BDD 2007 to automatically determine the best location for saving user state data.

Note If this option is selected, select the Allow data and settings to be stored locally when possible check box to store user state data locally (the default). If this check box is cleared, BDD 2007 will not store user state data locally.

  - ***Specify a location.*** Select this option to specify an exact location for saving user state data; then, type the location in the **Location** box.

  - ***Do not save data and settings.*** Select this option to prevent BDD 2007 from saving user state data.

[![Figure 16. Specify user data defaults](images/Bb490290.SE_CompImag16(en-us,TechNet.10).gif)](https://msdn.microsoft.com/en-us/bb490290.se_compimag16_big\(en-us,technet.10\).gif)

**Figure 16. Specify user data defaults**

Network

To create a network deployment point, complete the following steps:

  1. In the Deployment Workbench console tree, right-click Deployment Points, and click New to start the Windows Deployment Wizard.

    Note   Deployment Points resides beneath Deploy.

  2. On the Choose which you would like to configure or create page, select Separate deployment share, and then click Next.

  3. On the Specify a descriptive name page, type a name for the deployment point, and then click Next.

  4. On the Allow Application Selection during Upgrade page, perform one of the following tasks, and then click Next:

    • Select the Allow users to select additional applications on upgrade check box to enable users to install applications from the distribution share after upgrading their computers. This is the default.

    • Clear the Allow users to select additional applications on upgrade check box to prevent users from installing applications after upgrading their computers.

  5. On the Allow user to set Administrator password page, perform one of the following tasks, and then click Next:

    • Select the Ask user to set the local Administrator password check box to allow users to set the local Administrator password during installation.

    • Clear the Ask user to set the local Administrator password check box to prevent users from setting the local Administrator password during installation.

  6. On the Allow user to specify a product key page, perform one of the following tasks, and then click Next:

    • Select the Ask user for a product key check box to allow users to specify a product key during installation.

    • Clear the Ask user for a product key check box to prevent users from specifying a product key during installation.

  7. On the Specify the location of the network share to hold the files and folders necessary for this deployment type page, perform the following tasks, and then click Next:

    • In the Server name box, type the name of the server on which to create the new distribution share.

    • In the Share name box, type the name of the share to create for the new distribution share.

    • In the Path for share box, type the path in which to create the new distribution share on the server.

      Note   This path should be local to the computer on which the distribution share is created.

  8. On the Specify user data defaults page, select one of the following options, and then click Finish:

    • Allow the user to configure user state options. Select this option for BDD 2007 to prompt users for the location to save user state data.

    • Automatically determine the location. Select this option to allow BDD 2007 to automatically determine the best location for saving user state data.

      Note   If this option is selected, select the Allow data and settings to be stored locally when possible check box to store user state data locally (the default). If this check box is cleared, BDD 2007 will not store user state data locally.

    • Specify a location. Select this option to specify an exact location for saving user state data; then, type the location in the Location box.

    • Do not save data and settings. Select this option to prevent BDD 2007 from saving user state data.

Media

To create a media deployment point, complete the following steps:

  1. In the Deployment Workbench console tree, right-click Deployment Points, and click New to start the Windows Deployment Wizard.

    Note   Deployment Points resides beneath Deploy.

  2. On the Choose which you would like to configure or create page, select Removable Media, and then click Next.

  3. On the Specify a descriptive name page, type a name for the deployment point, and then click Next.

  4. On the Allow Application Selection during Upgrade page, perform one of the following tasks, and then click Next:

    • Select the Allow users to select additional applications on upgrade check box to enable users to install applications from the distribution share after upgrading their computers. This is the default.

    • Clear the Allow users to select additional applications on upgrade check box to prevent users from installing applications after upgrading their computers.

  5. On the Allow user to set Administrator password page, perform one of the following tasks, and then click Next:

    • Select the Ask user to set the local Administrator password check box to allow users to set the local Administrator password during installation.

    • Clear the Ask user to set the local Administrator password check box to prevent users from setting the local Administrator password during installation.

  6. On the Allow user to specify a product key page, perform one of the following tasks, and then click Next:

    • Select the Ask user for a product key check box to allow users to specify a product key during installation.

    • Clear the Ask user for a product key check box to prevent users from specifying a product key during installation.

  7. On the Specify the location of the network share to hold the files and folders necessary for this deployment type page, perform the following tasks, and then click Next:

    • In the Server name box, type the name of the server on which to create the ISO image.

    • In the Share name box, type the name of the share to create for the folder containing the ISO image.

    • In the Path for share box, type the path to create for the folder containing the ISO image.

      Note   This path should be local to the computer on which the distribution share is created.

  8. On the Specify user data defaults page, select one of the following options, and then click Finish:

    • Allow the user to configure user state options. Select this option if BDD 2007 should prompt users for the location to save user state data.

    • Automatically determine the location. Select this option to allow BDD 2007 to automatically determine the best location for saving user state data.

      Note   If this option is selected, select the Allow data and settings to be stored locally when possible check box to store user state data locally (the default). If this check box is cleared, BDD 2007 will not store user state data locally.

    • Specify a location. Select this option to specify an exact location for saving user state data; then, type the location in the Location box.

    • Do not save data and settings. Select this option to prevent BDD 2007 from saving user state data.

OSD

To create an OSD deployment point, complete the following steps:

  1. In the Deployment Workbench console tree, right-click Deployment Points, and click New to start the Windows Deployment Wizard.

    Note   Deployment Points resides beneath Deploy.

  2. On the Choose which you would like to configure or create page, select SMS 2003 OSD, and then click Next.

  3. On the Specify a descriptive name page, type a name for the deployment point, and then click Next.

  4. On the Specify the location of the network share to hold the files and folders necessary for this deployment type page, perform the following tasks, and then click Next:

    • In the Server name box, type the name of the server on which to create the files necessary to create an SMS 2003 OSD program.

    • In the Share name box, type the name of the share to create for the folder containing the SMS 2003 OSD program files.

    • In the Path for share box, type the path to create for the folder containing the SMS 2003 OSD program files.

      Note   This path should be local to the computer on which the distribution share is created.

  5. On the Specify where to obtain SMS 2003 OSD files screen, type the path of the SMS 2003 OSD installation folder. For example, type D:\SMS\OSD.

  6. On the More configuration required dialog box, note the additional configuration files that are required and then click OK.

Note OSD deployment points can only be used to deploy images created by the SMS 2003 Image Capture Wizard. Capturing an image for SMS 2003 OSD is slightly different than capturing an image for LTI. Instead of allowing the Windows Deployment Wizard to capture the image, you allow it to prepare the destination computer for image capture by the SMS 2003 Image Capture Wizard. After the computer shuts down, you start the computer using the Image Capture CD to run the SMS 2003 Image Capture Wizard. For more information, see Appendix G, “Capturing a ZTI Image.”

Configuring Deployment Points

To configure a deployment point, complete the following steps:

  1. In the Deployment Workbench console tree, click Deployment Points.

    Note   Deployment Points resides beneath Deploy.

  2. In the details pane, right-click the deployment point to edit, and then click Properties.

  3. Click the General tab, and then edit the following settings (the settings that can be edited depend on the type of deployment point):

    • Deploy point name. Type a descriptive name for the deployment point.

    • Network path. Type the Universal Naming Convention (UNC) path of the deployment point.

    • Local path. Type the local path of the deployment point.

    • Platforms supported. Choose which platforms the deployment point supports.

      To indicate that the deployment point supports the x86 platform, select the x86 check box (the default). To indicate that the deployment point does not support the x86 platform, clear the x86 check box. Do the same for the x64 check box.

  4. Click the Rules tab, and then edit the deployment point’s settings.

    These settings reside in CustomSettings.ini, which is in the deployment point’s Control folder. For more information about the settings that can be configured on this tab, see the Configuration Reference.

  5. Click the Builds tab, and then select the check box next to each build to include in the deployment point.

    Selecting a build causes Deployment Workbench to copy the operating system associated with the build to the deployment point when it is updated. The Builds tab is not available for lab deployment points.

  6. Click the Applications tab, and then select the check box next to each application to include in the deployment point.

    Selecting an application causes Deployment Workbench to copy the application source files to the deployment point when it is updated. The Applications tab is not available for lab deployment points.

  7. Click the Drivers tab, and then select the check box next to each device driver to include in the deployment point.

    Selecting a device driver causes Deployment Workbench to copy the device driver source files to the deployment point when it is updated. The Drivers tab is not available for lab deployment points.

  8. Click the Windows PE tab, shown in Figure 17, and then edit the settings described in Table 15.

    The Windows PE 2004/2005 tab replaces the Windows PE tab for SMS 2003 OSD Feature Pack deployment points. For more information about configuring Windows PE 2004/2005 for zero touch installation by using the SMS 2003 OSD Feature Pack, see the Zero Touch Installation Guide.

    Table 15. Windows PE Settings

    Area

    Settings

    Driver Injection

    • Include all network drivers. Select this option to inject all network drivers found in the distribution share into the Windows PE bootable images.

    • Include all mass storage drivers. Select this option to inject all mass storage drivers found in the distribution share into the Windows PE bootable images.

    • Include all video drivers. Select this option to inject all video drivers found in the distribution share into the Windows PE bootable images.

    • Include all system-class drivers. Select this option to inject all system drivers (mother board drivers, and so on) in the distribution share into the Windows PE bootable images.

    Optional Components

    • ADO. Select this option to add the Microsoft ActiveX® Data Objects (ADO) optional component 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 a lite touch deployment of Windows Vista images when the setup files are Japanese, Korean, or Chinese. The Optional Fonts area provides the following options:

    • Chinese (ZH-CN).

    • Chinese (ZH-HK).

    • Chinese (ZH-TW).

    • Japanese (JA-JP).

    • Korean (KO-KR).

    Note Adding additional fonts to Windows PE boot images increases the size of the images. Add additional fonts only if necessary.

    Images to Generate

    • Generate a Lite Touch flat bootable ISO image. Select this option to generate flat bootable ISO images.

    • Generate a Lite Touch bootable RAM disk ISO image. Select this option to generate ISO images that start from RAM disk.

    • Generate a generic flat bootable ISO image. Select this option to generate a generic Windows PE flat bootable image that does not contain BDD 2007.

    • Generate a generic bootable RAM disk ISO image. Select this option to generate a generic Windows PE bootable image that starts from RAM disk and does not contain BDD 2007.

      Note   Deployment Workbench always generates .wim image files containing Windows PE. These files reside in the distribution share’s Boot folder.

    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.

    Figure 17. Windows PE properties

    Figure 17. Windows PE properties

  9. Click OK to save changes.

    Tip   Deployment Workbench always generates .wim image files, which can be used to start destination computers using Windows DS. Choose to generate only the Windows PE bootable ISO images that are actually required. By limiting the number of images generated, the updating process is accelerated.

Updating Deployment Points

After creating and configuring a deployment point in Deployment Workbench, update it to create it on the file system. Updating a deployment point creates the folder structure, Windows PE boot images, and so on. To update a deployment point, right-click the deployment point to update in the Deployment Points details pane, and then click Update. The following list describes what happens when each type of deployment point is updated:

  • Lab. Updating a lab deployment point shares the distribution share and creates the Windows PE boot images (.wim and .iso files) necessary to start the LTI deployment process from the share.

  • Network. Updating a network deployment point creates and shares the folder specified when the deployment point was created. This folder contains a subset of the operating systems, builds, applications, and device drivers from the distribution share—based on the deployment point’s configuration.

  • Media. Updating a media deployment point creates and shares the folder specified when the deployment point was created. This folder contains a bootable ISO image containing a subset of the operating systems, builds, applications, and device drivers from the distribution share—based on the deployment point’s configuration.

  • OSD. Updating an OSD deployment point creates and shares the folder specified when the deployment point was created. This folder contains the files necessary to create an SMS 2003 OSD Feature Pack program, including a subset of the operating systems, builds, applications, and device drivers from the distribution share—based on the deployment point’s configuration.

Note Deployment Workbench can update a deployment point without generating new Windows PE boot images. To update the BootStrap.ini and CustomSettings.ini files without creating new Windows PE bot images, right-click the deployment point to update in the Deployment Points details pane, and then click Update (files only).

Removing Deployment Points

To remove a deployment point, complete the following steps:

  1. In the Deployment Workbench console tree, click Deployment Points.

    Note   Deployment Points resides beneath Deploy.

  2. In the details pane, right-click the deployment point to remove, and then click Delete.

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