none
MDT - The following networking device did not have a driver installed RRS feed

  • Question

  • Using MDT 6 and WDS

    x2 different dell laptops E5440 and E7250 using the same nic card - Intel I218-LM

    Booting into litetouchpe_x86 wim

    get error

    The following networking device did not have a driver installed

    PCI\VEN_8086&DEV_155A&Subsys_0DE2039&REV_04 - E5440

    PCI\VEN_8086&DEV_15A2&Subsys_062D1028&REV_03 - E7250

    Downloaded the drivers from the intel site and loaded im certain the correct drivers I m loading both x86 and x64 as when i look at the inf files it shows

    PCI\VEN_8086&DEV_155A and PCI\VEN_8086&DEV_15A2 however the subsys number does not match does this matter?

    so in MDT i load the drivers into the WinPE folder then updated the share which completes successfully then updated the image in WDS but i still get the error.

    Tried using the Dell drivers as well same problem

    What am i doing wrong ?

    Any help would be great.

    Quick update still having the same problem but i went into winpe and opened the .inf from MDT and I do see PCI\VEN_8086&DEV_15A2&SUBSYS_062D1028 in there dont see REV03 not sure if this makes the difference? so the drivers do match in WINPE folder and still getting the same error.

    Tuesday, April 7, 2015 11:09 AM

Answers

