MDT 2012, NIC driver injection 82579LM problem for HP Compaq 8300 Elite CMT
-
Monday, October 15, 2012 8:34 AM
Hi,
Just got 7 new computers in the door - pretty much the same setup as the HP 8200 Elite we have - including the NIC. Had hoped that the driversetup in MDT would be simple as most of the hardware should be the same. Oh so wrong...
The first problem is to find a working NIC driver - Have tried several different ones but none mentions the pci\ven_8086&dev_1502&subsys_33968086&rev_04 in the .inf files.
Wondering if anyone knows what _33968086&rev_04 really means in the Hardware ID's?
Any suggestion to how to make a workaround to this problem?
Waiting for a quote for 50 more of these and putting in a extra NIC isn't an option.
Have only tried deployement for Windows 7 x64.
Kjetil Jacobsen
All Replies
-
Monday, October 15, 2012 11:53 AM
You can run an hardware inventory assessment with HWinfo32/64 to see which NIC is used in that model.
Google then for the drivertype, add it to the driverstore, update your bootimage and selection profile, I know looking for drivers can be a real pain in the *ss sometimes.
Keep us posted, and if helpful please rate! Kind regards
- Edited by Rens Hollanders Monday, October 15, 2012 11:53 AM
-
Monday, October 15, 2012 2:36 PM
Thank you for your answer, sadly it didn't give me anymore information than I allready had.
The problem is that I can't find any drivers mentioning the Hardware ID subsys_33968086&rev_0 so I can't inject the right driver that will work with MDT. Have tried from HP Softpaq and from Intel and everytime the deployment stops at the same place.
kjetil
-
Monday, October 15, 2012 3:08 PM
This is what the BDD log says:
About to run command: cmd /c "\\KSUWDS\DeploymentShareLab$\Tools\X64\Microsoft.BDD.PnpEnum.exe" > C:\MININT\SMSOSD\OSDLOGS\PnpEnum.xml ZTIDrivers 15.10.2012 16:44:48 0 (0x0000)
Command has been started (process ID 1380) ZTIDrivers 15.10.2012 16:44:48 0 (0x0000)
Return code from command = 0 ZTIDrivers 15.10.2012 16:44:49 0 (0x0000)
Open Control File: Drivers ZTIDrivers 15.10.2012 16:44:51 0 (0x0000)
Filtered.Count: 0 ZTIDrivers 15.10.2012 16:44:51 0 (0x0000)
Indexed PnP Ids: 0 ZTIDrivers 15.10.2012 16:44:51 0 (0x0000)
...
Skipping Device PCI\VEN_8086&DEV_1502&SUBSYS_33968086&REV_04 No 3rd party drivers found. 11 ZTIDrivers 15.10.2012 16:44:51 0 (0x0000)kjetil
-
Tuesday, October 16, 2012 11:24 AM
Did you find a solution?
here same problem with toshiba laptop with 82579LM nic-card!
-
Tuesday, October 16, 2012 1:56 PM
Hi
Have a look at this thread and follow Johans advice
Thanks
Paul
Twitter: paul__iddon.....Any advice given in these forums should be tested in a non production environment before implementing.
-
Tuesday, October 16, 2012 2:13 PMThanks Paul, have allready tried Scenario #2 – Added Predictability, and it works. Only downside is the TS just for that model. Would prefer getting the right driver! kjetil
-
Tuesday, October 16, 2012 3:26 PM
Hello,
i have created a NEW TS...with the settings ALL Drivers...and then the driver is working..
when i am using the existing TS with same settings for drivers...it isn`t working.....
What is problem here??
-
Tuesday, October 16, 2012 3:34 PM
I have heard occasionally that this strange kind of things work. The vb error 13 type mismatch is the same example.
Perhaps some things underwater have been affected that you cant drawback.
Anyways good that it has been resolved.
Keep us posted, and if helpful please rate! Kind regards
-
Tuesday, October 16, 2012 4:38 PM
Hello Rens,
for me it`s not the ful solution.
I have many laptops installed using selection profiles.
Now i am deploying a Toshiba R950-101 laptop.
I have tried different ways to install the NIC-driver....until now i have the following situation:
With these settings the NIC driver is installed....but the rest of the drivers for this laptop not (the drivers for this laptop are in the selection profile voor R9501-101):
when trying this settings the NIC driver isn`t installed and the deployment will not go further after the first windows-step in task sequence:
Anybody who has a solution for this strange issue??
-
Tuesday, October 16, 2012 5:52 PM
If the device works when using the All Drivers profile, but not the one based on te model then I would think that the correct driver is not in the model based selection profile.
You need to find that driver that is being installed with the All Drivers rofile and add it to the model based selection profile.
-
Wednesday, October 17, 2012 6:15 AM
Now:
Unless using the settings : "install all drivers from the selection profile", i am missing many drivers : usb,vga,wifi....
Before the installation of windows i see many driver-copies....but i am missing hardware at the end of the installation!
What could be the problem?
-
Tuesday, November 20, 2012 10:44 AMAny solution to this problem allready? I have this problem also.
-
Tuesday, November 20, 2012 1:23 PMIn our situation the problem was a /P after the copyx command.
-
Wednesday, November 21, 2012 3:06 AMWe had that same issue with some laptops as well as the 8300. Here is the SoftPac number sp58964 and the link to the download the file for 64 bit. Once we loaded this into MDT all was well. For driver injection we are using Johan's Scenario #3 – Total Control for driver injection with the MDT database.
-
Wednesday, November 21, 2012 5:37 AM
Search microsoft driver catalog , if any driver there helps
http://catalog.update.microsoft.com/v7/site/Search.aspx?q=ven_8086%26dev_1502
Shiv
.png)
