Skip to main content
Matrix42 Self-Service Help Center

Inject drivers into a boot configuration

Some deployment scenarios may require a different approach to deploying certain drivers.

Some devices need to be fully initialized before starting the Windows HAL. Devices, such as some docking stations, that support Mac address pass-through.

To provide a simple and comprehensive method of addressing such scenarios, Matrix42's WinPE-based deployment provides the ability to declare driver packages to be injected into the boot image.

In the following short tutorial, we add an exemplary driver that is injected into the boot image.

  1. In the navigation bar, switch to Configuration and select Boot Configurations.
  2. Click the New button to create a new boot configuration.
  3. Activate the Advanced Properties in the upper right corner.
  4. Customize the Name and Description fields according to your requirements.
  5. Select the desired agent template from the Agent Template drop-down box.
  6. Select the platform(s) to support (EFI x86, EFI x64, BIOS).
  7. Set the TFTP Block Size to be used.
  8. Now add a driver to the boot configuration by clicking on the icon WinPE_Add.gif below the driver list and selecting the desired driver.
    Added drivers can be deleted by clicking the trash icon on the right side of the driver list.
    A driver was added to the boot image, in this case a VMware VMCIBus driver.
    This driver is marked as "Inject Driver" type and will be injected into the boot configuration afterwards.
    Another driver has also been added, in this case a PVSCSI driver, to show the visual difference between the two driver integration options.
    Note that a newly added driver is added by default as a "Driver Folder" type, which means that the driver is loaded into WinPE at runtime.
    To change the type of the driver, click on the list entry, this opens a pull down menu where you can change the driver type for this specific boot image.
  • Was this article helpful?