My organization has a k2000 appliance that we use to deploy Win7 x64 to Dell.  The appliance is presently running v3.6.98680.

Recently we purchased some Latitude E7450 laptops and discovered that the preboot environment did not have NIC driver for them and we were consequently unable to deploy to these systems.  I went through the process of downloading the appropriate NIC driver, added it to the driver share and rebuilt a new PBE.  When I use the new PBE I built I no longer have the issue of being unable to mount the kbox share and I can select the scripted installation I want to run.

However, the issue I am facing now is the scripted installation starts running and when it gets to the post-install task list, it errors out because the Windows 7 installation that was just completed does not have a driver for the NIC installed.  In the k2000 appliance, I downloaded the Win7 x64 driver feed for this system.  Also, on one of the systems exhibiting this error, I opened device manager and examined the properties of the NIC.

It shows up with the following hardware ids:

VEN - 8086
DEV - 15A2
SUBSYS - 062E1028

Back on the k2000, if I click on the drivers tab and look in the list of drivers, I can see that there is a matching driver, so I'm unsure as to why this driver is not being installed during a scripted installation.  I've recached the Win7 x64 drivers in the k2000, so I'm kind of stumped as to what I should be looking at next.

Any suggestions?
Answer Summary:
Cancel
2 Comments   [ + ] Show Comments

Comments

  • Are you deploying the image from the K2000 directly or an RSA?
  • I'm not sure what an RSA is, so I think from the k2000 directly.
Please log in to comment

Answer Chosen by the Author


  • Thank you for the info. I will try updating the appliance.
  • I updated the appliance and the problem has gone away. Thank you.
Please log in to comment

Answers

0
You may need to put in a support ticket to have an engineer tether in to update the VB Script that detect and copies the drivers. Chances are the script is reporting a slightly different model number, as SMal.tmcc suggested in his links.

A quick fix would be to run the driver_feed_discovery_tool.vbs located in the samba share of the k2000 on the laptop.
\\k2000\drivers_postinstall\feed_tools\driver_feed_discovery_tool.vbs


Create a matching path in the drivers folder and copy the drivers there.
My E7450 driver shows up like "\\K2000\drivers_postinstall\dell\windows_7_x64\e7450_7450" but you would want it to match the highlighted area in the picture above.
Answered 08/10/2015 by: jleitsch
Orange Senior Belt

  • If this is the case, we would recommend upgrading to 3.7.116629, because this version has the exceptions stored in a file that gets updated nightly so that no tether is required!
    -Corey
    • Good to know that this is a live document. I haven't had new equipment come in since my upgrade to 3.7. I just remember getting all the issues with my laptops showing up as non-vpro and messing up the WMI calls in the vbscript.
Please log in to comment
Answer this question or Comment on this question for clarity