Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
Cannot connect to deployment share due to LAN driver not being installed

Answered Cannot connect to deployment share due to LAN driver not being installed

  • Wednesday, October 20, 2010 2:44 PM
     
     
    Sign In to Vote
    0

    Hello.

    I have just received a Lenovo T510 laptop. I am trying to load an WinXp x86 image on the machine from MDT 2010.

    I boot from the network, everything is fine, it loads the Litetouch WinPE x86 wim and it boots into winPE displays my custom background and gives me the first screen, Run Deployment Wizard - Run Windows Recovery - Command Prompt - etc etc.. When I run the Deployment wizard it says " A connection to the deployment share (\\...) could not be made. The deployment will not proceed. The following networking device did not have a driver installed. PCI\VEN_8086&DEV_10EA&SUBSYS_215317AA&REV_06"

    Now I have tried every driver I could find for this network card from win7 to vista to xp.. 32bit to 64bit. I have updated my deployment share many times (Completely regenerate the boot images.) and still nothing.

    Has anybody encountered this? I cannot seem to find anything that applies to my senario, and if they do, it does not seem to work for me.

    Any help would be overly appreciated.

     

     

All Replies

  • Wednesday, October 20, 2010 4:21 PM
     
     
    Sign In to Vote
    0

    This is definitely an issue with the appropriate NIC driver not being part of your boot Image. Windows Vista/7 32-bit drivers are what you need for the Pre-Installation Environment.

    After adding the drivers to your MDT server, and regenerating the boot images, did you go into WDS and add the newly created boot image to WDS and remove the old one?

    Are you using a Selection Profile for your WinPE driver injection?  If not I highly recommend doing so to minimize your boot image size, and to make sure only the drivers you need for WinPE are getting injected.

    Zak

    Zak Lyles
     
  • Wednesday, October 20, 2010 4:51 PM
     
     
    Sign In to Vote
    0

    I was under the impression that once you regenerate the boot image that it just updated the .wim file which is already added to WDS? --yes, rookie...

    I have added the vista drivers and win7 drivers a few times, different version, still nothing. and yes, I am using selection profile.

     
  • Wednesday, October 20, 2010 5:33 PM
     
     Answered
    Sign In to Vote
    1

    Hi, there are indeed problem with those Nic. I had similar issue with that Nic (same laptop) but with Windows 7 x64 driver. I finally decided to install with the DVD after many unsuccessful attemp. I tried 3-4 different driver, updated MDT to the Update 1 and manually injected driver with the DISM command.

    See this thread:

    http://social.technet.microsoft.com/Forums/en-US/mdt/thread/2baf7f09-4b3b-4bcc-a971-4ee0bedaf7fc

    • Marked As Answer by Maddogy Wednesday, October 20, 2010 6:44 PM
    •  
     
  • Wednesday, October 20, 2010 6:43 PM
     
     
    Sign In to Vote
    0

    JFMartel: it worked!!!!!! wow thank you so much!

    Thanks a million for posting, my head and wall thank you :)

     

     
  • Wednesday, October 20, 2010 7:43 PM
     
     
    Sign In to Vote
    0
    Well I'm glad you were able to make it work. What exactly you did?
     
  • Thursday, October 21, 2010 2:28 AM
     
     
    Sign In to Vote
    0

    This is definitely an issue with the appropriate NIC driver not being part of your boot Image. Windows Vista/7 32-bit drivers are what you need for the Pre-Installation Environment.

    After adding the drivers to your MDT server, and regenerating the boot images, did you go into WDS and add the newly created boot image to WDS and remove the old one?

    Are you using a Selection Profile for your WinPE driver injection?  If not I highly recommend doing so to minimize your boot image size, and to make sure only the drivers you need for WinPE are getting injected.

    Zak

    Zak Lyles


    You do not use Vista drivers with WinPE 3.0, it's Windows 7 based. 

    You should ideally create a WinPe x86 and  WinPE x64 folders and then create matching selection profiles for those and set your boot images to use those.

     

    MCTS: ConfigMgr, MDT / http://myitforum.com/cs2/blogs/cnackers/default.aspx

     
  • Thursday, October 21, 2010 10:47 AM
     
     
    Sign In to Vote
    0

    I used the Vista drivers from the Lenovo site..

    Used imageX to mount the litetouchx86 wim file  (yes I know DISM will do it as well)

    Make sure there are no spaces in the folder path that you mount the image or where you have your drivers stored

    Launched a command prompt

    Enter in:

    dism /image:<mounted_image_location> /add-driver /driver:<path_to_the_driver.INF>

    It will 'install' the driver to the image.

    Then used imageX to unmount and commit to the changes.

    Boot back into WinPE with the target machine and you should be good to go.

     
  • Thursday, October 21, 2010 12:11 PM
     
     
    Sign In to Vote
    0
    Why would you manually inject a driver when MDT will do it for you?  Just curious.
    MCTS: ConfigMgr, MDT / http://myitforum.com/cs2/blogs/cnackers/default.aspx
     
  • Thursday, October 21, 2010 2:08 PM
     
     
    Sign In to Vote
    0

    Just to make sure that MDT is doin it correctly.

    Chris, can you tell me what MDT is doin when multiple version of the same driver are present? My LitetouchPE is configured to take all the driver for the x86 platform and I do have a lot of different driver version for all my computer selection profile.

    Thanks

     
  • Thursday, October 21, 2010 2:30 PM
     
     
    Sign In to Vote
    0

    Just to make sure that MDT is doin it correctly.

    Chris, can you tell me what MDT is doin when multiple version of the same driver are present? My LitetouchPE is configured to take all the driver for the x86 platform and I do have a lot of different driver version for all my computer selection profile.

    Thanks

    If you import a duplicate driver, MDT will just create a "link" in the folder your are trying to import, that link goes back to the source path for the driver that was imported previously.  It calculates the hash value of the driver, if it's the same it will just create that link, if the hash is different then it will import the driver as a different one.  

    You should use a selectrion profile to limit the drivers you are injecting into WinPE (like a WinPE x86 selection profile), you really should only need one or two nic's with WinPE 3.0.  I highly you test what is actually needed instead of injecting everything.

    MCTS: ConfigMgr, MDT / http://myitforum.com/cs2/blogs/cnackers/default.aspx
     
  • Thursday, October 21, 2010 2:42 PM
     
     
    Sign In to Vote
    0

    You should use a selectrion profile to limit the drivers you are injecting into WinPE (like a WinPE x86 selection profile), you really should only need one or two nic's with WinPE 3.0.  I highly you test what is actually needed instead of injecting everything

    Mmm ok will defenitly try that one out. I was under the impression that I had too many driver loaded for my PE image. I had maybe 3-4 different driver for each .inf file.

    Thanks

     
  • Thursday, October 21, 2010 2:53 PM
     
     
    Sign In to Vote
    0
    The most network drives i've had to do at any client so far is 2 network drives.  So unless you are a huge shop with alot of models, you shouldn't need many drivers for WinPE 3.0
    MCTS: ConfigMgr, MDT / http://myitforum.com/cs2/blogs/cnackers/default.aspx
     
  • Thursday, October 21, 2010 3:19 PM
     
     
    Sign In to Vote
    0

    Well, YES I have MANY laptop/desktop to support. I'm working at a place where everybody can buy whatever they want... I'm stuck with Dell, Lenovo, Toshiba, Fujitsu, HP, Acer and Apple. We are mostly Lenovo but I do have to support most computer brand. oO

    I'll add the latest Intel Pro 1000 driver and Broadcom (the 2 most common) and see the results.

    Thank you

     
  • Thursday, October 21, 2010 3:22 PM
     
     
    Sign In to Vote
    0

    Well, YES I have MANY laptop/desktop to support. I'm working at a place where everybody can buy whatever they want... I'm stuck with Dell, Lenovo, Toshiba, Fujitsu, HP, Acer and Apple. We are mostly Lenovo but I do have to support most computer brand. oO

    I'll add the latest Intel Pro 1000 driver and Broadcom (the 2 most common) and see the results.

    Thank you

    Yeah, that won't help :) 

    It's usually the 82567 LM-3 Intel Gigabit driver that you need, and then probably a Marvel driver for those Fujitsu's.  Dell, Lenovo, HP should all use the Intel driver.  

    What you can do to help isolate is find the hardware ID of the network drive on the machine, then search drivers.xml for that driver and then just add that appropriate network drive to your winpe selection profile.

    MCTS: ConfigMgr, MDT / http://myitforum.com/cs2/blogs/cnackers/default.aspx
     
  • Thursday, October 21, 2010 3:44 PM
     
     
    Sign In to Vote
    0

    I already tweaked the driver to add the specific Hardware ID without any success. In my case I had an extra "&REV_06" at the end of the string which leads me to beleive that the problem isnt related to MDT but to the vendor.

    I will keep you informed on whatever happens.

    I'm now rebuilding my PE image with my WinPE driver profile to see what's happening. Will it remove all the previous I add installed or I should get a new LiteTouchPE file?

    Thanks

     
  • Thursday, October 21, 2010 3:57 PM
     
     
    Sign In to Vote
    0

    I already tweaked the driver to add the specific Hardware ID without any success. In my case I had an extra "&REV_06" at the end of the string which leads me to beleive that the problem isnt related to MDT but to the vendor.

    I will keep you informed on whatever happens.

    I'm now rebuilding my PE image with my WinPE driver profile to see what's happening. Will it remove all the previous I add installed or I should get a new LiteTouchPE file?

    Thanks

    Wait, what? you are manually modifying the ini file?  If you are having trouble with the actual driver, that's not an MDT issue, that's a vendor issue.  
    MCTS: ConfigMgr, MDT / http://myitforum.com/cs2/blogs/cnackers/default.aspx
     
  • Thursday, October 21, 2010 4:03 PM
     
     
    Sign In to Vote
    0

    I tried to modify the .inf file to include the specific Hardware string. Vendor .inf file include the same string ID but without the REV_06. I saw another thread in which you posted and that guy was having problem with that hardware ID too:

    http://social.technet.microsoft.com/Forums/en-US/mdt/thread/0daa8b1f-23dd-4b6d-a88d-753f92cb1b11

    I can't beleive, tough, that I'm the only one on this earth having problem using MDT 2010 with those computer... :(

     
  • Thursday, October 21, 2010 4:09 PM
     
     
    Sign In to Vote
    0

    I tried to modify the .inf file to include the specific Hardware string. Vendor .inf file include the same string ID but without the REV_06. I saw another thread in which you posted and that guy was having problem with that hardware ID too:

    http://social.technet.microsoft.com/Forums/en-US/mdt/thread/0daa8b1f-23dd-4b6d-a88d-753f92cb1b11

    I can't beleive, tough, that I'm the only one on this earth having problem using MDT 2010 with those computer... :(

    I would assume a T510 would use the Intel gigabit driver.

     

    And you are injecting the windows 7 driver? It should be like E1k6232 or E1k6264, or possibly E1Q or E1Y, but you want to look for E1K6232, as the middle 62 means windows 7, the 32/64 on the end is for the architecture.  

    MCTS: ConfigMgr, MDT / http://myitforum.com/cs2/blogs/cnackers/default.aspx
     
  • Thursday, October 21, 2010 7:01 PM
     
     
    Sign In to Vote
    0

    That's already what I was injecting. (e,k, q, y, r).

    Is it supposed to remove all the previously injected drivers?

     
  • Thursday, October 21, 2010 7:10 PM
     
     
    Sign In to Vote
    0
    well, not if you injected it manually... 
    MCTS: ConfigMgr, MDT / http://myitforum.com/cs2/blogs/cnackers/default.aspx
     
  • Thursday, October 21, 2010 7:16 PM
     
     
    Sign In to Vote
    0

    Mmmmm I guess I'll grab new PE file.

    Thanks for taking time to answer.

     
  • Thursday, October 21, 2010 7:39 PM
     
     
    Sign In to Vote
    0
    Not a problem, happy to help.
    MCTS: ConfigMgr, MDT / http://myitforum.com/cs2/blogs/cnackers/default.aspx
     
  • Wednesday, January 19, 2011 10:16 PM
     
     
    Sign In to Vote
    0

    I resolved the problem doing the following:

    • Download the drivers and import on MDT
    • Add the network drivers to the On-Site-Drivers folder that you are injecting to WinPE
    • Regenerate the images
    • Recreate boot image on WDS (This is the part that I was missing)
    After that everything work ok.

     

     

     

     
  • Wednesday, March 30, 2011 7:02 PM
     
     
    Sign In to Vote
    0
    Yes I am having the same issue with another Intel Driver. I am trying to create a 64 bit Windows 7 image. I have completed everything correctly just like the white paper has you do. I can't seem to find the correct driver. Which seems very odd to me because I used the computer with MDT on it to go to the internet with that driver and I am using the same exact computer to use as a reference. This stinks because after a couple hours to get this right now this little problem..What Gives Microsoft!!!!
     
  • Friday, April 01, 2011 1:00 PM
     
     
    Sign In to Vote
    0
    Yes I am having the same issue with another Intel Driver. I am trying to create a 64 bit Windows 7 image. I have completed everything correctly just like the white paper has you do. I can't seem to find the correct driver. Which seems very odd to me because I used the computer with MDT on it to go to the internet with that driver and I am using the same exact computer to use as a reference. This stinks because after a couple hours to get this right now this little problem..What Gives Microsoft!!!!

    Keep in mind you need the windows 7 driver.  Doesn't matter about the OS you install (although you'll need that drive for the actual OS) but winpe is based upon win7, so you need the win7 driver to be injected into winpe. 
    My blog: http://myitforum.com/cs2/blogs/cnackers/default.aspx
     
  • Friday, October 07, 2011 12:50 PM
     
     
    Sign In to Vote
    0
    Hi I'm still having the same problem. I have an HP Elite dc 8200 ( first one that we just got ) and I tried to run the deployment wizard. Right when I click that button it tells me that a networking device can't be found and that I need to download a specific LAN driver. The model I downloaded and injected into Out of Box Drivers on MDT 2010 is Intel 82579LM NIC driver. I updated the deployment share and still nothing. Isn't MDT supposed to update the boot.wim as well on WDS or do you have to do that manually ? But, I guess it would help if WDS was actually on the server, but for some reason it went missing and I can't find it anymore...whole other issue though.
     
  • Friday, October 07, 2011 1:00 PM
     
     
    Sign In to Vote
    0

    You boot image should be updated in your deployment workbench. But you have to replace the boot image in the WDS boot folder. As long as you are not updating it there, WDS will use the old image without the new drivers.

     

    Good luck

    • Proposed As Answer by JFMartel Friday, October 07, 2011 1:00 PM
    • Unproposed As Answer by JFMartel Friday, October 07, 2011 1:00 PM
    •  
     
  • Friday, October 07, 2011 3:47 PM
     
     
    Sign In to Vote
    0
    Well here's the thing so I downloaded Win 7 32 Bit ISO - extracted the boot.wim from it to put into the Boot Image file for WDS. I have a working LiteTouch_x86.wim in there already, but I added a new one because I thought that this new win 7 iso should have all the drivers necessary. So, I put in the boot.wim and then I even added a driver package for that specific NIC card for the hp 8200 and it said that it was a success. Rebooted the machine and then did PXE boot and went to the new Boot.wim file I put up. This led me to a Windows 7 setup screen and then later proceeded to say the drivers you need for this device aren't available, etc. I mean is there something I'm missing from this ?
     
  • Tuesday, October 11, 2011 12:44 PM
     
     
    Sign In to Vote
    0
    I actually was able to get it to work. Thanks though for your help !
     
  • Wednesday, October 12, 2011 2:13 PM
     
     
    Sign In to Vote
    0
    Well here's the thing so I downloaded Win 7 32 Bit ISO - extracted the boot.wim from it to put into the Boot Image file for WDS. I have a working LiteTouch_x86.wim in there already, but I added a new one because I thought that this new win 7 iso should have all the drivers necessary. So, I put in the boot.wim and then I even added a driver package for that specific NIC card for the hp 8200 and it said that it was a success. Rebooted the machine and then did PXE boot and went to the new Boot.wim file I put up. This led me to a Windows 7 setup screen and then later proceeded to say the drivers you need for this device aren't available, etc. I mean is there something I'm missing from this ?


    There is no difference in the boot.wim from the install media and the one generated by litetouch, they are both winpe 3.0 based.  Litetouch allows a mechanism for easily injecting different drivers and extrafiles into the boot images.

    There is a way to have WDS auto updated when you update the workbench:

    http://blogs.technet.com/b/mniehaus/archive/2009/09/09/automatically-update-mdt-2010-boot-images-in-wds.aspx

    My blog: http://myitforum.com/cs2/blogs/cnackers/default.aspx
     
  • Wednesday, October 19, 2011 11:34 AM
     
     
    Sign In to Vote
    0
    Okay. I'm still actually having issues capturing this HP 8200 and I'm not sure what I'm doing wrong. As a test I tried capturing an older model to see if that worked and it did. Recently I updated the Capture XP image and created a new task sequence for XP Capture and that worked. So, clearly it's not MDT's TS for capturing, but rather something to do with this newer model. I even updated the Out of Box Drivers to incorporate the hp8200's NIC and hdd driver and that still didn't do the trick. And I also incorporated those same drivers into the actual Windows XP ISO that I used to create the XP capture Task Sequence. So, I don't think now that there should be a drivers issue, then what else can it be ? I know in the XP capture sequence it's getting hung up on ZTIDrivers.wsf I think and I'm not sure where you change the code in that file so that it understands the storage driver for the hp 8200 ? Btw, what I did to fix the issue above was that I had to download the x64 drivers for Windows 2008 R2: Enterprise for the hp 8200 ( NIC Drivers ) and incorporate that into the Boot image on WDS and that's how I got the networking driver issue to go away. Now after I set up a capture it restarts after like hanging on 'sysprep is working' for a few hours and then reboots into MDT and says a connection cannot be made to \\server\deploymentshare....
     
  • Monday, October 15, 2012 2:59 PM
     
     
    Sign In to Vote
    0

    Hello,

    i am having the same problem with a new Toshiba laptop...

    what will be the right solution for this issue? I am using selection profiles for new hardware and drivers...but my nic driver isn`t added when windows starts in the deployment...

     
  • Monday, October 15, 2012 3:21 PM
     
     
    Sign In to Vote
    0
    Did you added the driver to the profile and assigned that profile to your task sequence?
     
  • Tuesday, October 16, 2012 8:18 AM
     
     
    Sign In to Vote
    0
    Yep i did...this working well for all other drivers/profiles...
     
  • Tuesday, October 16, 2012 9:18 AM
     
     
    Sign In to Vote
    0

    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?