Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
MDT 2010 Injected drivers not found post-reboot

已答复 MDT 2010 Injected drivers not found post-reboot

  • Thursday, October 06, 2011 5:32 AM
     
     
    Sign In to Vote
    0

    I am performing a NEWCOMPUTER deployment type on a HP DL580 G7 server.  Server is able to PXE boot and view the MDT Wizard, choose my task sequence, and install my image.  When it completes its first reboot and starts Windows 2008 R2 Ent, it no longer is able to see it's network drivers. I have tried setting inject drivers task to "install all" from profile as well as "Install only matching" driver.  My BDD.log shows the following:

     

    <![LOG[LTI initiating task sequence-requested reboot.]LOG]!><time="22:57:44.000+000" date="10-05-2011" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

    <![LOG[Property start is now = ]LOG]!><time="23:08:45.000+000" date="10-05-2011" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

    <![LOG[Microsoft Deployment Toolkit version: 5.1.1642.01]LOG]!><time="23:08:45.000+000" date="10-05-2011" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

    <![LOG[Write all logging text to \\172.17.255.3\deploymentshare$\logs\%OSDComputerName%]LOG]!><time="23:08:45.000+000" date="10-05-2011" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

    <![LOG[Validating connection to \\172.17.255.3\deploymentshare$\logs\%OSDComputerName%]LOG]!><time="23:08:45.000+000" date="10-05-2011" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

    <![LOG[No networking adapters found, The network drivers for your device are not present]LOG]!><time="23:08:45.000+000" date="10-05-2011" component=

     

    This is after in WinPE previous phases I can see it finding the correct driver and loading it.  Can anyone please recommend further troublehooting steps I can take?

    Here is my full BDD.log if anyone would like to look at it: http://dl.dropbox.com/u/46718/BDD.log

    NOTE: In this log you will see that I manually installed the HP NC375i Gigabit driver and manually continue the sequence.

    Any help is greatly appreciated!





     

