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. |
5. |
• |
The recommended process for creating a new KBE is provided below.
a. |
Move out (or delete) any items in the kbe_windows_xXX directories located in the appliance drivers share (\\appliance\drivers). |
b. |
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. |
b. |
d. |
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. |
h. |
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.
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.
• |
You can add device drivers that do not get updated from the Driver Feed to the drivers_postinstall directory. |
• |
You can organize the drivers under the drivers_postinstall directory using the above folder structure. |
• |
Drivers that are included in a single .exe or .msi file require extracting the files before adding the drivers to the folder. |
• |
You can add driver packages that are larger than 1.5 GB 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. |
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 https://support.quest.com/kb/121734.
For Windows K-Images and WIM images, the Sysprepped field on the System Image Detail page indicates if an image is sysprepped.
1. |
On the left navigation bar, click Deployments, then click System Images to display the Systems Images page. |
2. |
3. |
Under Deploy options, ensure the Use driver feed (only with Sysprepped images) check box is selected. |
2. |
On the left navigation pane, click Settings > Control Panel to display the Control Panel, then click General Settings to display the General Settings page. |
3. |
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. |
4. |
4. |
5. |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Nutzungsbedingungen Datenschutz Cookie Preference Center