Chatta subito con l'assistenza
Chat con il supporto

KACE Systems Deployment Appliance 9.1 Common Documents - Administrator Guide

About the KACE Systems Deployment Appliance Getting started Using the Dashboard Configuring the appliance Setting up user accounts and user authentication Configuring security settings Preparing for deployment Managing device inventory Using labels Creating a Windows or Linux Boot Environment Managing drivers Capturing images Capturing user states Creating scripted installations Creating a task sequence Automating deployments Performing manual deployments Managing custom deployments Managing offline deployments About the Remote Site Appliance Importing and exporting appliance components Managing disk space Troubleshooting appliance issues Updating appliance software Glossary About us Legal notices

Best practices: Create a KACE Boot Environment (KBE) for Windows

Best practices: Create a KACE Boot Environment (KBE) for Windows

Some business environments can have strict policies and software that may keep the KACE Media Manager from creating a KACE Boot Environment (KBE) successfully.

You may need to set up an isolated system for the purpose of creating KBEs. Here is the recommended flow of actions:

The recommended process for creating a new KBE is provided below.

Move out (or delete) any items in the kbe_windows_xXX directories located in the appliance drivers share (\\appliance\drivers).
On the General Settings page, enter the appliance IP address.
Ensure the WAIK or WADK Path field points to the correct version of Windows AIK or Windows ADK:
On the Create KBE page, on the General tab, review the automatically generated name for the boot environment. You can edit this value, but keep in mind that the KBE name must be unique. Quest recommends that you include the architecture, WinPE version, and the date in the name. For example: WinPE 5 x64 4-5-2019.
Click Upload KBE.

Managing drivers

You can manage the network and mass storage drivers required to build the KACE Boot Environment from the drivers share directory. You can manage the drivers that the operating system requires by enabling the Driver Feed, which downloads and installs drivers to the driver_postinstall directory.

The appliance's driver library is a network share that stores the drivers that the appliance and Remote Site Appliance deployments use. The appliance automatically installs the drivers as part of the deployment, and enables uploading drivers for peripherals and hardware that are not included in the Source Media or the KACE Boot Environment (KBE). The appliance hosts Samba shares, and provides three directories to help you manage drivers.

Downloaded drivers are stored in the drivers_postinstall share directory using the following folder structure:

Virtual devices: <OS_name>/<OS_version>/<OS_platform>/any/vmware|hyperv/. For example: /windows/7/x64/any/vmware/.
Physical devices: <OS_name>/<OS_version>/<OS_platform>/<build_version>|any/<manufacturer>/<system_ID>/. For example: /windows/7/x64/any/dell/049a/.

Ensure that you set the appliance Samba Share Password on the General Settings page.

About adding drivers to the drivers_postinstall directory

You can organize the drivers under the drivers_postinstall directory using the above folder structure.

About adding drivers to the drivers directory

Drivers that are included in a single .exe or .msi file require extracting the files before adding the drivers to the folder.

About adding drivers to the restore directory

NOTE: The Package Management Export feature creates packages for larger driver files that you can import from the restore directory to the appropriate drivers share directory to make the drivers available to the appliance.

Add drivers to system images

Add drivers to system images

Enabling the Driver Feed for sysprepped system images captured from the KACE Systems Deployment Appliance and the Remote Site Appliance (RSA) adds the drivers automatically when you deploy the image. You can also install missing drivers on the device where you captured the image, re-capture the image, then upload the image to the appliance.

Use the Microsoft Sysprep tool to generalize the image to resolve duplicate device names and duplicate security identifiers (SIDs). For more information on the best practices for capturing images, go to

For sysprepped system images captured from an RSA, the corresponding drivers should be available on the KACE Systems Deployment Appliance and synchronized from the KACE Systems Deployment Appliance to the RSA.

For Windows K-Images and WIM images, the Sysprepped field on the System Image Detail page indicates if an image is sysprepped.

On the left navigation bar, click Deployments, then click System Images to display the Systems Images page.
Select the image to display the System Image Detail page.
Under Deploy options, ensure the Use driver feed (only with Sysprepped images) check box is selected.
Optional. You can enable this option by default on the General Settings page:
On the left navigation pane, click Settings > Control Panel to display the Control Panel, then click General Settings to display the General Settings page.
Under Imaging Options, select the Enable driverfeed for newly captured sysprepped images check box. Selecting this option automatically adds drivers to the target system deployed with newly captured sysprepped system images.
Click Save, and return to the Deploy Options on the System Image Detail page.
Optional: Click Duplicate to copy the image and edit it, as needed.
Click Save.

Adding drivers to scripted installation deployments

Adding drivers to scripted installation deployments

You can enable the Driver Feed to update the appliance with the latest device-specific driver packages automatically. When this feature is enabled, any older driver versions that are detected are deleted from the appliance, and replaced with their latest versions. You can also get the drivers from a manufacturer's website or from a different resource, and add the drivers manually to a scripted installation deployment.

During a scripted installation deployment, the appliance automatically pulls all of the drivers from the drivers directory in to the scripted installation. When device drivers or other drivers are in the drivers directory, the scripted installation might fail.

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione