MDT inject driver for usb3.0 port on pc

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? 

Answer 1

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