# ESXi Boot Prompt Configuration

An unmodified ESXi ISO boots into an interactive installer. This defaults to a manual process and prevents unattended installation if you do not provide a kickstart file.

To enable fully unattended deployment, choose one of the two options.

## Option 1: Modified ISO (Recommended)

Modify the ESXi ISO to embed the kickstart parameter in the boot configuration. This modification ensures the installer automatically loads the kickstart file and proceeds with an unattended installation.

1. Modify the ESXi ISO to embed the kickstart parameter in the boot configuration. This modification ensures the installer automatically loads the kickstart file and proceeds with an unattended installation.

   The ESXi ISO contains `boot.cfg` files at `/` and `/efi/boot/` with the following default entry:

   ```
   ```
   kernelopt=runweasel cdromBoot
   ```
   ```
2. Update this entry in both files to:

   ```
   ```
   kernelopt=runweasel cdromBoot ks=cdrom:/KS.CFG
   ```
   ```

   Place the `KS.CFG` file at the root directory of the ISO.
3. To customize and rebuild the installation media, perform the following steps:

   1. Extract the contents of the ESXi ISO.
   2. Update both `boot.cfg` files as shown above.
   3. Rebuild the ISO using `genisoimage` or `mkisofs`.

      ```
      ```
      genisoimage -relaxed-filenames -J -R  -o esxi-custom.iso \  
        -b isolinux.bin -c boot.cat  -no-emul-boot -boot-load-size 4 -boot-info-table \  
        -eltorito-alt-boot -e efiboot.img -no-emul-boot <extracted-dirpath>
      ```
      ```

      This ensures the installer automatically loads the kickstart file and proceeds unattended.

## Option 2: Manual Console Interaction

If you use an unmodified ISO, you must manually provide the kickstart configuration parameters during the initial boot sequence.

To complete a manual installation, perform the following steps:

1. **Open the Console:** Launch the provisioning workflow in Morpheus and open the instance console.
2. **Enter the Kickstart Parameter:** Interrupt the boot sequence when prompted, and manually append the `ks=` parameter to the boot options line.
3. **Complete Installation:** Commit the boot arguments to resume the automated installation.

NOTE

Bare Metal as a Service (BMaaS) generates a provisioning-specific `KS.CFG` file at runtime and mounts it through virtual CD-ROM media at the root folder.
