/build/static/layout/Breadcrumb_cap_w.png

Has anyone been able to image a Latitude 5540?

I've loaded the drivers manually into the appropriate folders on the SDA, afterwards I always re-cache the drivers. I've done this with nearly 40 different models and have yet to run into issues.


I've got a PXE environment setup for both Windows 10 and Windows 11. Neither work, and the system won't actually boot into the PXE system.


We are currently working on a life cycle change and have around 290 of these machines to image.


Thanks!


1 Comment   [ + ] Show comment
  • Are you saying you do not get the pxe boot menu that gives you the option of choosing a KBE when manually booting to network? - cserrins 1 year ago

Answers (9)

Posted by: WhatsATOF 1 year ago
Senior White Belt
1

We image 5540s on the regular. The key to imaging systems is to make sure the PXE environment has the latest Dell driver pack installed into the PXE boot image. After that it doesn't matter about drive RAID/AHCI settings. Should boot fine.


Posted by: EmmaF 1 year ago
Yellow Belt
0

We've imaged a few 5540s using the SDA Driver Feed without issue.

If you're not able to PXE-boot, it sounds like you're not at a point where drivers are applied. At what point exactly does it fail? What BIOS settings are you using?

Posted by: rtfmftw 1 year ago
Senior White Belt
0

Other than changing the RAID config it's default.


Comments:
  • At what point does it fail? Are you getting an error message? Does it reboot into HTTPS boot or something? - EmmaF 1 year ago
    • Nothing really other than it can't ping the SDA. When using a USB NIC with a generic driver it works just fine but this doesn't really help with the volume of devices we need to deploy. - rtfmftw 1 year ago
Posted by: Daniel Christian 1 year ago
Senior White Belt
0

We are having the same issue with the same model.  We have the appropriate drivers and have recached.  I've tried Raid on and off, booting to integrated NIC and IPV4 with thunderbolt adapter (thunderbolt boot enabled), the best i can do with Raid off is get to the point where it is unable to ping the appliance says check DHCP options or network drivers.  This is via USB thunderbolt.


With Raid On we can get it to boot to the SDA GUI but when selectin the scripted install it is unable to load the windows 10 image due to being unable to create the UEFI partition.


Comments:
  • After trying a generic USB NIC we can also get them to image but with the volume we have to get done this really isn't possible. We would need to purchase hundreds of adapters to get this deployment done. - rtfmftw 1 year ago
Posted by: Daniel Christian 1 year ago
Senior White Belt
0

update, USB Thunderbolt worked, just needed a different usb thunderbolt adapter.

Posted by: mwhiting 1 year ago
White Belt
0

Have you included the Intel RST VMD Controller 9A0B driver?
It's required for RAID operations

Posted by: vgeesink 1 year ago
White Belt
0

After updating the latest WinPE drivers pack to the bootimage, we were able to install again.

Posted by: rrichardson@ahbelo.com 1 year ago
White Belt
0

I am imaging Latitude 5440, I had to change in the BIOS under Storage to select AHCI/NVMe instead of RAID.  If I remember correctly I had to update the version Kace2000 9.1.178.  Hope this helps.

Posted by: technosupergeek 1 year ago
White Belt
0

I’ve run into this with several models.  I run the default RAID configuration and don’t change anything.  We image with MECM but honestly it’s all the same.  Always make sure to have the RAID drivers (Intel RST VMD Controller) installed on the boot image.  It typically comes in the driver packs Dell provides

Don't be a Stranger!

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

Sign up! or login

Share

 
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