Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
OOBD Drivers

Answered OOBD Drivers

  • Monday, March 04, 2013 4:51 PM
     
     
    Sign In to Vote
    0

    Hello,

       I have created and organized my 'Out-of-Box Drivers' groups for the specific models we deploy to. I have created specific 'selection profiles'. I get when you update the deployment share that it injects these drivers into your WinPE to get everything to work.

    My question is I thought once the OS was installed (i.e. Win7ProSP1) that once I went into my 'Device Manager' the driver levels would be of the ones I d/loaded from the manufacturer site. Looking at my video and networking sections it appears they are just running what came with Win7.

    Example:

    Networking = 03/26/2010

    Video = 04/25/2009

    ZT

     

All Replies

  • Monday, March 04, 2013 5:38 PM
     
     
    Sign In to Vote
    1

    Firstly, they are only included in your WinPE if you've selected them to be from your Deployment Share properties (Under Windows PE tab, Drivers and Patches subtab, Selection profile and the radio for 'All' or 'Selective' with boxes) and then re-generated your boot image.

    Your drivers will only apply if you create a Step in your Task Sequence to apply them during imaging.  You need to add an "Inject Drivers" step and then select the specific driver profile you want applied.  There are some great blogs on how to do this in an organized manner (like this: http://adminnexus.blogspot.com/2012/08/yet-another-approach-to-driver.html#!/2012/08/yet-another-approach-to-driver.html).  Doing it thusly allows you to have a single Task Sequence still, but only call the "Inject Drivers" step for a specific profile if the hardware type matches (using WMI).

    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek

     
  • Monday, March 04, 2013 5:40 PM
     
     Answered
    Sign In to Vote
    1
    Take a look here: LTI/ZTI Deployments: Injecting drivers during deployment

    Blog: http://scriptimus.wordpress.com

    • Marked As Answer by ZoeTaite Tuesday, March 26, 2013 2:06 PM
    •  
     
  • Thursday, March 21, 2013 4:06 PM
     
     
    Sign In to Vote
    0

    Quick follow up. Once the system has been imaged is there a log or a way to tell if the OOBD drivers have been injected into the image?

    -Brandon

     
  • Thursday, March 21, 2013 6:26 PM
     
     
    Sign In to Vote
    0

    ZTIDrivers.log

    After an LTI the logs are copied to %WINDIR%\Temp\Deployment Logs

    Blog: http://scriptimus.wordpress.com

     
  • Thursday, March 21, 2013 7:23 PM
     
     
    Sign In to Vote
    0

    Andrew,

       I found this log and I see that it copies the drivers (.inf) locally to C:\Drivers. When completed does a script just delete that folder from the local system? The reason I ask is what happens if a driver is needed (i.e. re-install as an example).

    ZT

     
  • Thursday, March 21, 2013 7:57 PM
     
     
    Sign In to Vote
    0

    I believe it does. I've never seen it moved anywhere else.

    Blog: http://scriptimus.wordpress.com

     
  • Saturday, March 23, 2013 12:23 AM
     
     
    Sign In to Vote
    0

    Andrew,

       I created a 'OTHER' container in my OOBD container. Created a new 'Inject Driver' TS and pointed to this selection profile. Seemed to work, but when I try and install the printer I can't find the driver on the local system that was just imaged.

    ZT

     
  • Saturday, March 23, 2013 1:17 PM
     
     
    Sign In to Vote
    0

    That's probably because a printer driver is a different beastie. You should handle your printer drivers seperately eg. Group policy printing.

    If the printer is not connected during deployment then it wont be installed. Same for all devices.

    Remember the default behavior is "Install only matching drivers from the selection profile".

    Blog: http://scriptimus.wordpress.com