Importing custom unattend files

You can import custom unattend files into the OS images repository. These files can then be used to customize Linux and Windows OS-images profiles.

About this task

The following file types are supported for custom unattend files.
Operating system Supported File Types More information
Microsoft® Windows® Server Unattend (.xml) For more information about unattend files, see the Unattended Windows Setup Reference webpage.
Microsoft Windows Hyper-V Server Not supported  
Red Hat® Enterprise Linux (RHEL) Server Kickstart (.cfg) For more information about unattend files, see the Red Hat: Automating the Installation with Kickstart webpage.
Consider the following when adding %pre, %post, %firstboot sections in the file.
  • You can include multiple %pre, %post, %firstboot sections to the unattend file; however, be aware of the ordering of the sections.

  • When the recommended #predefined.unattendSettings.preinstallConfig# macro is present in the unattend file, XClarity Administrator adds a %pre section before all other %pre sections in the file.

  • When the recommended #predefined.unattendSettings.postinstallConfig# macro is present in the unattend file, XClarity Administrator adds %post and %firstboot sections before all other %post and %firstboot sections in the file.

SUSE® Linux Enterprise Server (SLES) AutoYast (.xml) For more information about unattend files, see the SUSE: AutoYaST webpage.
VMware vSphere® Hypervisor (ESXi) with Lenovo Customization Kickstart (.cfg) Supported only for ESXi 6.0u3 and later updates and 6.5 and later.

For more information about unattend files, see the VMware: Installing or Upgrading Hosts by Using a Script webpage.

Consider the following when adding %pre, %post, %firstboot sections in the file.
  • You can include multiple %pre, %post, %firstboot sections to the unattend file; however, be aware of the ordering of the sections.

  • When the recommended #predefined.unattendSettings.preinstallConfig# macro is present in the unattend file, XClarity Administrator adds a %pre section before all other %pre sections in the file.

  • When the recommended #predefined.unattendSettings.postinstallConfig# macro is present in the unattend file, XClarity Administrator adds %post and %firstboot sections before all other %post and %firstboot sections in the file.

The OS images repository can store an unlimited number of predefined and custom files, if space is available to store the files.

Procedure

To import unattended files into the OS-images repository, complete the following steps.

  1. From the XClarity Administrator menu bar, click Provisioning > Manage OS Images to display the Deploy Operating System: Manage OS Images page.
  2. Click the Unattend Files tab.

    Illustrates the Manage OS Images page with a list of unattend files that have been imported to the OS images repository.
  3. Click the Import File icon (Import icon). The Import File dialog is displayed.
  4. Click the Local Import tab to upload files from the local system, or click the Remote Import tab to upload files from a remote file server.
    Note: To upload a file from a remote file server, you must first create a remote file-server profile by clicking the Configure File Server icon (Configure remote file server icon). For more information, see Configuring a remote file server
  5. If you chose to use a remote file server, select the server that you want to use from the Remote File Server list.
  6. Select the operating-system type.
  7. Enter the file name of the unattend file, or click Browse to find the file that you want to import.
  8. Optional: Enter a description for the unattend file.
    Tip: Use the Description field to distinguish between custom files with the same name.
  9. Optional: Select a checksum type to verify that the file being uploaded is not corrupt, and copy and paste the checksum value in the provided text field.

    If you select a checksum type, you must specify a checksum value to check the integrity and security of the uploaded file. The value must come from a secure source from an organization that you trust. If the uploaded file matches with the checksum value, it is safe to proceed with deployment. Otherwise, you must upload the file again or check the checksum value.

    Three checksum types are supported:

    • MD5

    • SHA1

    • SHA256

  10. Click Import.
    Tip: The file is uploaded over a secure network connection. Therefore, network reliability and performance affects how long it takes to import the file.

    If you close the web browser tab or window in which the file is being uploaded locally before the upload completes, the import fails.

What to do next

The unattend-file image is listed on the Unattend Files tab on the Manage OS Images page.

From this page, you can perform the following actions.

For information about adding an unattend file to a customized OS image profile, see Creating a custom OS-image profile.