All replies

  • In case you aren't doing this.

    Best to follow this method to keep your drivers well managed: http://deploymentresearch.com/Research/Post/325/MDT-2013-Lite-Touch-Driver-Management

    You can get your PE drivers from Dell here: http://en.community.dell.com/techcenter/enterprise-client/w/wiki/2065

    The PnP drivers for those two models are slightly different in the latest CABs, but as long as you're just using the PE drivers and the driver management method you shouldn't have issues. I say that because I'm support many Dell models including those.

    My x64 PE folder only has 28 drivers to cover everything I support, 10 of which are network. The x86 has 25 total.


    If this post is helpful please vote it as Helpful or click Mark for answer.

    Tuesday, April 7, 2015 9:00 PM
  • Thanks for the tip

    I have a WinPE folder but i havent separated it into x86 or x64 folders

    I tried using the network from the E7250 cab file originally which failed, havent used the WINPE Cab files.

    I will try that and see how i get on.

    Thanks again. 

    Wednesday, April 8, 2015 8:56 AM
  • Go there in the end

    WINPE 5.x didnt work. had to use WINPE 4.x working fine now

    http://en.community.dell.com/techcenter/enterprise-client/w/wiki/2065

    thanks Dan.

    • Marked as answer by ArnoldRimmer Wednesday, April 8, 2015 3:10 PM
    Wednesday, April 8, 2015 11:30 AM
  • Glad it's working for you now. The PE 5.x drivers are for the latest ADK if you're rolling out Windows 8.1 https://technet.microsoft.com/en-us/library/dn247001.aspx#Win81

    Don't forget to mark this thread as answered


    If this post is helpful please vote it as Helpful or click Mark for answer.

    Wednesday, April 8, 2015 1:20 PM
  • yeah that's right I was going ehh when looking at the inf files.

    marked as answered thanks again


    Wednesday, April 8, 2015 3:16 PM
  • So, what's the correct resolution? To use Dell WINPE 4.x drivers?

    I'm having exactly same issue with Dell E7250 laptop and MDT2013.

    Thursday, April 9, 2015 1:09 AM
  • Yes that's right use WINPE 4.x drivers - , it works for E5450 and E6540 too
    Thursday, April 9, 2015 7:14 AM
  • The answer is it depends on if you are using WAIK or ADK and which version of them. The latest ADK uses WinPE 5.1, the first ADK uses PE 4.0. If you are deploying Windows 8.1, then you need to upgrade to the latest ADK. The last WAIK used WinPE 3.1

    I only use PE 5.x drivers for all models I support because I'm using the latest ADK.

    You can get the ADK update here - http://www.microsoft.com/en-US/download/details.aspx?id=39982


    If this post is helpful please vote it as Helpful or click Mark for answer.



    • Edited by Dan_Vega Thursday, April 9, 2015 1:28 PM added link
    Thursday, April 9, 2015 1:23 PM
  • After ADK is updated, do I need to update the deployment share and re-create the boot image?

    Trying to install Windows 7 x64 on Dell E7250 and still struggling with the PCI\VEN_8086&DEV_15A2&Subsys_062D1028&REV_03 no driver error.

    Wednesday, April 15, 2015 10:55 PM
  • Yes you will need to force regeneration of your boot images.

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Wednesday, April 15, 2015 11:06 PM
    Moderator
  • That driver is for the Intel ethernet

    x64 Network Intel I2xx/825xx 10/10 0/1000 Ethernet Network Driver ReleaseID:
    MXH3C
    DellVersion: A09
    VendorVersion: 19.2.0.0

    I don't have that model in our pool, but that network card and driver is used in many Dell systems. The closest I have is the E7450, make sure you have the driver or at least an up to date version. You can verify what a driver supports by right clicking on it and then going to Properties.


    If this post is helpful please vote it as Helpful or click Mark for answer.

    Thursday, April 16, 2015 1:52 PM
  • Yeap, the driver is listed. WAIK was updated and boot image was re-generated and uploaded to WDS, but still same error:

    No driver for PCI\VEN_8086&DEV_15A2&Subsys_062D1028&REV_03

    Wednesday, April 22, 2015 5:21 PM
  • If the problem you're having is in PE and you are keeping your drivers well sorted, use a selection profile.

    Create a PE profile and only select the folder that contains your PE drivers.

    In the deployment share properties, go to the PE tab and set your selection profile such as below.

    Repeat the same process for x64 or just replace x86 examples with x64 if you aren't supporting 32bit at all.

    Update your deployment share and regenerate your boot image.


    If this post is helpful please vote it as Helpful or click Mark for answer.

    • Proposed as answer by anry555 Wednesday, April 22, 2015 9:06 PM
    • Unproposed as answer by anry555 Wednesday, April 22, 2015 9:06 PM
    Wednesday, April 22, 2015 7:43 PM
  • Finally got it solved by using the solution from HP forum.

    Added Win8_x64 network driver from Dell to the boot image and now able to deploy the image. I'm deploying Windows 7, so not sure why the Dell Win7_x64 and WinPE4.0 drivers for the same network adapter didn't work on E7250 laptop.


    • Edited by anry555 Wednesday, April 22, 2015 9:13 PM
    • Proposed as answer by anry555 Wednesday, April 22, 2015 9:59 PM
    Wednesday, April 22, 2015 9:12 PM
  • Do you know what version of the driver you got to work? I'm having a similar issue and can't seem to get any version to work.

    One thing we have just noticed is that the drivers are digitally signed, when we imported them using Dell Command and the downloaded CAB file for the E5X50 we had a lot fail but a lot import ok, when I've tried to manually import we got an error saying 'The selected driver is not applicable to any supported platforms.'

    A bit of digging and I found the i218-LM driver hadn't been imported using dell command - because it is digitally signed. A bit more digging and I discovered this issue https://support.microsoft.com/en-us/kb/3025419 as our SCCM install is on a Windows Server 2008 R2 box.

    The hotfix is now installed and the drivers now are being imported, still haven't found one that works yet though. Will keep you posted.

    ****UPDATE*****

    It looks like the problem all along was the failed imports of the drivers due to SHA-2 signing.

    Imported the intel drivers(which now works after installing the above hotfix) as we are using WinPE 4.0 the win 8 x64 driver was the one that worked. Happy Days!!


    • Edited by cumbrianblues Friday, April 24, 2015 11:12 AM updated
    Friday, April 24, 2015 9:06 AM
  • Thank you cumbrianblue for your post which has helped me hugely in resolving a driver issue with a Dell Latitude E5550 laptop. I was having a similar issue with the Network Adapter not being recognised in our WINPE4.0 boot image, I attempted to import the Dell Driver CAB for WinPE4.0 from this link

    http://en.community.dell.com/techcenter/enterprise-client/w/wiki/4376.winpe-4-0-driver-cab

    The import of the Windows 8 drivers failed due to the fact that we have SCCM2012 installed on a Win2008R2 server. I applied the Hotfix located here:

    http://hotfixv4.microsoft.com/Windows%207/Windows%20Server2008%20R2%20SP1/sp2/Fix420818/7600/free/462274_intl_x64_zip.exe

    I then rebooted the server, imported the drivers from the CAB which successfully imported. I then injected the drivers into our WinPE4.0 boot image, booted the Laptop to this boot image which successfully loaded without moaning about a missing Network Adapter. Thanks again!


    Friday, June 26, 2015 8:31 AM
  • E7250 Windows 8 driver did it for me, using ADK2013. Thanks for your help
    Thursday, November 5, 2015 12:04 PM
  • If the problem you're having is in PE and you are keeping your drivers well sorted, use a selection profile.

    Create a PE profile and only select the folder that contains your PE drivers.

    In the deployment share properties, go to the PE tab and set your selection profile such as below.

    Repeat the same process for x64 or just replace x86 examples with x64 if you aren't supporting 32bit at all.

    Update your deployment share and regenerate your boot image.


    If this post is helpful please vote it as Helpful or click Mark for answer.

    E7250 Windows 8 driver did it for me, using ADK2013. Thanks for your help

    Hi All,

    MDT/WDS N00b over here. I cant seem to find drivers for this driver package on 64 bit Vista to work with our PE 6.x environment.

    We have some E7250 laptops that will not pick up IP addresses on DHCP and therefore wont Image.

    What is ADK2013?

    How does the method quoted above resolve this issue? its just good practice?

    Any ideas would be VERY welcome :)

    EDIT - this is the info ive got regarding driver

    PCI\\VEN_8086&DEV_15A2&SUBSYS_062D1028

    &REV_03\\3&11583659&0&C8

    • Edited by Ilai.Schechter Monday, March 14, 2016 4:35 PM Addition of driver details
    Monday, March 14, 2016 3:44 PM
  • I've not heard of WinPE 6, as far as I know it jumps from 5.1 to 10. Get your Dell drivers for PE here - http://en.community.dell.com/techcenter/enterprise-client/w/wiki/2065

    ADK is located here - https://msdn.microsoft.com/en-us/windows/hardware/dn913721.aspx?f=255&MSPPError=-2147217396#adkwin10


    If this post is helpful please vote it as Helpful or click Mark for answer.

    Monday, March 14, 2016 4:40 PM
  • We are using SCCM 2012 R2 – WIN PE 2 (Vista x64). The laptop in question is a latitude E7250:
    PCI\\VEN_8086&DEV_15A2&SUBSYS_062D1028&REV_03\\3&11583659&0&C8

    It appears there are no drivers available regarding this PE for the Intel I218-LM, is there a workaround, possible INF manipulation?
    Tuesday, March 15, 2016 10:18 AM
  • Hey all, 

    tried going through the motions on some generic drivers - didn't get very far. our next option is to upgrade our entire MDT infrastructure (!!!!!!)  a project that may take a good few weeks. 

    Anyone got any ideas 

    Monday, March 21, 2016 2:49 PM
  • Since you're pretty new to MDT, get yourself a good book such as:

    Deployment Fundamentals, Vol. 6
    http://deploymentartist.com/books

    That series has really good step by step instructions with illustrations and gives practical tips for "real world" usage.

    As you build your deployment share be sure to create internal documentation, especially when you implement tweaks or customizations.


    If this post is helpful please vote it as Helpful or click Mark for answer.

    Monday, March 21, 2016 3:03 PM
  • RESOLVED THIS ISSUE!!!!!!

    From the CAB file which is unzipped, remove the network driver folder. Import all the drivers except those in the network driver folder. Once that has imported, then import the network drivers. This resolved the issue for me.

    Jacky

    P.S (i was only importing the x64, not the entire folder with x86 and x64)

    • Edited by arch2015 Thursday, April 7, 2016 4:57 PM
    Thursday, April 7, 2016 4:57 PM