Chat now with support
Chat with Support

KACE Systems Deployment Appliance 9.0 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 Imaging Mac devices About the Remote Site Appliance Importing and exporting appliance components Managing disk space Troubleshooting appliance issues Updating appliance software Glossary About us Legal notices

Update Windows drivers

Update Windows drivers

You can update the Windows Pre-installation Environment (WinPE) related drivers necessary to build a KACE Boot Environment (KBE) and add the drivers to the appropriate kbe_windows_x64 or the kbe_windows_x86 share directory on the appliance.

1.
Go to https://support.quest.com/kb/111717 to download the drivers. Use your Support credentials to log in, then select KBE Driver Pack.
2.
Navigate to the <appliance>/driver_packs folder to download the appropriate WinPE driver pack.
3.
Manually copy the drivers to one of the following directories:
◦
\\<appliance_IP>\drivers\kbe_windows_x86
◦
\\<appliance_IP>\drivers\kbe_windows_x64
4.
Re-cache the drivers. See Re-cache drivers.
Set the new KBE as the default.

Set new KBE as default for the appliance

Set new KBE as default for the appliance

You can set a KACE Boot Environment (KBE) as the default KBE for the appliance.

* 
NOTE: You can also set the default KBE for each linked RSA. For more information, see Set default KBE for the RSA.

If you change the share password, create a new KBE using the new password.

1.
On the left navigation pane, click Settings > Control Panel to display the Control Panel, then click General Settings to display the General Settings page.
2.
Under Boot Environment Options, select the new KBE.
3.
Click Save.
* 
TIP: When you review the details of a KBE using the Boot Environment Detail page, the Default field indicates if the selected KBE is a default boot environment.

Hide boot environments from the PXE boot menu

Hide boot environments from the PXE boot menu

Preboot Execution Environment (PXE) is a standard client–server environment that allows administrators to boot a PXE-enabled system using a collection of files stored on a network server. In a default installation, a PXE boot menu lists all Windows and Linux boot environments that exist on the appliance. Boot environments provide the drivers and other resources that a target device requires to network boot from the appliance.

In some cases, your appliance may have one or more older KACE Boot Environments (KBEs) that you do not want to appear in the PXE (Preboot Execution Environment) boot menu. You can choose to display or hide boot selected boot environments available on the KACE Systems Deployment Appliance, or on all associated Remote Site Appliances.

1.
On the left navigation pane, click Deployments, then click Boot Environments to display the Boot Environments page.
2.
Select the boot environment that you want to install to the USB flash device to display the Boot Environment Detail page.
3.
To hide this boot environment from the KACE Systems Deployment Appliance PXE boot menu, select Hide Boot Environment from SDA PXE Boot Menu.
4.
To hide this boot environment from the PXE boot menu of all associated Remote Site Appliances, select Hide Boot Environment from all RSA PXE Boot Menus.
After selected this option, if you want this boot environment to appear on a specific Remote Site Appliance, and to remain hidden on all other Remote Site Appliances, on the Remote Site Detail page, under Boot Environments, in the row containing the newly hidden Boot Environment, you must clear the Hidden check box. Making this change does not affect any other Remote Site Appliances.
5.
Click Save.
6.
Initiate the PXE boot menu on the associated appliance, and verify that the newly hidden boot environment no longer appears in the list.

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:

•
Set up a system or a virtual machine (VM) that can reach the appliance with the following software:
◦
Windows 7, 8, 8.1 or 10
◦
Windows AIK, Windows ADK 8, Windows ADK 8.1 or Windows 10 ADK
◦
The latest version of the KACE Media Manager
* 
•
Do not add that system to your domain.
•
Do not install any security or anti-virus software.

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

1.
Prepare the KBE drivers.
a.
Move out (or delete) any items in the kbe_windows_xXX directories located in the appliance drivers share (\\appliance\drivers).
b.
Download the KBE Driver Pack for the desired WinPE version. For more information, visit https://support.quest.com/kb/SOL111717.
c.
Extract the downloaded driver pack and copy the contents from the desired architecture's folder into the kbe_windows_xXX directory located in the appliance drivers share.
* 
NOTE: You should only have the drivers for one WinPE version at a time in the kbe_windows_xXX directories.
2.
Build the KBE.
a.
Open the KACE Media Manager.
b.
On the General Settings page, enter the appliance IP address.
c.
Enter the Samba share password.
d.
Ensure the WAIK or WADK Path field points to the correct version of Windows AIK or Windows ADK:
▪
WinPE 3 needs to point to the Windows AIK installation directory.
▪
WinPE 4 needs to point to the Windows ADK 8.0 installation directory.
▪
WinPE 5 needs to point to the Windows ADK 8.1 installation directory.
▪
WinPE 10 needs to point to the Windows ADK 10 installation directory.
e.
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.
f.
Select the desired architecture.
g.
Select the desired language.
h.
Click Upload KBE.
If you need to add additional drivers for your model to work, contact Quest Support to ensure the driver pack is updated with those drivers.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating