/bundles/itninjaweb/img/Breadcrumb_cap_w.png
I am testing the Latitude 7290. I usually switch from UEFI to legacy. Now legacy is external only. I am at a loss. I finally got it to image through lots of trial and error but now it only tries to boot to the network and not to the hard drive. When I go into BIOS I have 3 choices. UEFI no secure UEFI secure and Legacy External. None of which show the hard drive as a bootable device. Thoughts and ideas are welcome. My supervisor believes this to be a driver issue. I think it's a BIOS issue. Help!

Also how long does it usually take for the drivers of new models to show up in the Driver feed?
7 Comments   [ + ] Show comments

Comments

  • I believe all newer systems no longer use legacy BIOS they use UEFI. I would guess that Legacy External is referring to an external HDD for booting.
  • I believe all newer systems no longer use legacy BIOS they use UEFI. I would guess that Legacy External is referring to an external HDD for booting.
  • two things:
    1. you are right with the driver issue.
    You need to build a new KBE with the right driver:
    Download the hdd driver from Dell, unzip it and add it to \\SDA\drivers\kbe_windows_x64, recache the drivers and as soon as it is done create a new KBE.
    2. the drivers for new models are avaiable as soon as they are staged, this means, if Dell provides the driver pack it will be made avaiable for all appliances which are in support. This is a midlevel driver injection so it does not allow you to boot a kbe to a system when the kbe has not the right drivers in it (I hope there will be a future solution to inject the nessesary drivers automaticly to ta prebuilt KBE, but right now you need to build it by yourself)
  • So I used to change boot mode to legacy in order to get the option to boot from NIC. How do I do this now? I can't imagine that the drivers will help as they are not applied until after network booting. I have been through the bios and tried everything I can possibly think of. What am I missing?
  • Are you sure this model supports Legacy Images?

    I don't have it, but looking at it's manual, I don't see it listed.

    See:
    7290:
    http://www.dell.com/support/manuals/us/en/19/latitude-12-7290-laptop/latitude_7290_om/boot-menu?guid=guid-ba801466-f452-4ff8-9755-61cc580866c0&lang=en-us

    VS.

    7480:
    http://www.dell.com/support/manuals/us/en/19/latitude-14-7480-laptop/latitude_7480_ownersmanual/boot-menu?guid=guid-4dd97d2e-cfca-4c85-bea7-eb971bb06b5d&lang=en-us

    I would discard the drivers, 100% not the issue...

    Maybe try a dummy UEFI Imaging and confirm this is either a BIOS\Compatibility issue.

    Contact the manufacturer to clarify what exactly is Legacy External.... I don't recall seeing that before.
  • Hi,

    Did you ever resolve this issue?
    I have the same problem with same Dell machine 7290
    Captured the image, deployed it and no bootable devices found.....
    Can you please help?

    Thank you!
  • Same issue here, did you ever get it resolved?

    Thank you!!!
    • I did! I went to KaceUserCon and go t so much information. On the computer you need to change to UEFI non-secure boot and enable the network stack. Then you should get IPV4 and IPV6 options when you boot into Kace. You also have to make changes to your DHCP server. If you have Server 2008 you will need to manually change this everytime you switch between UEFI and Legacy( my current situation) If you have 2012 you can set it to auto select. Port 67 on the DHCP server need to be ipxe.efi for UEFI and undionly.kpxe for legacy. We were still using kbox2000.0(way behind the times) Here is a link to explain how to set it to auto pick on a 2012 server.https://support.quest.com/kace-systems-deployment-appliance/kb/217556/dhcp-configuration-for-bios-and-uefi-pxe You can also use your existing images with a legacy/uefi conversion in your mid level tasks.Here is the process:

      1. Create a new Post-Installation Task
      a. Type: BAT Script
      b. Name: UEFI Legacy Conversion
      c. Runtime: SDA Boot Environment (Windows)
      d. BAT Script: (Use the following)
      bcdboot c:\windows /s s: /f UEFI
      bcdedit /store S:\efi\microsoft\boot\bcd /set {bootmgr} device partition=s:
      bcdedit /store S:\efi\microsoft\boot\bcd /set {memdiag} device partition=s:
      bcdedit /store S:\efi\microsoft\boot\bcd /set {default} device partition=c:
      bcdedit /store S:\efi\microsoft\boot\bcd /set {default} osdevice partition=c:
      Bcdedit /store S:\efi\microsoft\boot\bcd /set {FWbootmgr} displayorder {Bootmgr} /addfirst
      bootsect /nt60 s:
      2. Duplicate your existing Single partition image
      3. Remove the existing Legacy Preinstallation tasks (Single Partition, Format C, MBR)
      4. Add the Create UEFI Partitions (built in) at the Preinstallation section
      5. Add the UEFI Legacy Conversion task (created above) at the Mid-Level Section
      6. Save
      7. Deploy
      8. Profit!

      Please feel free to let me know if you have any other question


Community Chosen Answer

1
1. you are right with the driver issue.
You need to build a new KBE with the right driver:
Download the hdd driver from Dell, unzip it and add it to \\SDA\drivers\kbe_windows_x64, recache the drivers and as soon as it is done create a new KBE.
2. the drivers for new models are avaiable as soon as they are staged, this means, if Dell provides the driver pack it will be made avaiable for all appliances which are in support. This is a midlevel driver injection so it does not allow you to boot a kbe to a system when the kbe has not the right drivers in it (I hope there will be a future solution to inject the nessesary drivers automaticly to ta prebuilt KBE, but right now you need to build it by yourself)
Answered 03/26/2018 by: Nico_K
Red Belt

All Answers

0
Hi, thank you for your response, but to be honest it did not really knew how to do what you did.
I found out in the BIOS there is an option under System Configuration -> Integrated NIC : Enable UEFI Network Stack.
So i enabled it, captured a new image and boot the machine -> booted to the onboard nic, uploaded it and able to deploy that image without issue.
I guess they have changed things....but really took me so many tries before finding this fix!


Answered 09/19/2018 by: yche
White Belt