none
How to verify driver installation RRS feed

  • Question

  • Is there a .log file in the MININT folder that shows that drivers are being deployed from a certain path in MDT. For example, will it show in the logs drivers coming from Out-of-Box Drivers\Win7x64\Dell Inc.\Precision Tower T7810, which is one particular folder in my MDT setup.

    Wednesday, June 10, 2015 6:02 AM

All replies

  • I tested this by changing the Inject Drivers task to "WinPE 5.0 Driver CAB" which has a very small bunch of drivers, and sure enough I saw them deployed during the deployment. I'm not that confident my "Set Drivers Path" task is working as it should.

    Set Drivers Path

    DriverGroup001

    Win7x64\%make%\%model%

    Ignore Set Drivers Path being disabled, this was to test something

    Wednesday, June 10, 2015 6:37 AM
  • On the next step "Inject drivers" have you set that to:

    Nothing and Install ALL?

    The way to tell would be to look through the BDD.log to see if it picks up the correct location it will say something along the lines of:

    Property DriverGroup001 is now = Win7x64\make\model

    but with the correct naming conventions.

    Thanks

    NN

    Wednesday, June 10, 2015 1:24 PM
  • ZTIDrivers.log will tell you exactly which drivers were installed.

    ZTISetVariable.log will tell you what the DriverGroup001 value was set to.


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

    • Proposed as answer by Dan_Vega Thursday, June 11, 2015 12:56 PM
    Wednesday, June 10, 2015 3:19 PM
  • On the next step "Inject drivers" have you set that to:

    Nothing and Install ALL?

    The way to tell would be to look through the BDD.log to see if it picks up the correct location it will say something along the lines of:

    Property DriverGroup001 is now = Win7x64\make\model

    but with the correct naming conventions.

    Thanks

    NN

    Just changed it to Nothing and Instal all drivers from the selection profile. So I can't get my head around this theory?


    • Edited by edgar_davids Wednesday, June 10, 2015 11:55 PM edit
    Wednesday, June 10, 2015 11:02 PM
  • Changed it to Nothing and Instal all drivers from the selection profile and no drivers were installed. I grabbed the OSDLOGS directory. I did note that my workstation was called Precision Tower T7810 in my folder structure and WMIC / CSProduct command revealed it as Precision Tower 7810 - not sure if that's related.

    ZTIDrivers.log

    <![LOG[Microsoft Deployment Toolkit version: 6.2.5019.0]LOG]!><time="08:55:04.000+000" date="06-11-2015" component="ZTIDrivers" context="" type="1" thread="" file="ZTIDrivers">
    <![LOG[The task sequencer log is located at X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log.]LOG]!><time="08:55:04.000+000" date="06-11-2015" component="ZTIDrivers" context="" type="1" thread="" file="ZTIDrivers">
    <![LOG[Processing drivers for an X64 operating system.]LOG]!><time="08:55:04.000+000" date="06-11-2015" component="ZTIDrivers" context="" type="1" thread="" file="ZTIDrivers">
    <![LOG[OSDTargetDriveCache was determined earlier : C:]LOG]!><time="08:55:04.000+000" date="06-11-2015" component="ZTIDrivers" context="" type="1" thread="" file="ZTIDrivers">
    <![LOG[Property OSDTargetDriveCache is now = C:]LOG]!><time="08:55:04.000+000" date="06-11-2015" component="ZTIDrivers" context="" type="1" thread="" file="ZTIDrivers">
    <![LOG[Property OSDisk is now = C:]LOG]!><time="08:55:04.000+000" date="06-11-2015" component="ZTIDrivers" context="" type="1" thread="" file="ZTIDrivers">
    <![LOG[Property DriverCleanup is now = DONE]LOG]!><time="08:55:04.000+000" date="06-11-2015" component="ZTIDrivers" context="" type="1" thread="" file="ZTIDrivers">
    <![LOG[Compare Image processor Type with Original [X64] = [X64].]LOG]!><time="08:55:04.000+000" date="06-11-2015" component="ZTIDrivers" context="" type="1" thread="" file="ZTIDrivers">
    <![LOG[ Open Control File: Drivers]LOG]!><time="08:55:04.000+000" date="06-11-2015" component="ZTIDrivers" context="" type="1" thread="" file="ZTIDrivers">
    <![LOG[Filtered.Count: 0]LOG]!><time="08:55:04.000+000" date="06-11-2015" component="ZTIDrivers" context="" type="1" thread="" file="ZTIDrivers">
    <![LOG[Updating downlevel OS configuration.]LOG]!><time="08:55:04.000+000" date="06-11-2015" component="ZTIDrivers" context="" type="1" thread="" file="ZTIDrivers">
    <![LOG[Vista identified, skipping update of Device Path]LOG]!><time="08:55:04.000+000" date="06-11-2015" component="ZTIDrivers" context="" type="1" thread="" file="ZTIDrivers">
    <![LOG[ZTIDrivers processing completed successfully.]LOG]!><time="08:55:04.000+000" date="06-11-2015" component="ZTIDrivers" context="" type="1" thread="" file="ZTIDrivers">

    ZTISetVariable.log

    <![LOG[Microsoft Deployment Toolkit version: 6.2.5019.0]LOG]!><time="08:55:03.000+000" date="06-11-2015" component="ZTISetVariable" context="" type="1" thread="" file="ZTISetVariable">
    <![LOG[The task sequencer log is located at X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log.]LOG]!><time="08:55:03.000+000" date="06-11-2015" component="ZTISetVariable" context="" type="1" thread="" file="ZTISetVariable">
    <![LOG[Setting variable DriverGroup001 to value Win7x64\Dell Inc.\Precision Tower 7810]LOG]!><time="08:55:03.000+000" date="06-11-2015" component="ZTISetVariable" context="" type="1" thread="" file="ZTISetVariable">
    <![LOG[Property DriverGroup001 is now = Win7x64\Dell Inc.\Precision Tower 7810]LOG]!><time="08:55:04.000+000" date="06-11-2015" component="ZTISetVariable" context="" type="1" thread="" file="ZTISetVariable">
    <![LOG[ZTISetVariable processing completed successfully.]LOG]!><time="08:55:04.000+000" date="06-11-2015" component="ZTISetVariable" context="" type="1" thread="" file="ZTISetVariable">



    • Edited by edgar_davids Wednesday, June 10, 2015 11:54 PM mistake
    Wednesday, June 10, 2015 11:28 PM
  • What MDT says in the logs about "Win7x64\Dell Inc.\Precision Tower 7810" is how you want your folder structure to be.

    Also the reason why you want to set the variable and have the driver selection profile set to nothing is so the variable you set previously doesn't get overwritten: (DriverGroup001=Win7x64\Dell Inc.\Precision Tower 7810). If you chose some selection profile the inject drivers wouldn't care about DriverGroup001.


    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, June 10, 2015 11:53 PM
    Moderator
  • Changed it back to Win7 and Install only matching drivers from the selection profile and it appears drivers were installed. This was minus the RAID card, which I removed. I will now place it back into the system and see if it blue screens again with the renamed folder structure (Precision Tower 7810 as opposed to Precision Tower T7810).
    Wednesday, June 10, 2015 11:57 PM
  • I would do the Total Control method as per: http://deploymentresearch.com/Research/Post/325/MDT-2013-Lite-Touch-Driver-Management

    There are a lot less variables about what gets injected (Dan was alluding to this) since you know 100% that what is in the "Win7x64\Dell Inc.\Precision Tower 7810" is there.  How I add a new model is create the folder structure with nothing in it.  Do an install.  Then only install the drivers required to get the machine with all its necessary drivers.  Then import the drivers that were required. 

    A lot of chaos can happen with the PNP detection.  The largess of new hardware has some child device that won't get seen until a parent is installed.  In that case you are going to wonder why doesn't this driver get installed?  I have MDT set to figure out the proper drivers... However you have no way of knowing what the children are until the parents are installed.


    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.


    • Edited by Ty GlanderModerator Thursday, June 11, 2015 12:08 AM sorry didn't see Dan mentioned in another thread
    Thursday, June 11, 2015 12:05 AM
    Moderator
  • OK, watching the Copying driver component, there seems to be a fair few drivers copied with (3) or (5) behind them, which would mean my Inject Drivers task is not pulling the correct drivers from Precision Tower 7810 folder. My Precision Tower 7810 folder doesn't contain any drivers with a (3) or (5) behind them. I'm stuck on this. The PC bluescreened again, I'm quite sure the correct driver is not being copied down.
    Thursday, June 11, 2015 12:25 AM
  • Can you copy bdd.log to something like OneDrive, share it, and provide a link to it?

    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.

    Thursday, June 11, 2015 12:40 AM
    Moderator
  • OK SUCCESS! Reverted the Inject Drivers task back to Nothing and Install all drivers from the selection profile. The Copying driver component during the build this time was super quick, and I noticed all the drivers from Precision Tower 7810 folder being copied - nothing with (3) or (5) etc. Then, NO BLUE SCREEN! I was using the A02 driver pack, then the updated LSI drivers with the AO2 LSI drivers removed (the driver with a (1) next to it and an older driver version) - but it was more of a case of the original setup of my Inject Drivers task that was the main issue to my initial blue screen problems. One thing I'm not sure of though was if changing the folder from Precision Tower T7810 to Precision Tower 7810 helped? Thanks to all involved!
    Thursday, June 11, 2015 12:55 AM
  • I guess I missed a lot. Just remember when you use the driver group variable to inject the drivers of the machine you are deploying to, your folder structure must exactly match the names that are returned when a query is done.

    Note: The only exception is if you are using a modelalias script, in which case you are the one who creates new aliases. If you don't use that, ignore this.

    Copy and paste below into notepad and save it as a batch file.

    @echo off
    powershell -command "& {gwmi Win32_Bios | Select SMBIOSBIOSVersion, SerialNumber | ft; gwmi Win32_ComputerSystem | Select Model, Manufacturer | ft }"
    pause

    I wrote this up to run on new machines we get to determine what the names are. Then I know what folder names to create.


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


    • Edited by Dan_Vega Thursday, June 11, 2015 12:55 PM
    • Proposed as answer by Dan_Vega Thursday, June 11, 2015 12:56 PM
    Thursday, June 11, 2015 12:53 PM