All Replies

  • Thursday, October 06, 2011 6:27 AM
     
     
    Sign In to Vote
    0

    What if you try copy network drivers locally and then point to that folder for driver installation?

    If this will work and driver for network card will be installed, then drivers are fine for Server 2008. What version WinPE do you use?

    Are the drivers compatible?

    Sometimes MDT couldn`t find correct driver to apply, got many cases with NVIDIA drivers. This can be the same.

    I can recommend workaround - to install driver from task sequence with WMI query.

     
  • Thursday, October 06, 2011 6:44 AM
     
     
    Sign In to Vote
    0

    Yes the drivers are injected and i can see them at C:\Drivers\Net.  If I manually install the drivers everything works fine.  However MDT is not automatically installing them.

    Currently under out of box drivers I only have one folder "WinPE x64" which contains all my drivers.  I have a selection profile pointing to this folder, and my task sequence uses "Install all drivers" from that selection profile.

     
  • Thursday, October 06, 2011 7:17 AM
     
     
    Sign In to Vote
    0
    What OS do you use in WinPE?
     
  • Thursday, October 06, 2011 2:25 PM
     
     
    Sign In to Vote
    0

    I believe it is the default WinPE in WDS/ MDT 2010.  Appears to use Vista.

    Thanks for your time

     
  • Friday, October 07, 2011 6:19 AM
     
     
    Sign In to Vote
    0

    I have seen problems with difference in WinPE. Can you try to do following:

    1 - Check for NIC driver update for your Server OS. It seems that driver works correctly in Vista, but not in Server 2008 R2.

    2 - Try to add older NIC drivers if there are.

     
  • Monday, October 10, 2011 8:22 PM
     
     
    Sign In to Vote
    0

    Hello for your step #1 I do not believe this is the case as if I install the driver manually it works just fine.  Ie. Go to device manager, click update drivers and point it to C:\Drivers\Net   it finds the injected drivers and installs them correctly.  I will try step #2 soon.

    Does anyone know what process is used by Windows to find the drivers that are in C:\Drivers\Net and install them automatically?  Are there any logs I can check to determine what is not happening here?

     

    Thanks!


    • Edited by Jason Fritts Monday, October 10, 2011 8:22 PM
    •  
     
  • Monday, October 10, 2011 10:52 PM
     
     
    Sign In to Vote
    0

    I believe I have determined the cause of my problem, but I still dont know how to fix it.

    My DevicePath is not updated during the task sequences.  If I look at HKLM\Software\Microsoft\Windows\CurrentVersion\DevicePath , I only see C:\Windows\inf and C:\drivers\net is not mentioned anywhere.

    If I look at my bdd.log I see the following:

    Vista identified, skipping update of Device Path

    Why would this be the case?  I am installing Windows 2008 R2 Enterprise, but why would updating DevicePath ever be skipped?

    Thanks

     
  • Monday, October 15, 2012 2:49 PM
     
     
    Sign In to Vote
    0

    did you find a solution for this?

    i have the following error using mdt 2012 : No networking adapters found, The network drivers for your device are not present

     
  • Monday, October 15, 2012 7:16 PM
     
     
    Sign In to Vote
    0
    My only solution thus far has been not relying on MDT for driver injection for R2 Enterprise and just using Dism /add-driver on the .wim file manually.
     
  • Friday, December 07, 2012 8:23 PM
     
     
    Sign In to Vote
    0

    I am getting the same issue. I worked around it originally by mounting the wim and adding the regkey. this was only happening on 1 vista wim that is not updated much.

    Now I have upgraded to mdt 2012 update 1 and all of my vista task sequences can no complete.

    The drivers are being found and copied to c:\Drivers, but the OS will not load them. I see the same thing in my ZTIDrivers log:

    Vista identified, skipping update of Device Path

    This is even happening on the virtual machine I use to create the base Vista images (on that task sequence I am not using a custom wim, just the files from the Vista DVD)

    This is not happening on windows 7 or 8 task sequences all drivers are loading fine.

    We need a solution to this issue

     
  • Friday, December 07, 2012 8:31 PM
     
     
    Sign In to Vote
    0
    Can you upload your logs somewhere (not here, somewhere it can be downloaded)? How about your Task sequence?
     
  • Friday, December 07, 2012 9:12 PM
     
     
    Sign In to Vote
    0

    you can grab the logs & TS here:

    http://sdrv.ms/THRwYV

     
  • Sunday, December 09, 2012 5:50 AM
     
     Answered
    Sign In to Vote
    0

    I was able to resolve my issue awhile back after I noticed that the Unattend.xml associated with the task sequence/OS I was running had the following compnent missing.  Once I added this component to the offlineServicing pass all was well again.  I also updated to MDT 2012 but I dont think that was the fix.  So check your unattend.xml located under DeploymentShare\Control\SequenceName

       <settings pass="offlineServicing">
          <component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <DriverPaths>
                    <PathAndCredentials wcm:keyValue="1" wcm:action="add">
                        <Path>\Drivers</Path>
                    </PathAndCredentials>
                </DriverPaths>
            </component>


    • Marked As Answer by Jason Fritts Sunday, December 09, 2012 5:50 AM
    •  
     
  • Monday, December 10, 2012 4:20 PM
     
     
    Sign In to Vote
    0

    Jason, This is allready in the unattend file and drivers are not being loaded. This is not a solution for me. (please un mark as solution)

    I also have manual added the driver path to registery ([HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion]) and this does not work

    The drivers are being copied to c:\drivers but vista will not load them. If i manually go to device manager and select c:\drivers, they load fine. 

    We need to find out why MDT is not telling vista to search for drivers in the default c:\drivers

    this is not happening on windows 7/windows 8 task sequences.


    • Edited by PeteBC Monday, December 10, 2012 4:22 PM
    •  
     
  • Tuesday, December 11, 2012 8:00 PM
     
     
    Sign In to Vote
    0

    Microsoft has confirmed that this is a bug (they believe with windows PE 4.0) that they can recreate.

    They are now opening a ticket with the MDT team to see if they can find a solution

    I'll post when i get more info

     
  • Tuesday, January 15, 2013 1:53 PM
     
     
    Sign In to Vote
    0

    Jason, This is allready in the unattend file and drivers are not being loaded. This is not a solution for me. (please un mark as solution)

    I also have manual added the driver path to registery ([HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion]) and this does not work

    The drivers are being copied to c:\drivers but vista will not load them. If i manually go to device manager and select c:\drivers, they load fine. 

    We need to find out why MDT is not telling vista to search for drivers in the default c:\drivers

    this is not happening on windows 7/windows 8 task sequences.


    I got the Same Problem for Windows Server2008R2
    I think i added all necessary drivers vor VMware ESXI5.1 who are just 60 KB.
    Then I Update the MDT. Replace the LiteTouchPE Bootiamge and start my Server but i always get the same Error.

    <![LOG[No networking adapters found, The network drivers for your device are not present]LOG]!>

    Causing the following Problem:

    A Connection to the deployment share
    (\\srv\deploymentshare$) could not be made.
    Connection OK. Possible cause: invalid credentials.

    Any Ideas?

    ooGDoo