MDT not installing network driver
-
Friday, September 07, 2012 11:20 AM
Hi,
I'm having an odd issue with new Toshiba laptop (Satellite pro L870) my school has purchased. I downloaded the drivers from Toshiba’s site directly. I have extracted the drivers from the .exe and then further unpacked all other .exe then I imported the drivers into MDT Deployment Share (server: srv-vapp01).
Then Updated the MDT production Deployment share (with a complete rebuild), and then replaced boot wim with the latest boot wim (On sever: srv-vdc02)
Then pxy boot to MDT production x86, the PE environment loads up fine and I select the Student custom image that has been premade and is in use on all other student computers. This works fine and downloads the custom image fine.
It then unpacks and installs windows as normal with no issues. It then shuts down and boots into windows 7 and then I get an error message as follows:
A connection to the deployment share (\\SRV-VAPP01\MDTPRODUCTION$) could not be made.
The following network device did not have a driver installed.
PCI\VEN_10C&DEV_8168&SUBSYS_FB371179&REV_07
Which makes no sense as if this where the case it would have never been able booted up into the PE environment, and would not have been able to download and unpack the custom student image…
So obviously I’m left very confused anyone able to offer any insight?
I have also updated the deployment share MDT Build with the drivers at the suggestion of my schools external ICT support contract with Viglen. This did nothing and as yet they have still yet to come back to me with another solution
- Edited by Mr Agincourt Friday, September 07, 2012 11:20 AM
- Edited by Mr Agincourt Friday, September 07, 2012 11:20 AM
- Edited by Mr Agincourt Friday, September 07, 2012 11:21 AM
- Edited by Mr Agincourt Friday, September 07, 2012 11:21 AM
All Replies
-
Friday, September 07, 2012 12:49 PMTry pulling the driver directly from the Realtek site. You are using a x86 PE Image. Are you deploying x86 or x64? Perhaps you have integrated the x86 driver, which works fine for PE, but after the PE Phase the x64 Installation is missing the x64 version of the driver.
-
Friday, September 07, 2012 1:18 PM
Hi Agin,
Somethings to check before you can go any further in this testing.
1. Are you using the default TS provided by Microsoft?
2. After you extracted the driver, have you noticed any inf or cab files of the network driver ( ;) it should be as it is NETWORK)
3. Search PCI\VEN_10C&DEV_8168&SUBSYS_FB371179&REV_07 is this ID points to correct driver which you have downloaded. May be you hardware has a different NIC card with different drivers
Thats all at the moment :)
Thanks,
Rakesh Sahoo
-
Saturday, September 08, 2012 5:06 AM
Hi,
While importing drivers , you may get some warning (in yellow colour) related to driver.
so remove the drivers which are giving warnings and angain update the deploymemt share and check.
You can save the output of import driver message output and cross verify.
-
Monday, September 10, 2012 9:22 PM
This is explained well here. In short, download the drivers, check that the ID is correct in the out-of-box drivers section. then update your deployment share to recreate your WinPE boot disk.
You should do more, like create selection profiles but I wont confuse you.
Blog: http://scriptimus.wordpress.com
- Proposed As Answer by Shrek46 Thursday, September 20, 2012 4:41 PM
-
Thursday, September 20, 2012 1:24 PM
Thanks for the info guys, the Realtek drivers have both x64 and x86 in one package and i have tried them (2012 drivers) as well as the ones from Toshiba (2011 drivers), as well as the drivers from Viglen (2010 drivers) all seem to have the same issues they work right up until windows 7 boots. Then it fails to install the drivers and hults the MDT process.
One bit I did leave out which was quite an important point was if I then use the same driver I imported into MDT and manually installed it onto windows it then workes fine. Which has really confused me. Oncce this is done I can carry on the MDT process from where it left off.
I've not yet tried to remove any of the drivers that conflict and I do get some when I rebuild the MDT share so I'll take a look at that.
- Edited by Mr Agincourt Thursday, September 20, 2012 1:24 PM
- Edited by Mr Agincourt Thursday, September 20, 2012 1:55 PM
- Edited by Mr Agincourt Thursday, September 20, 2012 1:56 PM
- Edited by Mr Agincourt Thursday, September 20, 2012 1:59 PM
- Edited by Mr Agincourt Thursday, September 20, 2012 2:00 PM
- Edited by Mr Agincourt Thursday, September 20, 2012 2:02 PM
- Edited by Mr Agincourt Thursday, September 20, 2012 2:02 PM
- Edited by Mr Agincourt Thursday, September 20, 2012 2:06 PM
- Edited by Mr Agincourt Thursday, September 20, 2012 2:07 PM
-
Thursday, September 20, 2012 2:03 PM
On a side note to people who have told me to updated the MDT share and the MDT PE boot.wim....
This isn't my first time doing this I've been running the MDT/creating custom imagies etc. for my School for the last 3 years. This is the first time I have ever come accross anything like this.
I'm sure you all mean well but please don't teach me to suck eggs. As stated in my first post I HAVE UPDATED MDT SHARE and then UPDATED THE PE boot.wim, otherwise I'd never have been able to add new drivers for all the computers I've setup on the network over the last 3 years. Also if I'd not done those steps, win PE would not have booted for me to be able to select a custom image and have it successfully download and unpack onto the computer.
Please read the issue I'm having rather than just half reading it and giving me the stock helpdesk responce to my issue.
- Edited by Mr Agincourt Thursday, September 20, 2012 2:04 PM
-
Monday, October 15, 2012 3:07 PMDid you find a solution?
-
Tuesday, October 16, 2012 9:20 AM
I have tried adding the nic-drivers to the reference-image using dism /add-driver.
But still same problem!
After installing the driver manually...(from the same directory) the NIC is working.
The problem NIC = Intel 82579LM Gigabit Network Connection.
Anybody with a solution?
.png)
