/build/static/layout/Breadcrumb_cap_w.png

Optiplex 7440 AIO - KBE fails at network adapter

Pretty comfortable creating KBE on K2000 - but for the life of me I cannot get this new unit to work, on either x32 or x64.  I don't want to assume I know everything, so going to layout what I am doing - hopefully another set of eyes can show me the issue.

WAIK installed - believe I have Windows 8 or 8.1.  -> so I am trying to use the WINPE 4.0 CAB from Dell.  (I cannot install the Driver Pack from K2000 support, as our support ran out, without receiving notice).

I have blown away all drivers under these two folders:  Drivers\KBE_Windows_x86 & x64.  (I actually deleted all folders after getting frustrated).

Copied the x64 drivers into the x64 folder - so now I have two folders - Network & Storage.

Re-cached.

Built and uploaded KBE using Media Manager.  Opened said environment and looked at 3rd party drivers installed - here is what is displayed for the Intel Side:
oem4.inf       | e1c63x64.inf          | No    | Net         | Intel             | 5/2/2014   | 12.10.29.0  
oem5.inf       | e1d63x64.inf          | No    | Net         | Intel             | 9/29/2014  | 12.12.80.19 
oem6.inf       | e1r63x64.inf          | No    | Net         | Intel             | 3/11/2014  | 12.11.97.0  
oem8.inf       | ixn63x64.inf          | No    | Net         | Intel             | 12/5/2013  | 3.8.35.0    
oem9.inf       | ixt63x64.inf          | No    | Net         | Intel             | 12/5/2013  | 3.8.35.0    

I think one of these is the driver I need - but maybe not.  At any rate - I can PXE fine - but when I select the newly created KBE it always fails at the network spot.


3 Comments   [ + ] Show comments
  • Hi Hutch...,

    Did the fix mentioned by rjasutis work at all? We are starting to purchase 7440 AIOs and have come up with the same problem. The normal build procedure doesn't appear to work at all. My colleagues are telling me that they've spent too much time to resolve the KBE issue and have gone back to setting the PCs up manually. Cheers. - Tea_monkey 8 years ago
  • No. The driver pack continued to fail. I ended up downloading the drivers from Intel, and using those. There were 4 folders - ndis62, ndis63, ndis64, and ndis65. I copied them all in, cached, and created my PE build. Finally boots up. - hutcha4113 8 years ago
  • I'm having this exact same issue but with the 7440, 7510 & E5470 - chris.poston 8 years ago

Answers (2)

Posted by: hutcha4113 8 years ago
Second Degree Blue Belt
0
Suggestion did not work for me (Dell Driver Pack and or the 7440AOI).  Downloaded the NIC driver from Intel instead.  This let me PE boot. 

Comments:
  • would it be possible to share the link used for the intel driver? - chris.poston 8 years ago
    • Seconded! - agibbons 7 years ago
    • FWIW I saw reference elsewhere in a spiceworks forum to someone using https://downloadcenter.intel.com/download/25016/Network-Adapter-Driver-for-Windows-10 - agibbons 7 years ago
Posted by: rjasutis 8 years ago
White Belt
0
I'm always having problems with Dell's new hardware and their KBE's. 

In situations when I can't get a machine to boot using the WinPE driver pack on Dell's site, I follow you steps above but instead of the WinPE drivers, download the entire 7440AOI driver pack. Here is a link for the driver pack for Windows 8.1 http://en.community.dell.com/techcenter/enterprise-client/w/wiki/11655.optiplex-7440-aio-windows-8-1-driver-pack.  Download the file, extract it and copy the storage and network drivers to the KBE folders on the K2000. Recache the drivers and rebuild your KBE. This should solve the issue.

Comments:
  • how is one meant to know which files are for which driver when you download the CAB file? - chris.poston 7 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