locked
MDT inject driver for usb3.0 port on pc RRS feed

  • Question

  • I import usb 3.0 drivers to share and replaced the boot wim after I updated the share.But the usb 3.0 drivers still cannot be installed well on PC.Beyond that,everything works fine.How can I deal with it? 




    • Edited by longgegeno1 Wednesday, September 3, 2014 8:27 AM
    Wednesday, September 3, 2014 8:25 AM

Answers

  • AS a follow up, I checked the logs offline...

    It appears that MDT did find the drivers and attempted to copy down locally:

    Found Device PCI\VEN_8086&DEV_8C31&REV_04 with 3rd party drivers! Count = 0  = {380f248f-1b26-450f-9697-1fa8e749210b}
    Found a driver for PCI\VEN_8086&DEV_8C31&REV_04: {380f248f-1b26-450f-9697-1fa8e749210b} from \\MDT\DeploymentShare$\Out-of-box Drivers\USB\oem143_2.5.4.40_6AACC3E6D10DF8699AA52D142550C5F98F140B69\oem143.inf
    Validating connection to \\MDT\DeploymentShare$\Out-of-box Drivers\USB\oem143_2.5.4.40_6AACC3E6D10DF8699AA52D142550C5F98F140B69
    Mapping server share: \\MDT\DeploymentShare$
    Already connected to server MDT as that is where this script is running from.
    Copying drivers from "\\MDT\DeploymentShare$\Out-of-box Drivers\USB\oem143_2.5.4.40_6AACC3E6D10DF8699AA52D142550C5F98F140B69" to "V:\Drivers\USB\oem143_2.5.4.40_6AACC3E6D10DF8699AA52D142550C5F98F140B69"
    About to run command: cmd.exe /c xcopy /seihycd "\\MDT\DeploymentShare$\Out-of-box Drivers\USB\oem143_2.5.4.40_6AACC3E6D10DF8699AA52D142550C5F98F140B69" "V:\Drivers\USB\oem143_2.5.4.40_6AACC3E6D10DF8699AA52D142550C5F98F140B69" 1> NUL 2>NUL
    Command has been started (process ID 500)
    Return code from command = 0
    Found Device PCI\VEN_8086&DEV_8C31 with 3rd party drivers! Count = 0  = {853ada7d-36f6-40e5-8719-734d3606bac1}
    Found a driver for PCI\VEN_8086&DEV_8C31: {853ada7d-36f6-40e5-8719-734d3606bac1} from \\MDT\DeploymentShare$\Out-of-box Drivers\System\2008s4el_9.1.9.1005_2CA3E45C2F9AFCC12681EC010E1D73FEA7613AA9\LxPtUSB3.inf
    Validating connection to \\MDT\DeploymentShare$\Out-of-box Drivers\System\2008s4el_9.1.9.1005_2CA3E45C2F9AFCC12681EC010E1D73FEA7613AA9
    Mapping server share: \\MDT\DeploymentShare$
    Already connected to server MDT as that is where this script is running from.
    Copying drivers from "\\MDT\DeploymentShare$\Out-of-box Drivers\System\2008s4el_9.1.9.1005_2CA3E45C2F9AFCC12681EC010E1D73FEA7613AA9" to "V:\Drivers\System\2008s4el_9.1.9.1005_2CA3E45C2F9AFCC12681EC010E1D73FEA7613AA9"
    About to run command: cmd.exe /c xcopy /seihycd "\\MDT\DeploymentShare$\Out-of-box Drivers\System\2008s4el_9.1.9.1005_2CA3E45C2F9AFCC12681EC010E1D73FEA7613AA9" "V:\Drivers\System\2008s4el_9.1.9.1005_2CA3E45C2F9AFCC12681EC010E1D73FEA7613AA9" 1> NUL 2>NUL
    Command has been started (process ID 832)
    

    So the question remains, if we copied down the drivers, why didn’t MDT pick up these drivers?

    IT is possible that the OS does not like these driver packages, so it did not install.  As a test, find the device in the device manager, and “update Driver Software”


    Then force MDT to use the paths:

    \\MDT\DeploymentShare$\Out-of-box Drivers\USB\oem143_2.5.4.40_6AACC3E6D10DF8699AA52D142550C5F98F140B69

    \\MDT\DeploymentShare$\Out-of-box Drivers\System\2008s4el_9.1.9.1005_2CA3E45C2F9AFCC12681EC010E1D73FEA7613AA9

    The system should use these drivers, if not, then you do not have the correct drivers, or there is some other problem, check the SetupAPI.*.log files.


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Thursday, September 4, 2014 4:16 AM
  • Do you need the USB 3.0 drivers from within WinPE? Try putting your USB Flash drive in a USB 2.0 port to confirm that it's really a driver issue (some machines have *both* usb 3.0 and usb 2.0 ports). I have USB 2.0 drives that are plenty fast. Additionally, using WInPE 5.0 (from the Windows 8.1 ADK), might have better driver support.

    Or is your problem that the full OS is missing the correct USB 3.0 drivers? If so, can you include your pnpenum.xml, bdd.log, drivers.xml and drivergroups.xml file in a public site like OneDrive for viewing? Speficially, which device is it? (what is the PnPID?)


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    • Marked as answer by Keith GarnerMVP Wednesday, September 3, 2014 10:40 PM
    Wednesday, September 3, 2014 10:40 PM

