Importing boot files

You can import boot files into the OS images repository. These files can then be used to customize and deploy Windows images.

About this task

A boot file acts as the bootstrap install environment. For Windows, this is a Windows Pre-installation (WinPE) file. A WinPE boot file is required to deploy Windows

Lenovo XClarity Administrator supports predefined and custom boot files.
  • Predefined boot files. Lenovo provides a WinPE_64.wim boot file that can be used to deploy predefined OS-image profiles.

    Lenovo bundles the predefined WinPE_64.wim boot file along with a set of device drivers into a single package that can be downloaded from the Lenovo Windows drivers and WinPE Images Repository webpage and then imported into OS-images repository. Because the bundle file contains both device drivers and boot files, you can import the bundle file from the Device Driver or Boot Files tab.

    • A predefined boot file is not preloaded with XClarity Administrator. You must import a boot file into the OS-images repository before you can deploy a Windows profile.

    • If you migrated your Windows images to XClarity Administrator v2.1.0 from an earlier release, a preloaded WinPE_64.wim boot file was migrated to the OS-images repository. It is recommended that you import the bundle file for the specific Windows release that you want to deploy instead of using the preloaded boot file.

    • You cannot delete predefined boot files that were loaded when you installed XClarity Administrator; however, you can delete predefined boot files that were imported from a Lenovo bundle.

    • XClarity Administrator requires that imported bundle files be signed by Lenovo. When importing a bundle file, an .asc signature file must also be imported.

  • Custom boot files. You can create a WinPE boot file to customize boot options for a Windows deployment. You can then add the boot file to custom Windows profiles.

    XClarity Administrator provides scripts for creating boot files in the correct format. For information about creating a custom boot files, see Creating a boot (WinPE) file and Introduction to Windows PE (WinPE) website.

    The following file types are supported for importing custom boot files.
    Operating system Supported Boot File Types Supported Bundle File Types
    CentOS Linux Not supported Not supported
    Microsoft® Windows® Server A .zip file that contain a WinPE file that is created using the genimage.cmd script A .zip file containing device drivers and boot files
    Microsoft Windows Hyper-V Server A .zip file that contain a WinPE file that is created using the genimage.cmd script A .zip file containing device drivers and boot files
    Red Hat® Enterprise Linux (RHEL) Server Not supported Not supported
    SUSE® Linux Enterprise Server (SLES) Not supported Not supported
    VMware vSphere® Hypervisor (ESXi) with Lenovo Customization Not supported Not supported
Note: The OS images repository can store an unlimited number of predefined and custom files, if space is available to store the files.


What to do next

The boot file is listed on the Boot Files tab on the Manage OS Images page.

From this page, you can perform the following actions.