Importing drivers to MDT

I have a driver structure in MDT that is based on OS\vendor\model style and I'm using drivergroups to apply drivers. When Importing drivers to MDT should I select the import duplicate driver or not? Many models share same drivers so if I dont choose the
duplicate option some models might miss some drivers if I'm understanding correctly.

Assuming you have your OOB driver folder set up correctly, you don't need to re-import the driver. Just have it "copy" the driver and it will work.
Also, once I find a working driver to get the system to PXE, I *never* update it again. I perform all driver updates (NIC, Storage, Chipset, etc) afterwards via the TS. I only put my Storage and NIC drivers into the boot image and OOB folder.

Similar Messages

How To: Debug missing Drivers in MDT

The definitive post on missing drivers in MDT (most comprehensive list I've done so far)…
Please to NOT post questions from this thread, instead create a new thread.
How to debug Network Driver Problems
One of the earliest hurdles an MDT administrator will come across is the management of device drivers, specifically networking drivers. With most other drivers, like Audio, printer, and video drivers, a quick call to Windows Update or install over the network
will resolve the Installation. However unless the Network (and storage) Drivers are installed into Windows from the start, it will be much more difficult to install the rest of the system.
This post should help you get started if you find a machine that did not install a device driver properly, and you want to know how to find and import the correct drivers.
Installing network drivers in the
full OS
Step 1 - Try network connection again
It's possible that you might get a DHCP error from MDT, but when you try again later to connect the Deployment Share it works! This may be caused by a slow or malfunctioning DHCP server in your network. Re-check your DHCP servers, ensure that PortFast is enabled
on your routers. If all else fails get your network administrators to document the DHCP delay. A long delay in modern networks is unnecessary.
Step 2 - Verify connectivity
You may not have a driver problem but a network problem. Check the physical connection on the computer (Network installs on MDT *REQUIRE* a wired network connection, no Wi-Fi). Open a web browser. Check the IP Address (ipconfig.exe /all). Ping the Deployment
Server, manually connect to the Deployment Share. IF you can't connect to the Deployment Share, neither can MDT.
Step 3 - Find the Correct Driver Package
Before you load the driver into MDT, first verify that you have the correct driver. There are scenarios where you may *think* you have the correct driver, but the driver will never run because the package is designed for a different OS/SKU/Platform/whatever.
Install the driver package by:
  ○ Open the Device Manager (devmgmt.msc).
  ○ Find the network device in the list (ensure this is the wired device, not the wireless device)
  ○ Right click on "Properties" and click on the "Details" tab.
  ○ From the "Details" tab, select the property "Hardware Ids" select all the values, and copy to the clipboard, it would be a good idea to save for later. Should look something like:
      PCI\VEN_8086&DEV_1502&SUBSYS_21F317AA&REV_04
      PCI\VEN_8086&DEV_1502&SUBSYS_21F317AA
      PCI\VEN_8086&DEV_1502&CC_020000
      PCI\VEN_8086&DEV_1502&CC_0200
  ○ From the "Driver" tab, click on "Update Driver…", click on "Browse my computer for driver software" locate the driver package on the local machine or USB Drive, and install the package.
  ○ You should get a confirmation that the driver package was installed.
  ○ IF you do not get confirmation, MDT driver installation may not work.
Windows will install the driver starting with the *.inf install package, and will typically include a *.sys (binary) and a *.cat (digital Signature). If the driver package has been re-packaged into a *.cab, *.zip, or other compressed *.exe file, the
package must be extracted first. This is a hard requirement for any driver used by MDT and/or SCCM. All driver packages that are signed by Microsoft (WHQL) will be installed from the *.inf file, and you should only use devices that have the Microsoft WHQL
Logo as a sign of quality.
If you need a help on where to find driver packages for your devices, the 3 largest Computer OEM manufacturers supply drivers grouped by Make and Model that are easily imported into MDT and SCCM. See:
http://deploymentbunny.com/2014/07/08/back-to-basicwhere-to-find-drivers-for-servers-and-clients/
Step 4 - Load driver into MDT
If you have more than 20 driver packages, or if you anticipate you will have more than 20 drivers, you should start grouping your drivers in sub-folders for organization. One popular method is to group by Computer Make and Model. Ensure that you are using the
correct Driver Selection Profile in your task sequence. If you are unsure, disable any selection profile(s) to ensure the driver is installed correctly.
Step 5 - Run the full MDT installation
During installation MDT will perform the following:
  ○ Run the PNPEnum.exe utility and capture output to PnPEnum.xml. The VEN_Xxxx and DEV_Yyyy from the "HardwareIDs" property above must be present in this list. Otherwise we won't have a match.
  ○ Search through the %DeployRoot%\control\drivers.xml file looking for a match for the HardwareID. MDT may filter the search based on the folder search type.
  ○ MDT will copy each matching driver to the local c:\drivers directory using the xcopy.exe command. You can search (grep) for the string "xcopy" in the ZTIDrivers.log file, that will get you list of all driver packages matched by MDT.
  ○ MDT will allow the machine to boot into the NEW OS, and Driver Installation will begin in the OS. IF there are multiple drivers found and copied locally, the Windows (not MDT) will determine the best one. The c:\windows\inf\SetupAPI.*.log files
will detail which drivers copied locally were installed (or *not* installed).
Installing Network Drivers in
WinPE
Step 6 - Try the network connection again
(See above
Step 7 - Verify Connectivity from within WinPE
Verifying network connectivity will be a bit more difficult in WinPE, since we have a limited User Interface, so all investigation must be done in the debugging mode (Press F8) cmd.exe
  ○ Try connecting to the Deployment Share:
  c:\> net use * \\MDT\DeploymentShare$ /u:UserDomain\UserName *
  ○ Try pinging the Deployment Server:
  c:\> Ping.exe MDT.Corp.contoso.com
  ○ Verify that you have an IP address ( ipconfig /all ) If you have an AutoConfiguration address - Driver OK - WinPE can't reach the DHCP server. If you have "Media Disconnected" - Driver OK - Physical adapter not plugged to network. If
no devices are listed - Driver bad - Driver not installed.
  ○ Check the x:\windows\system32\WpeInit.log - This log will show the network driver (if found) being installed.
Step 8 - Verify driver packages are getting included into WinPE
Firstly, verify the correct driver package from within the full OS above. By default MDT will import *all* Storage and Networking drivers into your WinPE image. However it is possible to change the subset of files copied via "Selection Profile" or
other method. Cross check your WinPE Driver Settings.
  ○ From within the MDT console, right click on the root of your Deployment Share and select properties.
  ○ Click on the "Windows PE" tab, and the "Drivers and Patches" sub tab for both x86 and x64.
  ○ Your Network Drivers package must be in the "Selection Profile" if enabled.
Finally verify that the correct Network Driver package is being copied to WinPE. If necessary this may include setting up a debugger to watch the MDT Provider build the WinPE Image from scratch. My preference is to use the SysInternals
http://live.sysinternals.com/Dbgview.exe tool.
  ○ Open up the MDT console.
  ○ Download and run the DbgView.exe tool.
  ○ Update the deployment share in question.
  ○ The DbgView tool should show what drivers were copied to each WinPE Image.
Other
Whenever you add a driver into the MDT console, you must update the deployment share for that drivers to be added to your WinPE Image. If you are unsure, select "Completely regenerate the boot images." to ensure the drivers is imported. Additionally,
you must copy the updated LitetouchPE_x??.wim and *.iso files to the other consumers of the WinPE image like WDS/PXE and or any USB offline media.
Note that some Broadcom NetXtreme class of drivers have a multi-function driver architecture that may have difficulty loading in WinPE. Ensure that you load the "RIS" class of drivers from Broadcom in your MDT environment.
Note that by default MDT does *NOT* support the installation of Windows over Wireless network devices (Wi-Fi). The MDT installation sources must either be available through wired networking, or offline (USB Flash) media.
This post does not discuss origination of drivers within MDT ( Chaos vs. Total Control ), that is a different topic.
http://www.deploymentresearch.com/Research/tabid/62/EntryId/112/MDT-2013-Lite-Touch-Driver-Management.aspx
Further Help
If you are still having problems with drivers in via MDT, ask the experts in the MDT Technet Forum:
Include a short description of the problem. Including the Make/Mode if necessary.
Include the HardwareIDs from the Device Manager (Devmgmt.msc) into the post (from above).
Copy your known good driver package (step 3 above) to OneDrive.
Copy the following log files to a public site like OneDrive and include the link:
  ○ PnpEnum.xml (from Client)
  ○ Bdd.log (From Client) - or at least the ZTIDrivers.log file.
  ○ c:\windows\inf\SetupAPI.*.log (from client)
  ○ %DeployRoot%\control\Driver*.xml
  ○ %DeployRoot%\control\SelectionProfile*.xml
  ○ %DeployRoot%\control\settings.xml (if problems in WinPE)
  ○ x:\windows\System32\WpeInit.log (if problems in WinPE)
  ○ If the MDT server is not including your driver package in WinPE include the DBGView log.
This post is by Keith Garner - Keith was a developer on the MDT team where he developed the ZTIDrivers.wsf script, he also worked for the Windows Hardware Quality Labs as a technical PM on Driver Quality, and developed samples for the
Microsoft Device Driver Kit (DDK) specifically around the area of Device Driver installation in the OS (Windows NT 5.0, 2000 and Windows XP). (So yes, I know drivers :^).
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

OK. I have redone the drivers for WinPE which has reduced the image size by about 200MB. Unfortunately the problem persists.
Is there anyway to turn on some sort of boot logging so I can see what driver it is failing on?
I am also still seeing the weird behavior of it working over PXE but blue screens when booting from USB. Can anyone explain that?
JJ

Important Drivers downloads for HP 15 R 045TX

Hi All,
I just got a new laptop HP 15 R 045TX without OS.
I installed the Windows 7 on it.
I need the drivers for it,
can anyone tell me the important drivers to install and the link to that.
Windows 7 ultimate 64 bit OS

Hi,
Intel Chipset Installation Utility
Intel High-Definition (HD) Graphics
http://ftp.hp.com/pub/softpaq/sp65501-66000/sp65598.exe
NVIDIA High-Definition (HD)
http://ftp.hp.com/pub/softpaq/sp65001-65500/sp65477.exe
Intel Management Engine Components Driver
Intel USB 3.0 Driver for Intel 8 and U/Y
Synaptics TouchPad Driver
IDT High Definition (HD) Audio Driver
HP 3D DriveGuard 6
Ethernet
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=14&PFid=7&Level=5&Conn=4&DownTy...
Card Reader
http://www.realtek.com.tw/Downloads/downloadsView.aspx?Langid=1&PNid=15&PFid=25&Level=4&Conn=3&DownT...
Bluetooth Raink 4.0
http://ftp.hp.com/pub/softpaq/sp58501-59000/sp58515.exe
WiFi 802.11 b/g/n Ralink
http://ftp.hp.com/pub/softpaq/sp60001-60500/sp60464.exe
Reagards

Trying to import drivers, anyone ever run across FOLDERS that are named with a .INF?

I am using the excellent driver import script from http://blog.coretech.dk/kea/automate-importing-and-creating-drivers-packages-in-sccm-2012-r2/ to try and import drivers from Dell and HP.
We got these drivers from the Dell driver CAB website, same with HP.
We've extracted these drivers and are now attempting to import them. For the most part this works well, but there are some drivers that have a FOLDER in their path that has .INF in the FOLDER name. The script (I think) is seeing that folder name and
treating it as a driver .INF file, and failing to import it. An example is below.
These folders do have drivers in them, but the script is stopping before going any deeper, since it thinks these folders are actually driver files. Has anyone else run across this? I imagine you have if you're using the Dell and HP CAB files, which I suspect
many people are. Is there any reason these folders are named like this? Can I remove the .INF from the folder names and re-run the script? Will this cause any problems down the road?

It is kinda silly of the vendors to extract to folders in this way. You would never manually create a folder structure like that.
However, you are lucky to have the CAB file in the first place. More and more I am finding that there are no CAB files to download for certain models - I have to end up making my own driver package by importing individual drivers. It's a real pain.
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Satellite A30: What important drivers should I install

Hi, My Satellite A30 PSA30E had a major crash a while ago, now I have to reinstall everything but I lost my boot disc, I got an XP disc and I kno I have to install the drivers afterwards. I was just wondering what ones are the most important and if I need to install them in any specific order.
Thanks in advance

Hi
If you want to use all notebook features you should install all available XP drivers from the Toshiba driver page.
You ask for the most important drivers? Well, you should install
- Chip Set Utility
- Display Driver
- Sound Driver
- LAN Driver
- Wireless Lan Driver
- Cardbus Driver
- Touch Pad Driver
- Modem Driver
Other utilities like Toshiba Console or E-Key are needed to use the notebooks features but you the unit will run also without these programs

Import Drivers Fail- SCCM 2012 R2

Hello,
I am having issues with importing drivers and adding them to a driver package. The error message that I am receiving is "The SMS Provider reported an error." Our environment has a single SCCM 2012 R2 for the site. I looked through the SmsAdminUI
log file and found this:
[8, PID:5444][09/02/2014 16:32:48] :System.Management.ManagementException\r\nGeneric failure \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.ExecuteMethod(String methodClass, String methodName, Dictionary`2 methodParameters, Boolean traceParameters)\r\nManagementException details:
instance of SMS_ExtendedStatus
Description = "This driver (id=SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_8377D013536B9BAE158F0E5DE037A5DCCD06FA57_71FC22A08C28649AB32043B429AA6AB726BE536ABB4CAFA083E82699CBD027BC) has already been imported into the driver catalog.";
ErrorCode = 183;
File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspdriverci.cpp";
Line = 712;
ObjectInfo = "SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_8377D013536B9BAE158F0E5DE037A5DCCD06FA57_71FC22A08C28649AB32043B429AA6AB726BE536ABB4CAFA083E82699CBD027BC";
Operation = "ExecMethod";
ParameterInfo = "SMS_Driver";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
\r\n
[8, PID:5444][09/02/2014 16:32:55] :System.Management.ManagementException\r\nGeneric failure \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.ExecuteMethod(String methodClass, String methodName, Dictionary`2 methodParameters, Boolean traceParameters)\r\nManagementException details:
instance of SMS_ExtendedStatus
Description = "This driver (id=SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_8377D013536B9BAE158F0E5DE037A5DCCD06FA57_B9DDE7DF4661034EC956AC906BFFD363E845403FB0986F0FE59D21EA87042303) has already been imported into the driver catalog.";
ErrorCode = 183;
File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspdriverci.cpp";
Line = 712;
ObjectInfo = "SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_8377D013536B9BAE158F0E5DE037A5DCCD06FA57_B9DDE7DF4661034EC956AC906BFFD363E845403FB0986F0FE59D21EA87042303";
Operation = "ExecMethod";
ParameterInfo = "SMS_Driver";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
\r\n
[8, PID:5444][09/02/2014 16:32:59] :System.Management.ManagementException\r\nGeneric failure \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.ExecuteMethod(String methodClass, String methodName, Dictionary`2 methodParameters, Boolean traceParameters)\r\nManagementException details:
instance of SMS_ExtendedStatus
Description = "This driver (id=SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_ADCC44F92EB0E9B4B03925B054A05AA544097BCF_8F9AF41BF5B833AAE3DD249A3C9D567CD9FA9311B521BC20A4CEB3E36B48E427) has already been imported into the driver catalog.";
ErrorCode = 183;
File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspdriverci.cpp";
Line = 712;
ObjectInfo = "SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_ADCC44F92EB0E9B4B03925B054A05AA544097BCF_8F9AF41BF5B833AAE3DD249A3C9D567CD9FA9311B521BC20A4CEB3E36B48E427";
Operation = "ExecMethod";
ParameterInfo = "SMS_Driver";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
\r\n
[8, PID:5444][09/02/2014 16:33:03] :System.Management.ManagementException\r\nGeneric failure \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.ExecuteMethod(String methodClass, String methodName, Dictionary`2 methodParameters, Boolean traceParameters)\r\nManagementException details:
instance of SMS_ExtendedStatus
Description = "This driver (id=SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_C4E6DA78F9AF1BEE85077F65AEE0C6B7A7512E16_8F9AF41BF5B833AAE3DD249A3C9D567CD9FA9311B521BC20A4CEB3E36B48E427) has already been imported into the driver catalog.";
ErrorCode = 183;
File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspdriverci.cpp";
Line = 712;
ObjectInfo = "SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_C4E6DA78F9AF1BEE85077F65AEE0C6B7A7512E16_8F9AF41BF5B833AAE3DD249A3C9D567CD9FA9311B521BC20A4CEB3E36B48E427";
Operation = "ExecMethod";
ParameterInfo = "SMS_Driver";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
\r\n
[8, PID:5444][09/02/2014 16:33:09] :System.Management.ManagementException\r\nGeneric failure \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.ExecuteMethod(String methodClass, String methodName, Dictionary`2 methodParameters, Boolean traceParameters)\r\nManagementException details:
instance of SMS_ExtendedStatus
Description = "This driver (id=SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_ADCC44F92EB0E9B4B03925B054A05AA544097BCF_B35AE527E5F0B2DF31D07AE67C0217191797CD26C68355231E0EE7E2B71D6F80) has already been imported into the driver catalog.";
ErrorCode = 183;
File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspdriverci.cpp";
Line = 712;
ObjectInfo = "SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_ADCC44F92EB0E9B4B03925B054A05AA544097BCF_B35AE527E5F0B2DF31D07AE67C0217191797CD26C68355231E0EE7E2B71D6F80";
Operation = "ExecMethod";
ParameterInfo = "SMS_Driver";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
\r\n
[8, PID:5444][09/02/2014 16:33:13] :System.Management.ManagementException\r\nGeneric failure \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.ExecuteMethod(String methodClass, String methodName, Dictionary`2 methodParameters, Boolean traceParameters)\r\nManagementException details:
instance of SMS_ExtendedStatus
Description = "This driver (id=SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_C4E6DA78F9AF1BEE85077F65AEE0C6B7A7512E16_B35AE527E5F0B2DF31D07AE67C0217191797CD26C68355231E0EE7E2B71D6F80) has already been imported into the driver catalog.";
ErrorCode = 183;
File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspdriverci.cpp";
Line = 712;
ObjectInfo = "SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_C4E6DA78F9AF1BEE85077F65AEE0C6B7A7512E16_B35AE527E5F0B2DF31D07AE67C0217191797CD26C68355231E0EE7E2B71D6F80";
Operation = "ExecMethod";
ParameterInfo = "SMS_Driver";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
\r\n
[8, PID:5444][09/02/2014 16:33:17] :System.Management.ManagementException\r\nGeneric failure \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.ExecuteMethod(String methodName, Dictionary`2 methodParameters, Boolean traceParameters)\r\nManagementException details:
instance of SMS_ExtendedStatus
Description = "CIContentSourcePath - '\\\\aps-sccm\\sources$\\Drivers\\Driver Sources\\Dell Precision T1700\\USB\\Drivers\\HCSwitch\\x86' could not be found\n";
ErrorCode = 3;
File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\ssppackage.cpp";
Line = 3827;
Operation = "ExecMethod";
ParameterInfo = "SMS_DriverPackage.PackageID=\"APS00049\"";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
\r\n
[8, PID:5444][09/02/2014 16:33:17] :Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException\r\nThe SMS Provider reported an error.\r\n at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.ExecuteMethod(String methodName, Dictionary`2 methodParameters, Boolean traceParameters)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.ExecuteMethod(String methodName, Dictionary`2 methodParameters)
at Microsoft.ConfigurationManagement.AdminConsole.Driver.PackagesToDriversControl.UpdatePackage(PackageInfo packageInfo)\r\nConfigMgr Error Object:
instance of SMS_ExtendedStatus
Description = "CIContentSourcePath - '\\\\aps-sccm\\sources$\\Drivers\\Driver Sources\\Dell Precision T1700\\USB\\Drivers\\HCSwitch\\x86' could not be found\n";
ErrorCode = 3;
File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\ssppackage.cpp";
Line = 3827;
Operation = "ExecMethod";
ParameterInfo = "SMS_DriverPackage.PackageID=\"APS00049\"";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
\r\nSystem.Management.ManagementException\r\nGeneric failure \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.ExecuteMethod(String methodName, Dictionary`2 methodParameters, Boolean traceParameters)\r\nManagementException details:
instance of SMS_ExtendedStatus
Description = "CIContentSourcePath - '\\\\aps-sccm\\sources$\\Drivers\\Driver Sources\\Dell Precision T1700\\USB\\Drivers\\HCSwitch\\x86' could not be found\n";
ErrorCode = 3;
File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\ssppackage.cpp";
Line = 3827;
Operation = "ExecMethod";
ParameterInfo = "SMS_DriverPackage.PackageID=\"APS00049\"";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
\r\n

Hello,
I am having issues with importing drivers and adding them to a driver package. The error message that I am receiving is "The SMS Provider reported an error." Our environment has a single SCCM 2012 R2 for the site. I looked through the SmsAdminUI log
file and found this:
[8, PID:5444][09/02/2014 16:32:48] :System.Management.ManagementException\r\nGeneric failure \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.ExecuteMethod(String methodClass, String methodName, Dictionary`2 methodParameters, Boolean traceParameters)\r\nManagementException details:
instance of SMS_ExtendedStatus
Description = "This driver (id=SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_8377D013536B9BAE158F0E5DE037A5DCCD06FA57_71FC22A08C28649AB32043B429AA6AB726BE536ABB4CAFA083E82699CBD027BC)
has already been imported into the driver catalog.";
ErrorCode = 183;
File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspdriverci.cpp";
Line = 712;
ObjectInfo = "SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_8377D013536B9BAE158F0E5DE037A5DCCD06FA57_71FC22A08C28649AB32043B429AA6AB726BE536ABB4CAFA083E82699CBD027BC";
Operation = "ExecMethod";
ParameterInfo = "SMS_Driver";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
the driver already exists in the catalog..
http://technet.microsoft.com/en-us/library/2240a538-f7c1-4118-8b7b-894950dd5c34#ImportingWondowsDeviceDrivers
did you "Specify the option for duplicate drivers: Select how you want Configuration Manager to manage driver categories when a duplicate device drive is imported." ??
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Importing drivers takes long time

Hey all, i have a question about importing drivers. I'm importing drivers right now into one package from source that is about 1GB for one specific laptop. It already took 4 hours and its still importing. Why it is taking so much time??? Its not about
network issues- network works great. Anyone?

It's not about processor. The driver packs out there have a lot of info in them that just simply takes time to churn through. Additionally, all of the files needs to be copied to the package source location specified during the import wizard. Thus, it
simply can take a long time for this to happen based on many different variables.
Jason | http://blog.configmgrftw.com | @jasonsandys

Failed to import drivers System Center 2012 Config Manager on Windows 2008 R2 Datacenter

Hello, I am having a problem importing Surface Pro 3 drivers into SCCM 2012 on Win2008 R2 Datacenter for OSD. I get the message that the selected drivers are not applicable to any supported platforms. I know there was a hotfix for SCCM 2007
and Win7 only drivers. Is there one for SCCM 2012 and Win8.1 drivers? Or is there something else I need to be looking at? Everything I find is for SCCM 2007 not 2012. Any push in the right direction is greatly appreciated.

Hi,
Please check the answer of the thread below to see if it can also resolve your issue.
Quote:
They verified that this is NOT an SCCM 2012 Issue, but is in fact an issue with the underlying server OS of (in this case) Server 2008 R2 SP1. There is a known bug with inf file verfication: http://support.microsoft.com/kb/979492, but the hotfix
doesn't currently fix it.
The workaround is to edit the Manufacture section of the affected inf files, and add NTx86.6.1.1 to the line, like this:
[Manufacturer]
%Microsoft% = Microsoft, NTamd64,NTx86.6.1.1
https://social.technet.microsoft.com/Forums/en-US/534b67e5-d2db-457a-863c-f0bd381eaf4d/driver-is-not-applicable-to-any-supported-platforms?forum=confi
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Importing drivers in SCCM 2012

Hi,
I like to have a one to one relationship between drivers and PC models.
I can get this by using a text file in every folder with and inf/sys file "_Lenovo_T520_Win8.1.txt"
I know this will use more storage, but is there anything else?
Is this supported?
Could I recommend using this "feature" to customers?
Best Regards,
Stian

Well its not needed, but will help greatly when removing drivers...
Dell:s drivercabs does this for me with their release.dat file in each folder with a .inf file while Lenovos versions does not. When I import the drivers from Dell every driver get one category while Lenovo drivers get multiple categories. If you
then want to remove the first imported Lenovo model from the drivers tab you gonna end up with a bunch of drivers pointing to the place where the first models driver source was, the one you want to remove..
Or is there some automatic way to fix it? Sure removing all the driver / driver packages and importing them again from the driver source folder works but thats not exactly my idea of fun!

Adding drivers to MDT that have no .inf file

I am currently creating images for a deployment server at work and have come across a problem. A few of the drivers I need to add, including the chipset driver, have no .inf files that I can see, I have extracted the .exe file using 7zip but this just produces
a number of random files. Can anyone help please??? I am using MDT 2013 and server 2012 essentials R2
Thanks

* You should only be using signed drivers in your environment.
* In order to get a *signed* driver from Microsoft, the IHV must supply a driver package that is installed via the *.inf file
* IHV's can add a *.exe wrapper after the fact, but the *.inf driver package is in there somewhere.
I have seen some instances of driver packages that have many working components that require a *.exe to install the individual *.inf parts in the correct order (some display drivers are like that), but these kind of drivers can be installed as an application
in the full OS. Any driver required to boot, should supply an *.inf package, if not please let us know so we can shame the IHV in question.
Additionally, some driver packages can be extracted without installation have you tried running the driver package with the /? switch to see if you can extract? or have you tried monitoring the %temp% directory to see what got created? Driver packaging
is an Art.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

MDT Console with more then 15 machines, How to use the same drivers for more machines.

Hello,
I'm am looking for a solution to make our MDT design as effective as possible(as small as posible).
The Situation:
The company has more then 15 different computers added to the MDT console for the automated installation of Windows 7. The installations are done in 2 different ways, 1 with a local USB key installation (with the deployment folder on the USB key) and the other
installation is a network USB key installation (with the deployment folder on the server).
The local USB key exists for offices in parts of the world where the internet connection is poor.
The problem:
We have machines which can use the same driver for different kinds of hardware functions (LAN, WLAN, etc..)
If we add a new machine to the MDT and we don't check the box for "Import drivers even if they are duplicates of an existing driver" we will automatic use the driver which already exists in the deployment folder. If say half a year
later we stop using an older machine which "may" have drivers that are being used for other machines and we delete the machine from MDT we should
NOT check the box "Completely delete these items, even if there are copies in other folders". The problem is that this can also lead to a lot of unused drivers in the deployment folder also because we do not know exactly how many
computers are using a certain driver.
At the moment we have another deployment share with for each machine its own drivers installed (so some drivers will be multiple times in the deployment folder) as you can guess this becomes really big.(deployment folder of more then 24 GB). The advantage
of this is that we can delete a machine from the MDT list without having to worry if the drivers for that machine might be used by other machines. It is now just becoming to big in size(GB).
The Question:
Is there not an option within MDT that checks automatically if the drivers connected to a certain machine in MDT are being used by other machines? In this case we would check the box "Completely delete these items, even if there are copies in other folders"
and MDT would not delete the drivers which are still used for the installations of other computers.
Thanks in advance.
Greets,
Arie

Arie,
I think you are over-complicating this. Basically using drivers that already exist is the way to go. Otherwise drivers will be imported a second, third or fourth time. Which also takes up allot of disk space. If you're concerned about driver management,
then I would suggest to drop your concerns, since there is nothing to less you can do about this particular issue. As long as you don't delete the driver that's been imported earlier by another machine there is nothing to worry.
Ask yourself:
- how long am I going to support model x
- how many times do I want to update drivers
With selection profiles you can easily target which content needs to go where (on your USB drive of-course)
I can imagine that managing 25 shares for 25 different models, just because you 'refuse' to have old drivers in your share, or have removed support for some hardware models, isn't really time and energy efficient too.
If you take a look in your deploymentshare\control folders you will see some XML files. These XML files hold all the entries in your deploymentshare. So your drivers.xml and drivergroups.xml (depending on the number of groups you have) are going to be very
big XML files. These XML files are read by MDT to identify the objects in MDT and under which folder the objects are located.
It's not possible to create or have an dependency between driver files and hardware models, other then creating groups under "Out-of-box Drivers" and using selection profiles.
Another suggestion would be to decrease your number of hardware models drastically. On the other hand, having 25 Gb of offline media isn't really a big deal either. Portable and removable media of those sizes (32 and 64 Gb) isn't that expensive as it used
to be 5 years ago.
Don't get me wrong, I perfectly understand your desire to manage this, but MDT doesn't provide any other way, then the things I have pointed out to you here.
Good luck! :)
If this post is helpful please click "Mark for answer", thanks! Kind regards

Updating drivers already imported into SCCM 2012

Hi
We imported drivers for all our models into sccm when we set it up.
Obviously there are now new versions of these drivers.
What's the best way to remove the old and add new drivers to sccm?
This is NOT a question about updating drivers on clients but in sccm it self.
Kindest regards, Martin

Hi,
Please refer to the link below:
SCCM OSD driver best practices
http://hayesjupe.wordpress.com/sccm-2012-osd-driver-good-practice/
ConfigMgr Driver Injector
This tool will allow you to capture installed drivers on your workstations and then will
automatically import them in ConfigMgr 2012.
http://gallery.technet.microsoft.com/ConfigMgr-Driver-Injector-aae7d17d
Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

SCCM 2012 R2 Boot WIM DISM - Drivers Failing -hr:0xc0000135‏

Hello OSD Experts,
I have upgraded my SCCM 2012 RTM to SP1(Not installed any Cumulative updates) then to SCCM 2012 R2 Successfully... I did not get any errors.
Before Upgrade my SCCM 2012 RTM/SP1 Images are removed from DP Targets.
Now my next high priority task is I wanted to integrate my Hardware models NIC & Mass Storage Drivers to my Boot Images, So that my OSD will work without any issues. But am getting errors, when I try
to add by DISM command to the Boot Images.
I have taken Default boot.wim file from SCCM 2012 R2 and copy pasted to my work location and ran the DISM command... however I am not successful in this for integration.
Has anyone have already have solution for this let me know.
<<<AV is in Disabled state during DISM.. Still no Luck>>>
<<<<<I tried to ran the DISM on Windows 8 & Windows 2008 R2>>>>>
Attached my DISM.Log @OneDrive... http://1drv.ms/1gdUi6w
Failed to create Dism Image Session in host. - CDISMManager::LoadImageSession(hr:0xc0000135)
DISM Manager: PID=3200 A problem ocurred loading the image session. Retrying... - CDISMManager::CreateImageSession(hr:0xc0000135)
DISM.EXE: Unable to start the servicing process for the image at 'E:\Boot_WIM\SCCMR2_WIMS\X86\Temp'. HRESULT=C0000135
<<< I have already checked this link but no luck... http://social.technet.microsoft.com/Forums/en-US/6b9facc4-9174-4ae7-a8a0-98d88d7f8a95/dism-error-0xc0000135-when-attemptign-to-add-drivers-to-mounted-2012-image?forum=mdt
>>>
Thank you In Advance,
HunBoy Started learning from this page

Hi,
You could use SCCM console to add these drivers. From the SCCM console, go to Operating Systems -> Drivers. Right click and select Import Drivers and follow the wizard. Or go to Operating Systems -> Boot Images -> Right click the boot image in question
-> select Properties. Select the Drivers tab and click on the add button on the right and then select the NIC drivers.
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

MDT and capture & sysprep existing machine

Hi,
In a few special situations I need to be able to capture and sysprep existing physical machine. In MDT there is this Sysprep & Capture task sequence template. I think it's just what I need, but I have read somewhere before that it shouldn't be used for
some reason. Is anyone actually using this?

Generally, if you are deploying to *more* than one make and model of machines, the recommended procedure is to build your images within Virtual Machines like Hyper-V (which is free on Windows 8.1), When you build using virtual machines, Windows won't need
to load any extra Drivers into your image that will be unnecessary on other machines.
However... If you have a lot of machines that are all of the same make/model and installation speed is important, then sure, imaging via a physical source is OK.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com
Customer sent us a preconfigured physical machine and we just need to capture image from that and deploy it to few hundred identical machines.
I have previously used manual sysprep process and after that use DISM to read hard disk to WIM file. Then import WIM to mdt. That works but too much manual work.

MDT - iaStorA.sys error when starting up, Status: 0xc0000098, multiple errors updating deployment share

I recently had rearranged our imaging by creating selection profiles for each computer model and then creating a task sequence for each model so that it looks for a model and only injects the drivers for that model. Everything had been working great
and then we got a new batch of Dell Latitude E6440's in. I checked over the machine and just wanted to make sure nothing changed so i grabbed a couple drivers off of it and uploaded them into mdt under that model. I went to update the deployment
share and started to get a whole host of Error: 2, no driver packages were found on the specified path. Verify the driver .INF file are in the specific location and try the command again. It points to the dism log and exit code is =2 then it says DISM
/Add-Driver failed, rc = 2 and lists all the drivers that had failed. It was a whole bunch for both the x86 and x64. Although i didnt add all these drivers. I only messed with the wifi and nic driver and it was only two files. I ran
through imaging and there were no issues it rebooted windows is about to start and it goes to the black screen with the iaStorA.sys message. I checked everything, i looked over all the chipset drivers i knew i imported and those were still there. I
downloaded the WINPE stuff from dell and found the driver and made sure to import everything in that folder and it skipped it as it said it was still there. I wanted to make sure it wasnt the whole mdt server so i imaged a different computer model all
together and that worked. So i deleted every driver out for this model made sure to delete it if it was in other places. I am now in the process of only including very specific drivers ie just the nic and display and audio and see if it will get
passed first bootup. But what would make it go from working every time for about 3 weeks now to all of a sudden not injecting drivers through updating the deployment share and causing a problem for just this image. I am including the dism log and
it is lengthy. The drivers are all sitting all sorted out in their respected folders on the desktop of the share. This has never been an issue before. here is the log
=== Making sure the deployment share has the latest x86 tools ===
=== Processing LiteTouchPE (x86) boot image ===
Building requested boot image profile.
Determining if any changes have been made in the boot image configuration.
No existing boot image profile found for platform x86 so a new image will be created.
Calculating hashes for requested content.
Changes have been made, boot image will be updated.
Windows PE WIM C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\en-us\winpe.wim will be used.
WIM file mounted.
Deployment Image Servicing and Management tool
Version: 6.3.9600.17029
Image Version: 6.3.9600.16384
There was a problem opening the INF file. D:\Windows7\Out-of-box Drivers\hdc\iaAHCI_8.9.8.1005_157DE4AE7437DC1A46C7E0E4B3294E513CB47D80\iaAHCI.inf Error: 0x80070002.
Error: 2
No driver packages were found on the specified path.
Verify that the driver .INF files are in the specified location and try the command again.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
Exit code = 2
DISM /Add-Driver failed, rc = 2.
Injected driver Intel hdc iaAHCI.inf 8.9.8.1005 (2)
Injected driver Intel hdc ibexahci.inf 7.0.0.1013 (14)
Deployment Image Servicing and Management tool
Version: 6.3.9600.17029
Image Version: 6.3.9600.16384
There was a problem opening the INF file. D:\Windows7\Out-of-box Drivers\hdc\ibexahci_7.0.0.1013_CDE6EABDFCC22A23476F9CB4EA115D63FF4A6DBE\ibexahci.inf Error: 0x80070002.
Error: 2
No driver packages were found on the specified path.
Verify that the driver .INF files are in the specified location and try the command again.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
Exit code = 2
DISM /Add-Driver failed, rc = 2.
Injected driver Intel hdc ibexahci.inf 7.0.0.1013 (15)
Injected driver Intel hdc ibexid2.inf 9.1.1.1013 (6)
Deployment Image Servicing and Management tool
Version: 6.3.9600.17029
There were about 2,000 plus more lines of the same stuff.
For future purposes where should the driver be when import them into mdt and do i need to then keep them? I am still learning all this stuff after taking over the roll in October of 2014. Any help would be greatly appreciated.

Hi KheenanHalvorson,
According to the log ,it seems that there is something missing in the driver package .
According to your description ,I assumed that you have configured the whole process correctly.
To deploy the drivers in this way the driver package should include two files an INF and SYS file .We may need to replace the driver package with another one including the INF file .
Here is a link for reference:
How to manage Out-of-Box Drivers with the use of Model Specific Driver Groups in Microsoft Deployment Toolkit 2012 Update 1
http://blogs.technet.com/b/askcore/archive/2013/05/09/how-to-manage-out-of-box-drivers-with-the-use-of-model-specific-driver-groups-in-microsoft-deployment-toolkit-2012-update-1.aspx
"One thing to note about Driver injections is that the driver must have an INF and SYS file in order for us to install the driver this way. If a driver installs via an EXE and there is no way to extract that driver to reveal the actual INF
and SYS file, then you would be forced to add that driver EXE package as an application and install it as an application. "
Best regards
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Importing drivers to MDT

Similar Messages

Maybe you are looking for