SDA

KBE

KBE

Create KBE 9.X

KBE 9.0 – 9.1 – 9.2 (Oct 15, 2024)
Reference KB article 184391

Before creating a KBE, it is crucial to prepare a Windows 10 or Windows 11 system and drivers. It's recommended to use an isolated system, as antivirus software can interfere with the KBE build process.

Steps to Create a KBE:

  1. Set Up a VM
    Ensure that the VM can connect to the KACE System Deployment Appliance (SDA) and has the following installed:

  2. Backup and Update Drivers
    a. Go to the KACE SDA Samba Share Driver folder and back up these directories:
    \\KaceSDA\drivers\kbe_windows_x64
    \\KaceSDA\drivers\kbe_windows_x86

    Note: You may need these drivers to recreate a KBE for previous versions of Windows.

    b. Delete all folders and files inside the above directories.
    c. Download the latest KBE Driver Pack from Dell Support. Extract the CAB file using 7-Zip or WinRAR (Windows' default extractor won't work). Then, copy the folders as follows:

    • Copy the x64 folder to: \\KaceSDA_IP\drivers\kbe_windows_x64
    • Copy the x86 folder to: \\KaceSDA_IP\drivers\kbe_windows_x86

    d. Re-cache the drivers in the KACE SDA console by going to Settings → Appliance Maintenance.

  3. Use the Media Manager
    a. In the SDA UI, navigate to Library → Source Media → Media Manager, and download the KACE SDA Media Manager tool.
    Open the Media Manager, go to the General Settings tab, and fill out the following:

    • SDA hostname
    • IP address
    • Samba share password
      Click Test Connection. More details about this can be found here.

    b. In the Create KBE tab, you’ll find different settings groups for customizing the KBE creation process. Typically, the default settings work for uploading the KBE.

For more details on creating a KBE, refer to the documentation here.

Post Installation task order

The order in which you place your post-install tasks can significantly impact the success of your deployments. To ensure a smooth process, here are three key considerations when determining the sequence of these tasks:
  1. System Lockdown Risks: Does this task have the potential to lock down the system, causing other tasks to fail? (e.g., domain joining or anti-virus installation)
  2.  Automation Dependencies: Does the task install or join something that could trigger other automation? (e.g., KACE agent initiating managed installs and scripts, domain join enforcing GPOs that launch scripts)
  3. Task Dependencies: Are there any dependencies for this task, or is this task a prerequisite for another? (e.g., network installation should be completed before any dependent installations)

As a best practice, the final three tasks in your sequence should typically follow this order:
  1. KACE agent installation (if required)
  2. Anti-virus or security software installation
  3. Domain joining

image.png