/build/static/layout/Breadcrumb_cap_w.png

Cannot boot new Latitude E5520 to KBE

This is my second batch of E5520s. I had no problem with the first batch (about 3 months ago). I just got in a new shipment, set them up and tried to boot. I get the Systems Deployment Menu and the computers try to connect (dots across the screen), but fail. I've tried both 32-bit and 64-bit KBEs and I have all of the Windows 7 drivers from the driver feed. I can connect other Dell models that I have in the office, just not these.


0 Comments   [ + ] Show comments

Answers (2)

Answer Summary:
Downgrading the BIOS
Posted by: samzeeco 11 years ago
10th Degree Black Belt
3

Try downgrading the BIOS. That's what fixes the issue for me, and it also worked for a guy over here: http://www.itninja.com/question/pxe-boot-environment-restart

If it's something like A13+ making it A12 would likely help as it did for me and the other user in the thread linked above.

 


Comments:
  • ageed it's most likely the bios, downgrade it - SMal.tmcc 11 years ago
  • Same, bios version change should fix it. - aaronr 11 years ago
Posted by: dpyett 11 years ago
Third Degree Blue Belt
1

I had a similar issue with a batch of Latitude E5530 laptops so this may help.  I simply couldn't get a scripted install to go down to them at all and I eventually discovered that it was all down to drivers.

I built one of my laptops using the Window DVD and manually installed a KACE agent onto it.  When the inventory item appeared, the model being reported back wasn't quite what I expected.  It was being reported as an "E5530 non-vPro".

I therefore connected to the UNC path for my K2100 drivers (\\k2100\drivers_postinstall\dell\windows_7_x86) and created an e5530_non-vPro folder in there.  I then copied over the drivers from the normal e5530 folder into that.

After PXE booting the other laptops, they could connect and install my scripted OS/apps etc no problem.

Hope this helps!

Dave.


Comments:
  • I had exact same issue with E5503 laptops however, drivers were my only issue. Did exactly what dpyett suggested and created an "E5530_non-vPro" folder into the drivers_postinstall directory and copied drivers into that folder. Problem solved!

    --Thanks! - apacheco 11 years ago
  • Excellent! I had been baffled by this too. We recently got a batch of E5530 Laptops and I couldn't get them to pickup the driver feed.

    After following the same technique the E5530 Laptops are now building perfectly. - Arcolite 11 years ago
  • Actually, the BIOS upgrade works as well. You don't have to downgrade. - hhall@cruhsd.org 11 years ago
 
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