/build/static/layout/Breadcrumb_cap_w.png

New Dell Latitude 5420 failing when trying to image

We just purchased a 5420 for a high end user and we were able to get the driver feed installed but when we go to deploy our image, it errors out on the first task which is Create UEFI partitions - S.WIM Error Fix.  The error KACE gives is Return Code: 2147942487, Error description Unknown error.  Tried retrying task and even Resume to skip but then it fails at Apply Image.

I noticed this laptop has a different BIOS (UEFI) than the others and we have combed through the settings to see if there is anything new that could be blocking it.  Anyone else run into this?


0 Comments   [ + ] Show comments

Answers (4)

Answer Summary:
Posted by: Nico_K 3 years ago
Red Belt
1

the Error code means that it cannot access the storage.
So the first step I would do is checking the Dell web page for the latest storage driver and bake it into the KBE.
Also make sure you have the latest driver pack and the latest version of the Media Manager and SDA to do so.

Posted by: bmontooth 3 years ago
Senior White Belt
1

Top Answer

Nico is on the right path.  It looks like I found the answer on another forum with someone using SCCM.  The issue is in the BIOS with the storage controller, it is set to RAID and when changed to AHCI it images fine.  Hope this helps fellow ninja's!


Comments:
  • Thank YOU!!! so much brother, had such of hard time imaging new Dell 3420, a real pain but your suggestion did the trick. - jgu 2 years ago
Posted by: andy.gilmore 3 years ago
White Belt
0

FWIW: I had the same problem, but I created a new KBE with the most up-to-date driver pack (found here: https://support.quest.com/download-install-detail/6111756). Using this updated KBE, the SDA was able to see and image the hard drive without needing to change storage modes in the BIOS.

Posted by: TimHR 3 years ago
Second Degree Blue Belt
0

We have (8) Dell Latitude 5500 and all of them fail at the Create UEFI partitions.

K2000 version 3.7

Steps

Downloaded the new KBE Driver pack PE10 -Version A22

I found the the correct driver that works  and created a new KBE with only that driver.

Still failing at  Create UEFI partitions.

Went into the samba removed all drives out of storage except the one that worked when I Manually installed the OS and uploaded the driver.

Saved updated k2000 driver share and created a new KBE.

Still failing at  Create UEFI partitions.

Other steps were changing from RAID to AHCI turning off Secure Boot, enabled Thunderbolt boot support, Fastboot to Thorough, Enabled Windows Boot Manager.

Still failing at  Create UEFI partitions.

Downloaded the new KBE Driver pack PE10 -Version A23

Ran Diagnostics - no issues

Reset BIOS to default

Still failing at  Create UEFI partitions.


Any  ideas would be a help.


Comments:
  • 1. Update to a current version (you are using 3.7, current version is 8.0, 8.1 is coming soon, there were so many changes, especially for UEFI clients, an easier way would export all packages, setup a new appliance and import the packages)
    2. build a new KBE with all nessesary drivers with the latest Media Manager
    3. test it again - Nico_K 3 years ago
    • Built a new server with the new 8.0 moved over our images. Had to change the ID #'s for each one.
      Built a new KBE from the new Media Manager also had to update the ADK to v2004. (ALL our images are v2004).
      Was immediately able to image the Latitude 5520 only thing was I had to change the boot environment to move hard to 1st boot then IPV4 removed IPV6 and left UEFI HTTP's Boot removed the windows boot manager.
      Legacy Boot mode is not supported on this model.

      Thank you for the help. - TimHR 3 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