KACE Product Support Question

Booting KBE from USB and deploy via K2000

05/18/2013 6434 views

With all the problems in getting the Dell XPS 13 to boot and connect to K2000 via the StarTech USB-to-ethernet, the solution suggested by KACE support is to take a working KBE for that image and create a bootable USB with that specific KBE, and then select the correct deployment once booted into WinPE and onto the K2000.

Problem is that is work for a basic image, but when I try this same process for another image (created in 3.2, now on 3.5) it formats and installs onto the USB instead of the local HDD.  I've ensured the installation tasks match the working deployment image, hence why I'm so perplexed as to why this would be the case.

Now the USB-to-ethernet problem on KACE 3.5 I’ve been told will be solved with the SP1 which is due for release in July, however I have deployments which needs to be completed before then, and can’t wait for this patch to be released (which I will add is for hardware confirmed by Dell as compatible and their preferred XPS 13 to solve the simple issue of no Ethernet on the XPS 13).

If anyone is able to provide an answer/solution for this, I’d be extremely grateful as I can’t put our business on hold whilst KACE/Dell figure out that having their own hardware work on their own platform is paramount.


0 Comments   [ + ] Show comments


All Answers


Have you added the StarTech driver to your boot env.  I have managed to image lat10's (UEFI) via a TrippLite usb dongle and Lenovo Ultrabooks (legacy bios) via the usb3.0 lenovo dock.  I can pull the image directly from the kbox to the machine after booting.  I had to use a boot stick for the UEFI boot but was able to PXE for the Lenovo.


Answered 05/20/2013 by: SMal.tmcc
Red Belt

  • Thanks. Yes, have feed the drivers in via the Harvest tool and by manually adding them in with the help of KACE support. BIOS A06 and A08 are not compatible as per DELLs input, so got the A07 for the XPS L322X installed.
    Also, what I found is that when KACE upgraded from 3.4 to 3.5 the partitioning/swapping tasks of C & D are no longer required. What I have to do though is now clean the disk first and create the partitions using DISKPART:

    select volume 0
    remove all noerr
    select disk 0
    create partition primary size=15513
    select partition 1
    assign letter="C"
    create partition primary
    select part 2
    assign letter="D"

    And then format separately:
    format /q /y /fs:ntfs /v:Windows C:
    bootsect.exe /NT60 C:
    format /q /y /fs:ntfs /v:System D:
    bootsect.exe /NT60 D:

    Still to now test this with booting from USB for XPS until such time as KACE release SP1 (works on all other deployments)
    Funny enough, Ghosting a working image and deploying with Ghost USB (with ghost image preloaded) worked, and even quicker than KACE at that. Not ideal for multiple deployments as creating the USB with image takes hours, just the copying onto part - so eager to see SP1

  • This content is currently hidden from public view.
    Reason: Removed by member request For more information, visit our FAQ's.
  • For your USB to Ether problem.

    What is the reason you have to wait for SP1, why can't you put the drivers in the KBE yourself?

    What model of star tech are you trying to boot with?
    • Is the port USB 2 or 3? If it is 3.0 you need to add the usb3 drivers to the KBE also.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