/build/static/layout/Breadcrumb_cap_w.png

Task Error 4294967295 on Dell E6430

Hello,

I have been able to successfully deploy an image from the KACE to a Dell E6430 laptop in the past, so I was puzzled when I came to this error this morning on yet another deployment of an E6430 laptop. 

I then realized that there is one difference. The laptop that the deployment failed on has an i7 chip in it, while the others have an i5 chip in them that the deployments do work on.

I assume this would mean I would have to manually copy the chipset driver files to the KACE for the i7? Would this just be a matter of copying the chipset driver files to the already existing E6430 directory?

I'm new at the KACE, so any assistance or tips would be greatly appreciated.

Thanks

0 Comments   [ + ] Show comments

Answers (2)

Posted by: Burya 10 years ago
White Belt
1
If your system is not the E6430s which has separate drivers in the driver feed tool that you can download directly then you will need to insert a driver for the i7 processor in the post install drivers folder, the easiest way is to use the driver harvester tool or double driver to grab the driver using the folder structure you need and copy it to the folder on the k2.

Comments:
  • Thank you Burya! I appreciate your comment. - Bentley 9 years ago
Posted by: nickbaldwin86 10 years ago
Yellow Belt
0
Try and only put the Network and Storage drivers in the driver feed folder. I NEVER put chipset drivers in and it works every time.

Good luck.
Nick

Comments:
  • Nick, thank you. I will try that. - Bentley 9 years ago

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