none
Computer Model Not Detected For WMI Query Needed For Driver Selection Profile RRS feed

  • Question

  • We have a couple of workstation models that will not inject any drivers.  The likely cause is that it is not being correctly detected and therefore doesn't choose any selection profile.

    The deployment fails because there is no nic driver so it cannot reconnect to the deployment share after the OS installed and when I look in the device manager, there are no other drivers installed either there are question marks or generic drivers for everything (sound, display etc..).

    When I do wmic computersystem get model, it returns "HP Compaq Elite 8300 SFF"

    So I downloaded the driver management pack from the HP website for the model and imported all the extracted drivers into MDT and them created a driver selection profile that points to those drivers and then created a task that installs drivers from that selection profile based on these queries:

    If any conditions are true

    Select * FROM Win32_ComputerSystem Where Model like "%HP Compaq 8300 Elite SFF%"

    Task sequence variable %model% equals HP Compaq 8300 Elite SFF

    Despite this, no drivers are attempted to be installed.

    How can I fix this so the drivers are matched and installed.

    I have several other models in this deployment  task sequence and this is one of only 2 models that don't work using the same syntax.

    Thursday, May 16, 2013 9:45 PM

All replies

  • Well, it's not actually proof your criteria isn't working, it's just proof that the drivers aren't loading as expected.  Can you post your BDD.log (to SkyDrive, etc) from one of these HP Compaq 8300 Elite SFF machines?  The first thing to check is to see if the criteria is actually working or not.  Conversely, you could try removing the criteria and re-imaging an HP Compaq 8300 Elite SFF and see if it applies the drivers.  If it still doesn't apply the drivers, then it's not the criteria, it may be the drivers or something related.

    Are you using Selection Profiles to pick which drivers you want installed?  Are you forcing or allowing it to match PnP IDs?


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

    Thursday, May 16, 2013 10:52 PM
    Answerer

  • This is where the drivers it should be pulling from MDT are.

    Drivers in MDT Selection Profile

    I don't see any MDT logs in the C;|Windows\Temp folder of the failing computer.

    Friday, May 17, 2013 12:40 AM
  • One thing I see is that the error says the device is PCI\VEN_8086&DEV_1502&SUBSYS_3397103C&REV_04

    None of the available drivers have that extra few characters on the name.  There is a driver shown in the screenshot that matches except for the &REV_04 appended to the end. I wonder if that is what is messing it up?  I went to the HP support site to download these drivers and didn't see any different network driver available.

    That doesn't explain why no other drivers installed either unless the video and sound drivers do not install unless network driver installs first.

    Friday, May 17, 2013 2:50 AM
  • I don't see any MDT logs in the C;|Windows\Temp folder of the failing computer.

    Check out this article for where to find logs: http://blogs.technet.com/b/askcore/archive/2012/05/08/mdt-2010-amp-2012-my-deployment-failed-what-and-where-are-logs-i-should-review.aspx

    Not sure if the REV_04 is directly impacting it.  Again, until we can look at the BDD.log, all we know is that it isn't working as expected.  If you manually take the drivers you have for that model, can you browse to them and load them for that device correctly?  If so, then the PnP ID matching in MDT should be doing the same, assuming it's being run correctly and not having a different issue which is why we need the logs.


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

    Friday, May 17, 2013 5:26 AM
    Answerer
  • I don't see any MDT logs in the C;|Windows\Temp folder of the failing computer.

    Check out this article for where to find logs: http://blogs.technet.com/b/askcore/archive/2012/05/08/mdt-2010-amp-2012-my-deployment-failed-what-and-where-are-logs-i-should-review.aspx

    Not sure if the REV_04 is directly impacting it.  Again, until we can look at the BDD.log, all we know is that it isn't working as expected.  If you manually take the drivers you have for that model, can you browse to them and load them for that device correctly?  If so, then the PnP ID matching in MDT should be doing the same, assuming it's being run correctly and not having a different issue which is why we need the logs.


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

    None of those locations exist or have MDT logs files

    After the system drive has been formatted:

    C:\MININT\SMSOSD\OSDLOGS

    After Deployment:

    %WINDIR%\TEMP\DeploymentLogs

    There is no C:\MININT directory at all

    %WINDIR%\TEMP does not contain any .log files at all 

    There is no X: drive.

    Friday, May 17, 2013 5:18 PM
  • You could setup a folder for logs and in CustomSettings.ini turn on SLShare=\\server\share, and run the deployment on that machine, then remove it from CustomSettings.ini.  This value tells MDT to copy the logs here at the end of the deployment process.

    If that fails, you can use SLShareDynamicLogging=\\server\share in CustomSettings.ini, but this is for advanced real-time debugging and should NOT be used in a Production environment.  It basically writes to the network share every step during the deployment, so has networking implications.

    We'll get to your logs one way or another! : )


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

    Friday, May 17, 2013 5:31 PM
    Answerer
  • the BBD info is posted at http://wikisend.com/download/328642/BDD.txt
    Friday, May 17, 2013 7:01 PM
  • I tried running another deployment task sequence that does not do the WMI query for the specific model and just blindly installs "all drivers" and that one works.  The NIC driver is found and every other driver gets installed with no problems.

    Still can't figure out why the WMI query to filter drivers to a selection profile works for laptops and not this desktop.

    Saturday, May 18, 2013 6:29 PM