All replies

  • Do you need the USB 3.0 drivers from within WinPE? Try putting your USB Flash drive in a USB 2.0 port to confirm that it's really a driver issue (some machines have *both* usb 3.0 and usb 2.0 ports). I have USB 2.0 drives that are plenty fast. Additionally, using WInPE 5.0 (from the Windows 8.1 ADK), might have better driver support.

    Or is your problem that the full OS is missing the correct USB 3.0 drivers? If so, can you include your pnpenum.xml, bdd.log, drivers.xml and drivergroups.xml file in a public site like OneDrive for viewing? Speficially, which device is it? (what is the PnPID?)


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    • Marked as answer by Keith GarnerMVP Wednesday, September 3, 2014 10:40 PM
    Wednesday, September 3, 2014 10:40 PM
  • Hi,keith,I send you an email with the files you need except the pnpenum.xml cause I can't find it.

    My email address: longgegeno1@vip.qq.com

    And my proble is the later one you mentioned above.





    • Edited by longgegeno1 Thursday, September 4, 2014 4:07 AM
    Thursday, September 4, 2014 3:53 AM
  • PNPID:

    1.IUSB3\ROOT_HUB30$VID_8086&PID_8C31&REV_0004&SID_309817AA

    2.PCI\VEN_8086&DEV_8C31&SUBSYS_309817AA&REV_04



    • Edited by longgegeno1 Thursday, September 4, 2014 4:06 AM
    Thursday, September 4, 2014 4:06 AM
  • AS a follow up, I checked the logs offline...

    It appears that MDT did find the drivers and attempted to copy down locally:

    Found Device PCI\VEN_8086&DEV_8C31&REV_04 with 3rd party drivers! Count = 0  = {380f248f-1b26-450f-9697-1fa8e749210b}
    Found a driver for PCI\VEN_8086&DEV_8C31&REV_04: {380f248f-1b26-450f-9697-1fa8e749210b} from \\MDT\DeploymentShare$\Out-of-box Drivers\USB\oem143_2.5.4.40_6AACC3E6D10DF8699AA52D142550C5F98F140B69\oem143.inf
    Validating connection to \\MDT\DeploymentShare$\Out-of-box Drivers\USB\oem143_2.5.4.40_6AACC3E6D10DF8699AA52D142550C5F98F140B69
    Mapping server share: \\MDT\DeploymentShare$
    Already connected to server MDT as that is where this script is running from.
    Copying drivers from "\\MDT\DeploymentShare$\Out-of-box Drivers\USB\oem143_2.5.4.40_6AACC3E6D10DF8699AA52D142550C5F98F140B69" to "V:\Drivers\USB\oem143_2.5.4.40_6AACC3E6D10DF8699AA52D142550C5F98F140B69"
    About to run command: cmd.exe /c xcopy /seihycd "\\MDT\DeploymentShare$\Out-of-box Drivers\USB\oem143_2.5.4.40_6AACC3E6D10DF8699AA52D142550C5F98F140B69" "V:\Drivers\USB\oem143_2.5.4.40_6AACC3E6D10DF8699AA52D142550C5F98F140B69" 1> NUL 2>NUL
    Command has been started (process ID 500)
    Return code from command = 0
    Found Device PCI\VEN_8086&DEV_8C31 with 3rd party drivers! Count = 0  = {853ada7d-36f6-40e5-8719-734d3606bac1}
    Found a driver for PCI\VEN_8086&DEV_8C31: {853ada7d-36f6-40e5-8719-734d3606bac1} from \\MDT\DeploymentShare$\Out-of-box Drivers\System\2008s4el_9.1.9.1005_2CA3E45C2F9AFCC12681EC010E1D73FEA7613AA9\LxPtUSB3.inf
    Validating connection to \\MDT\DeploymentShare$\Out-of-box Drivers\System\2008s4el_9.1.9.1005_2CA3E45C2F9AFCC12681EC010E1D73FEA7613AA9
    Mapping server share: \\MDT\DeploymentShare$
    Already connected to server MDT as that is where this script is running from.
    Copying drivers from "\\MDT\DeploymentShare$\Out-of-box Drivers\System\2008s4el_9.1.9.1005_2CA3E45C2F9AFCC12681EC010E1D73FEA7613AA9" to "V:\Drivers\System\2008s4el_9.1.9.1005_2CA3E45C2F9AFCC12681EC010E1D73FEA7613AA9"
    About to run command: cmd.exe /c xcopy /seihycd "\\MDT\DeploymentShare$\Out-of-box Drivers\System\2008s4el_9.1.9.1005_2CA3E45C2F9AFCC12681EC010E1D73FEA7613AA9" "V:\Drivers\System\2008s4el_9.1.9.1005_2CA3E45C2F9AFCC12681EC010E1D73FEA7613AA9" 1> NUL 2>NUL
    Command has been started (process ID 832)
    

    So the question remains, if we copied down the drivers, why didn’t MDT pick up these drivers?

    IT is possible that the OS does not like these driver packages, so it did not install.  As a test, find the device in the device manager, and “update Driver Software”


    Then force MDT to use the paths:

    \\MDT\DeploymentShare$\Out-of-box Drivers\USB\oem143_2.5.4.40_6AACC3E6D10DF8699AA52D142550C5F98F140B69

    \\MDT\DeploymentShare$\Out-of-box Drivers\System\2008s4el_9.1.9.1005_2CA3E45C2F9AFCC12681EC010E1D73FEA7613AA9

    The system should use these drivers, if not, then you do not have the correct drivers, or there is some other problem, check the SetupAPI.*.log files.


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Thursday, September 4, 2014 4:16 AM
  • Thank you very much. You provided me a useful way to find out what's going on with my deployment.  


    • Edited by longgegeno1 Thursday, September 4, 2014 5:27 AM
    Thursday, September 4, 2014 5:26 AM