/build/static/layout/Breadcrumb_cap_w.png

K2000 BIOS/PXE Boot Issues

 

This is a list of machines which we know have issues PXE booting with particular BIOS versions and also a list of machines that had issues previously, but the issue has been resolved.

To make sure the issue was not driver related we used the support provided driverpack. When you see KBE-DPA08x64 and KBE-DPA08x86 it means: KBE is K2000 boot environment, DPA08 is the version of the driverpack, x64 and x86 is the architecture used.

Models with Issues:

The following table includes models that currently have issues PXE booting.

 

Model

BIOS revision

Notes

Latitude Slate Tablet PC

A09

A09 - Fails to complete PXE boot.  Was not able to USB KBE network boot as a workaround. 

XPS 13(L321X)

A08

A08 - Fails to complete PXE boot.  On A08 you can see the PXE menu but once the ISO loads, it stops at the "loading boot sector.... booting..." message and the NIC link lights die.

**Use A07 as a workaround

XPS 13(L322X)

A10

A10 - Fails to complete PXE boot. Will load the KBE and then reboot back to the BIOS screen

**Use A06 as a workaround

Venue 11 Pro

A04 - 5130

although the Venue Pro 11 will PXE, it doesn't work with the star-tech dongle or the usb2ethernet dongle, p/n part number TXXF8 that ships with the tablet [which is supposed to support pxe], just the doc or an asix usb2ethernet dongle. tested at latest a04 bios. Also, of note: the systems come in various models, as detailed in this article; http://www.dell.com/support/troubleshooting/us/en/19/KCS/KcsArticles/ArticleView?c=us&l=en&s=dhs&docid=635828 models: 7130/7139 will function in legacy mode and can PXE boot, 5130 will not.


 

Resolutions:

The table below indicates models that had issues in the past, but an update BIOS version resolved the issue.  This table is maintained for the purpose of record keeping and as a means of knowing that a particular system needs updating.


Model

BIOS
revision

Notes

Opti 740

2.2.7

Not Enough Memory during attempting to boot via PXE with 2.2.5
**resolved with 2.2.7

Opti 760

A13

cust reported heavy latency (network) which was resolved by updating the BIOS. He wasn’t sure of previous version
**A13 reported to have resolved issue.

Opti 780

A13

Opti 780 various bios fail to boot via PXE - A12 confirmed to work
**A13 - Does PXE boot to KBE-DPA08x64 or KBE-DPA08x86

Opti 790

A15 

**A15 - Does PXE boot to KBE-DPA08x64 or KBE-DPA08x86

Opti 7010

A12 

**A12 - Does PXE boot to KBE-DPA08x64 or KBE-DPA08x86

Opti 980

A13 

**A13 - Does PXE boot to KBE-DPA08x64 or KBE-DPA08x86

Opti 990

A15 

**A15 - Does PXE boot to KBE-DPA08x64 or KBE-DPA08x86

Opti 9010

A10

**A10 using this driver: http://www.dell.com/support/drivers/us/en/19/DriverDetails?driverId=KCXX0

E5420

A09 

**A09 - Does PXE boot to KBE-DPA08x64 or KBE-DPA08x86

E5520

A09 

**A09 - Does PXE boot to KBE-DPA08x64 or KBE-DPA08x86

E5530

A07

Systems with A03 fail to boot into KBE when PXE booting. Systems on A02 and A07 work fine

E6220

A09

**A09 - Does PXE boot to KBE-DPA08x64 or KBE-DPA08x86

E6320

A14 

**A14 - Does PXE boot to KBE-DPA08x64 or KBE-DPA08x86

E6420

A16 

**A16 - Does PXE boot to KBE-DPA08x64 or KBE-DPA08x86

E6520

A14

**A14 - Does PXE boot to KBE-DPA08x64 or KBE-DPA08x86 

3330

A05

**A05 - PXE boots to PE4/5

A02,A03,A04 - Fail to PXE

XT3

A08

A03, A06 perhaps others fail to PXE boot, A08 resolves the issue.

XPS 15

A04

A03 was a problem
**A04 resolves issue.

XPS 14z (L412Z)

A06

A02 was a problem
**A06 resolves issue

T3500

A15 

**A15 - Does PXE boot to KBE-DPA08x64 or KBE-DPA08x86

T5500

A13

**A13 - Does PXE boot to KBE-DPA08x64 or KBE-DPA08x86

T3600

A07 

**A07 - Does PXE boot to KBE-DPA08x64 or KBE-DPA08x86 

T5600

A08 

**A08 -  Does PXE boot to KBE-DPA08x64 or KBE-DPA08x86

T7600

A05

**A05 - Does PXE boot to KBE-DPA08x64 or KBE-DPA08x86 

M4600

A13

**A13 - Does PXE boot to KBE-DPA08x64 or KBE-DPA08x86

M6700

A08 

**A08 -  Does PXE boot to KBE-DPA08x64 or KBE-DPA08x86

R5500

A09

**A09 -  Does PXE boot to KBE-DPA08x64 or KBE-DPA08x86
-A05 fails

Vostro V130

Realtek NIC

These Systems are adversely effected by Non MS DHCP, VOIP, etc. even when other systems with Intel, Broadcom, etc. will PXE ok with latest driverpack.

Vostro 3460

A14 

**A14 - Does PXE boot to KBE's built with the following driver: http://www.dell.com/support/drivers/us/en/19/DriverDetails/Product/vostro-3460?driverId=YN802&fileId=3126814206&osCode=W732  

Mini 1012

Realtek NIC

