Creating WinPE 2.0 and later images using the Image Creation  wizard

Use the Image Creation wizard to create WinPE 2.0 and later x86 or x64 boot image files from the BMC Server Automation Console.

Before you begin

  • Prepare the machine on which boot images are created.
  • If you plan to create image files for booting from media local to the target server, create a network.ini file.

To create the boot image file

  1. Select Configuration > Provisioning Image Creation.

  2. Specify information for creating the image, as described in the following sections:

    Toolkit Select

    Click here for more information on Toolkit Select.

    The Toolkit Select wizard panel lets you specify the location of the image toolkit used to create the image, the type of image to create, and where the newly created image file should be stored. The following figure shows the Toolkit Select wizard panel.WinPE_Toolkit.jpgField Definitions
    Image Toolkit Host
    Identifies the server on which the image tool kit is located. Type the server name or click Browse to select the server.
    The image tool kit host must be a server running a licensed RSCD agent and the user creating the image file must be logged into the server using a role that has Write authorization.
    Image Type
    Specifies the method of creation and format of the WinPE 2.0 and later image you want to create. Select one or more types.
    • PXE Image: Creates an image for booting the target server from the PXE server. The image is a directory with the name bootImageName; the directory contains the files for booting the target server from the PXE server.
    • ISO Image: Creates an image in ISO format (_bootImageName._iso) for booting from media connected to the target server.
    • UFD Image: Creates an image in UFD format for booting from USB flash drive. The image is a directory with the name bootImageName_UFD; the directory contains the files for booting from a USB flash drive.
    Architecture
    Specifies the architecture of the machine for which you are creating the image: x86 or x64.
    Win AIK Directory Path
    Specifies the full path for the Microsoft Windows Automated Installation Kit (WAIK) directory. Type the path or click Browse to select the directory. For example: C:\Program Files\WinAIK
    Create WinPE Script Directory Path
    Specifies the full path for the directory in which you unzipped the provision-files.zip file. The directory should contain the CreateWinPE2_x.vbs file. For example: C:\BMC_BL\provisioning\winpe.
    Type the full path for the directory or click Browse to select the directory. The pathname may contain spaces.
    Boot Image Target Directory
    Specifies the target directory for the new image file.
    NoteThe target directory must be on a server running a licensed RSCD agent and the user creating the image file must be logged into that server using a role that has Write authorization.
    • For PXE image type — If this is the only image type you selected:
      • Select Use TFTP Root as base directory to specify that tftproot on the tftp server be used as the base directory. In the text box, type the directory under tftproot where you want the image file created.
      • Deselect Use TFTP Root as base directory, and in the text box, type the full path to the directory in which you want the image file created, or click Browse to select a location. Use NSH format for the path. For example:
        //myComputerHostname/myImageDirectory
    • For ISO or UFD image types — In the text box, type the full path to the directory in which you want the image created, or click Browse to select a location. Use NSH format for the path. For example:
      //myComputerHostname/myImageDirectory
    Boot Image Name
    Specifies the new boot image file name. Spaces are not supported in the boot image name.
    For PXE or ISO image types:
    • If you are creating the default images (for the default placeholders on the Image Files tab of the Provisioning Configurations window), use the following expected file names:
      • boot_2_0_x86 for 32-bit images
      • boot_2_0_x64 for 64-bit images
    • If you are creating additional custom images, provide a name other than those listed above. When the boot file name is other than boot_2_0_xx, the system creates custom placeholders for the image on the Image Files tab of the Provisioning Configurations window.

      For USB flash drive (UFD) image types, there are no placeholders, and thus no expected image names.
       

    Driver Selection

    Click here for more information on Driver Selection.

    The Driver Selection wizard panel lets you inject drivers into the WinPE image. The following figure shows the Driver Selection wizard panel.

    WinPE_DriverSelection.jpg

    Most installations require a set of drivers. For example, you might need to inject VMware drivers, such as vmware-nic.inf, vmx_svga.inf and vmxnet.inf, in the WinPE boot image.

    To provide the path names to the driver files to inject into the image:

    • To select an existing Driver.txt file that contains the path names to .inf driver files, click Browse next to the Open Driver.txt file field.
       The path names contained in the selected file appear in the large Driver Files panel in the middle of the window.

    • To add additional drivers to the displayed list or to start building a list of drivers, click Add. In the Select Driver Files dialog, select the root folder that contains the drivers or subfolders with drivers. Then click OK. All drivers in the selected folder or subfolders appear in the large Driver Files panel in the middle of the window.

      Note

      The path to the Driver.txt file can contain spaces. However, the path names of the .inf driver files cannot contain spaces. Spaces are not supported.

    • To save a new Driver.txt file that contains all of the drivers shown in the Driver Files panel, click Save new Driver.txt file. Then do one of the following:
      • Type the path to a folder where you want to save this new Driver.txt file. Use NSH format and include the file name. For example:
        //myComputerHostname/myDriversFile/Driver.txt
      • Click Browse to select a folder in which you want to save this new Driver.txt file. Add the file name to the path in the edit box under Save new Driver.txt.

    Custom Script

    Click here for more information on Custom Script.

    To specify an external script to run when the image is mounted, use the Custom Script wizard panel. This panel lets you select an existing script or type a script in the text box.

    Specify an external script using one of the following methods:

    • Click Browse g_V95_BrowseIcon.gifto select the script file in the Select Custom Script dialog. Then click OK after selecting the file.
    • Type the script in the text box.

    Configuration Details

    Click here for more information on Configuration Details.

    The Configuration Details wizard panel lets you specify information for an image for booting a target server from local media (CD-ROM, DVD, USB flash drive, iLO, DRAC). Provide information only if you creating an ISO or UFD image. The following figure shows the Configuration Details wizard panel.

    WinPE_ConfigDetails.jpg

    Field definitions

    Network Details

    (Optional) Specifies the path to the network.ini file. This file contains the MAC address of each target server and its network details (static IP address, subnet mask, default gateway, WINS server, and DNS servers). Specify this file if the provisioning environment does not contain a DHCP server.
    Click Browse g_V95_BrowseIcon.gifto select the network.ini file.
    If you select a network.ini file, the image creation process copies the file to the root of the WinPE ISO image or UFD directory, depending on the image types you selected.
    If you do not specify a network.ini file during image creation, you can:

    • Manually copy the network.ini file to the root directory of the media (CD, DVD, USB) you use for local provisioning of the server.
    • Provide network details during the provisioning of the target server. Use this option if your provisioning environment does not include a DHCP server.

      When you run the Provision Job, it searches for the network.ini file at the root of the local media. If the file is not present there, the job allows the DHCP server to provide network details dynamically. If no DHCP server is present, the job prompts you for those details.

    Application Server IP Address

    Specifies the IP address of the Application Server with which the target server communicates.

    Application Server Port

    Specifies the port that the target server uses to communicate with the Application Server.

    Configuration Components for Local Data Store

    Specifies the location to which these components (bmiwin.exe, RSCD Agent installer, and operating system drivers) are copied on local media. Select either of the following:

    • Copy to root of ISO/UFD: Copies configuration components to the root of ISO image or UFD directory on the media.
    • Copy to WinPE image: Copies configuration components to a pre-defined directory (LDS) in the WinPE image.

      The copy option you select becomes the value of the CONFIG_STORE property. You can set the value of the CONFIG_STORE property in Local Properties when you create a system package.

    BMIWIN.EXE Path

    Specifies the path to the bmiwin.exe file to copy the local media. For example: D:\DataStore\bmiwin.exe. Type the path (including the file name) or click Browse to select the file.

    RSCD Installer Path

    Specifies the path to the RSCD agent installer files to copy to the local media. For example: D:\DataStore\RSCD\rscd_76_x86. Type the path or click Browse to select the directory.

    OS Drivers Path

    Specifies the path to the operating system driver files you want to copy to the local media. For example: D:\DataStore\Drivers. Type the path or click Browse to select the directory.

    Tip

    If you are using the DHCP server to assign IP addresses (not the network.ini file) and the server fails to assign the network details due to slow initialization of network cards on the target machine, edit the BLAssignNetDetails.vbs file and increase the ATTEMPTS and DELAY values to allow for initialization time. For example, you might increase ATTEMPTS from 2 (the default) to 5 and DELAY from 10 (the default) to 30.
    The BLAssignNetDetails.vbs file resides in the /provisioning/winpe subdirectory you created by unzipping the provision-files.zip file.

  3. Click Finish to begin image file creation.
     A progress dialog box informs you that the image file creation is running. When it completes, the script execution log appears in the dialog box.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*