KACE Systems Deployment Appliance 9.1 Common Documents

The Package Management Export feature creates a .pkg file. The .pkg file contains the drivers and an .xml file with the same name as the .pkg file. The .xml file contains metadata about the drivers. A separate package is created for each selected driver package.

On the left navigation pane, click Settings to expand the section, then click Package Management to display the Package Management page.

Click Export SDA Packages to display the Export List page.

Select the driver package to export.

Select Choose Action > Export Selected.

Ensure that export completes before selecting a different export.

If you start an export of a package while an export process is in progress, the package waits in the queue. The packaging process can take a few minutes to several hours to complete, depending on the size and number of items in the package. The Status column indicates when each export completes.

Next, import the driver packages to the appliance.

Import driver packages to the appliance

You can import device-specific and network or storage driver packages from the restore share directory to the appliance. The Import feature is useful when drivers packages are larger than 1.5 GB and when you need to download driver packages from a manufacturer's website, such as audio, video, and chipset drivers that have complex configurations or dependencies.

On the left navigation pane, click Settings to expand the section, then click Package Management to display the Package Management page.

Click Import SDA Packages to display the Import List page, which lists all of the packages in the restore share directory.

For more information, see Import appliance components.

Select the driver package to import.

If the drivers are required for network booting, add the WinPE package.

Select Choose Action > Import Selected.

If the drivers are network or storage drivers, re-cache the drivers. See Re-cache the network and storage driver directory.

Understanding KACE Boot Environment drivers

When adding the network and storage drivers for the KACE Boot Environment (KBE), the drivers share directory requires re-caching the corresponding driver folder and building a new KBE.

There are two boot environment folders in the drivers share directory, and a folder for each supported operating system. Each KBE and operating system type requires its own driver version.

The drivers share directory has the following directory structure:

•

kbe_windows_x86

•

kbe_windows_x64

You can store any type of drivers in the drivers directory, but Quest recommends storing only the network drivers to this directory.

Add network and storage drivers manually

You can get the network and storage drivers from the manufacturer's website or from a different resource, and add the drivers manually.

Move any drivers that are currently stored in the drivers directory to a different source or device to prevent conflict. When switching from a lower version of WinPE KBE to a higher version or conversely, remove any drivers that were downloaded from the Driver Feed because the drivers are similar. Also, to avoid slow deployments, remove drivers for devices that are no longer in your environment.

The driver files from a manufacturer's site generally consist of .inf, .sys, and .cat files. There might be dependent files that the .inf file requires to load the drivers.

Access the drivers share directory of your appliance from the UNC (Universal Naming Convention) path \\<appliance>\drivers, where <appliance> is either the IP address or the DNS name of the appliance.

Download and extract the drivers from the manufacturer's website or any other source to a device that can access the appliance drivers share directory.

Add the driver files to the folder that corresponds to the process to which you want to make the drivers available. For example, add the KBE_driver_pack/kbe_windows_x86 directory in to the corresponding kbe_windows_x86 directory on the appliance. Also, copy the contents of the KBE_driver_pack/kbe_windows_x64 directory in to the corresponding kbe_windows_x64 directory on the appliance.