These Systems are adversely effected by Non MS DHCP, VOIP, etc. even when other systems with Intel, Broadcom, etc. will PXE ok with latest driverpack.

Opti 390

Realtek NIC

These Systems are adversely effected by Non MS DHCP, VOIP, etc. even when other systems with Intel, Broadcom, etc. will PXE ok.



Models that were reported as having issues, but did not.


Model
BIOS 
revision
Notes
2120 A00 

**A00 - Does PXE boot to KBE-DPA08x64 or KBE-DPA08x86

Also has no issues deploying a Windows 7 scripted installation. 

E5430 A03vPro **A03 - Does PXE boot to KBE-DPA08x64 or KBE-DPA08x86
E6330 A02  **A02 - Does PXE boot to KBE-DPA08x64 or KBE-DPA08x86
E6430 A12 **A12 - Does PXE boot to KBE-DPA08x64 or KBE-DPA08x86
E6530 A07  **A07 - Does PXE boot to KBE-DPA08x64 or KBE-DPA08x86
T1650  A07  **A07 - Does PXE boot to KBE-DPA08x64 or KBE-DPA08x86 

Comments

  • BIOS A09 for E6220 resolves the issue - dgrishey 11 years ago
  • Thanks!!! - kwhatcher 11 years ago
  • E5430 non-vPro BIOS version A03 did not PXE boot to x86. I updated to A07, and it works now. - sfigg 11 years ago
  • T3600-Bios A07 resolves PXE Issue - KACE_Mary 11 years ago
  • Optiplex 7010 with A09 will PXE boot as long as you make sure that the switch port you are connected to is in spanning tree portfast mode. DHCP times out too quick otherwise. - iceheat 11 years ago
  • Optiplex 7010 with bios A12 will PXE boot on a netgear unmanaged gigabit switch if the bios is set to legacy boot mode. It will not work in UEFI boot mode on this switch. I'll try UEFI boot on a switch with spanning tree portfast features whenever I get my hands on one. It will not boot on a powerconnect 3024 or 3048, they have spanning tree, but not the portfast feature. - lysinger 11 years ago
    • @lysinger KACE does not support UEFI PXE booting. The platform has not been standarized at this time, so its a moving target.
      Corey
      Lead L3 Enterprise Solutions Engineer, K2000
      If my response was helpful, please rate it! - cserrins 11 years ago
  • In Cisco at least, the setting for a port is spanning tree OR portfast. So if spanning tree is off, then portfast is on and vice versa. - jamie_kace 11 years ago
  • Latitude E6330 still doesn't PXE boot, even after downgrading the BIOS to A02; I've tried A06 and A08 versions also; any suggestions? I can't even get the laptop to boot from USB - norrij 11 years ago
    • In the lab, we have this model successfully pxe booting with A02. I will ask that newer bios be tested. What error message are you getting?

      Corey
      Lead L3 Enterprise Solutions Engineer, K2000
      If my response was helpful, please rate it! - cserrins 11 years ago
      • Yeah, previous models were working ok, but the two newest ones are not. The error message is:
        PXE-E51: No DHCP or proxyDHCP offers were received.

        PXE-M0F: Exiting Intel Boot Agent.
        Selected boot device failed. Press any key to reboot the system. - norrij 11 years ago
    • If you cant even get it to boot from the USB you might consider recreating a KBE and trying it instead. Do other models still boot into the KBE? - samzeeco 11 years ago
      • All older models boot into KBE. I'm only having issues with the new ones. - norrij 11 years ago
    • Can you email me the service tag of the machine you are having issues. We need to compare the specs of the one you are using to what we have.

      Corey
      Lead L3 Enterprise Solutions Engineer, K2000
      If my response was helpful, please rate it! - cserrins 11 years ago
  • Apparently some of the newer Dell Latitude notebooks take issue with Cisco spanning tree protocol. As soon as I moved to a switchport where spanning tree protocol wasn't configured, I was able to boot my KBE. - cholton 10 years ago
  • Hi, I am having issue with E7440 model, getting error 1231 , unable to mount Kbox share at \\x.x.x.x\peinst. I have downloaded the latest NIC driver, updated the BIOS, added drivers manually to the share but still same error, Any help would be great to fix the issue. - sherazq 10 years ago
  • Sherazq, see http://www.itninja.com/question/k2000-and-the-new-e7440-ultrabook. This should reolve your issue. Let me know if it helps. - KACE_Mary 10 years ago
  • I have a few brand new Opti3020's and they are not seeing the KBox when trying to image. When trying to ping it is not seeing the I/P address. When the PC is connected to the network without going through KACE it sees the server when pinging. I've worked with the KACE Tier 1 and 2 techs, we have updated the drivers on both the KBOX and the PC which did not work and we have verified that the PC has the latest version of Bios A00. Do any of you have suggestions or encountered this type of issue? - Lisa_McMillin 10 years ago
  • Lisa, let me see what I can do for you. I see the ticket that you have. Can you please place a 3020 service tag so I can see the specs? - KACE_Mary 10 years ago
  • Update your ticket :) - KACE_Mary 10 years ago
  • Is there an updated definitive list for this issue? We have multiple XPS 13 (9333) laptops and it has the exact same issue as described for the XPS 13(L321X) at the top of the page. We are using a USB to Ethernet adaptor. - shoddinott 9 years ago
  • For the T3600 and T3610, Try plugging the hard drive into SATA0. KACE didn’t recognize the drive when it was in HDD1 for some reason. The SATA slots are labeled right next to each one. This worked for me on BIOS A13. - Gary.Cooper 9 years ago
This post is locked
 
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