Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
inject drivers issue Windows 7 x86 task sequence MDT2012 OS not installing drivers

Answered inject drivers issue Windows 7 x86 task sequence MDT2012 OS not installing drivers

  • Monday, March 18, 2013 3:35 PM
     
     
    Sign In to Vote
    0

    Hoping someone can help with my inject drivers issue.  I have a custom  x86 and x64 windows 7 image built.  The x64 image works fine and injects drivers and the OS instlalls them like they should.  My x86 image on the other hand copies the drivers to c:\Drivers  but the Operating system will not load the drivers.  My deployment errors out when it doesnt have a NIC driver and device manager shows no drivers installed for all my devices.  I have tried creating a new ground up win7 x86 image as well as new task sequences but still nothing seems to work.  This has worked in the past before upgrading to MDT2012 sp1.  Any suggestions would be greatly appreciated.


    Thanks,


    • Edited by NickC00k Monday, March 18, 2013 5:59 PM
    •  
     

All Replies

  • Monday, March 18, 2013 4:32 PM
     
     
    Sign In to Vote
    0

    Can you post an example bdd.log with the failure you are seeing?

    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. ” How to ask a question that is fixable.

     
  • Monday, March 18, 2013 5:49 PM
     
     
    Sign In to Vote
    0
    The only failure is the fact that the Task Sequence is unable to complete because of the missing network driver.  If I install the driver manually i can resume the task sequence and it completes. None of the drivers that are copied to C:\drivers are installing in the Operating System.
     
  • Monday, March 18, 2013 6:18 PM
     
     
    Sign In to Vote
    1

    Logs:

    https://skydrive.live.com/?cid=2f5af70aed8518d7#cid=2F5AF70AED8518D7&id=2F5AF70AED8518D7%21283

     
  • Monday, March 18, 2013 8:47 PM
     
     
    Sign In to Vote
    0

    Rebuild your boot image but, make sure you have the NIC drivers in the selection profile you use for your winPE.

    Personally I have selection profiles for WinPEx86 and WinPEx64.

    Then for my boot images I choose to inject all drivers:

    and my WinPEx86 folder looks like:

    Also I think the reason why it worked in the past but, not now is when you upgraded to 2012 u1 you probably had to rebuild the 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. ” How to ask a question that is fixable.


    • Edited by Ty Glander Monday, March 18, 2013 8:48 PM
    •  
     
  • Monday, March 18, 2013 8:58 PM
     
     
    Sign In to Vote
    0
    Unfortunately I have the nic drivers in my boot images already hence it deploys the image fine then errors when it gets into the OS.  The drivers that are being copied from my selection profile to C:\drivers are not installed by the OS. 
     
  • Monday, March 18, 2013 11:12 PM
     
     
    Sign In to Vote
    0
    The only failure is the fact that the Task Sequence is unable to complete because of the missing network driver.  If I install the driver manually i can resume the task sequence and it completes. None of the drivers that are copied to C:\drivers are installing in the Operating System.

    I will take a look at the logs tonight when I get home (no sky driver access currently) and see if I can figure out what is happening.

    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. ” How to ask a question that is fixable.

     
  • Tuesday, March 19, 2013 2:52 PM
     
     
    Sign In to Vote
    0
    Unfortunately I have the nic drivers in my boot images already hence it deploys the image fine then errors when it gets into the OS.  The drivers that are being copied from my selection profile to C:\drivers are not installed by the OS. 

    For some reason dism is not not being called to inject drivers.  I think the Inject drivers section is missing from your post install phase.  I expected to see something in the cbs.log like:

    DISM   DISM Driver Manager: PID=1536 Path = '\Drivers' ( HRESULT = 0x0 ) - DriversCallback

    Can you check and see if your Task Sequence Inject Driver section is in post install also?:

    This one will be with a command line of cscript.exe "%SCRIPTROOT%\ZTIdrivers.wsf"

    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. ” How to ask a question that is fixable.






    • Edited by Ty Glander Tuesday, March 19, 2013 2:53 PM
    • Edited by Ty Glander Tuesday, March 19, 2013 2:53 PM
    • Edited by Ty Glander Tuesday, March 19, 2013 3:04 PM
    • Edited by Ty Glander Tuesday, March 19, 2013 3:07 PM
    • Edited by Ty Glander Tuesday, March 19, 2013 3:08 PM
    •  
     
  • Tuesday, March 19, 2013 3:55 PM
     
     
    Sign In to Vote
    0

    I do have the inject drivers option in postinstall with the command line.

     
  • Tuesday, March 19, 2013 4:37 PM
     
     
    Sign In to Vote
    0
    I am at a loss then...  From you bdd.log we do see that drivers are being copied down which is the first part.  The next part is the post install inject drivers.  The cbs logs don't show any DISM activity about injecting drivers.  Which I would expect since you have the Inject Drivers in your post install phase.

    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. ” How to ask a question that is fixable.

     
  • Tuesday, March 19, 2013 9:09 PM
     
     
    Sign In to Vote
    0

    Can you check the unattend for your particular task sequence?  You should see this:

    Bleh my screenshot... it should be Microsoft-Windows-PnpCustomiationsNonWinPE

    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. ” How to ask a question that is fixable.

     
  • Wednesday, March 20, 2013 4:31 PM
     
     
    Sign In to Vote
    0
    Yes mine says exactly that,  Microsoft-Windows-PnpCustomizationsNonWinPE
    • Marked As Answer by NickC00k Wednesday, March 20, 2013 8:39 PM
    • Unmarked As Answer by NickC00k Wednesday, March 20, 2013 8:49 PM
    •  
     
  • Wednesday, March 20, 2013 8:49 PM
     
     Answered
    Sign In to Vote
    0
    I started over with a base win7x86 image and then captured that and it deployed fine to my machine and installed all the drivers.  I started installing the few apps that we dont have automated and took snapshots along the way.  It ended up being our rightfax client install that includes c++, Visual Studio, Donetframework4.0full and a rightfax print driver.  It was either one of those many installs or the windows updates that want to install after. I will have to bite the bullet and make several app installs for each of the pieces of this rightfax client. Weird thing about all this is we have it all working fine and recapturing on x64.  So if anyone else runs across drivers not being loaded by the OS even know the C:\Drivers folder is copied it could be an app if you dont use a bone stock Win7 OS in  your task sequence.
    • Marked As Answer by NickC00k Wednesday, March 20, 2013 8:49 PM
    •