ConfigMgr Driver Injector

This tool will allow you to capture installed drivers on your workstations and then will automatically import them in ConfigMgr 2012.The tool is composed of two utilities :The driver grabber that can be deployed via ConfigMgr or that you can launch manually on your workstations.

 
 
 
 
 
4.7 Star
(31)
23,718 times
Add to favorites
System Center
4/7/2015
E-mail Twitter del.icio.us Digg Facebook
Sign in to ask a question


  • Distribute drivers to distribution points
    1 Posts | Last post April 04, 2018
    • Hi.
      Excellent work. The script successfully collects, saves and organizes the drivers from all computers and operating systems, and it shows them in the sccm console.
      But my doubt is: it doesn't, automatically, distributes the driver packages to the distribution points. Should I distribute them manually? Or it all work fine in a install image task sequence in the section Auto Apply Drivers even if the driver packages are not distributed?
      Thank you so much.
  • ConfigMgr 1606
    1 Posts | Last post June 07, 2017
    • same question as the one asked last..will the injector work with the latest versions of SCCM. 
      Also wondering if there are any plans to get it to work with Win10?
      
      Thanks for your assistance 
  • ConfigMgr 1606?
    1 Posts | Last post January 12, 2017
    • Will this work on ConfigMgr 1606? I manually run the grabber then attempt to import all drivers from a directory into SCCM. Nothing shows up and no error. If I try to import the driver specifically from each category folder created by the grabber, I get "Error importing the selected driver". 
      
      Thanks for any help you can provide.  
  • Importing driverr localy and copying to SCCM server
    2 Posts | Last post August 23, 2016
    • Hi. 
      Thanks for this great tool.
      If I export the drivers localy and copy them to my SCCM server is there anything I should be aware of? Our driver structure isnt like the one you describe inside the Driver inject txt file. Do I need to make the folder structure to make drivers work in the task sequence? Got BSOD on our HP Prodesk 400 G3 after deploying the drivepack i exportet from the PC. Our other models works with the HP sccm driverpacks. 
    • Hi,
      
      It depends on what you meant with your question :
      1) If you want to import manually some drivers you captured with the tool : no problems
      2) If you want to use the "driver injector" with a folder that wasn't created with the grabber then it won't work as the "injector" requires a specific folder structure and few xml metadata files
  • Issues importing drivers
    5 Posts | Last post July 01, 2016
    • I’m having issues with the Driver Injector.
      My ConfigMgrDriverInjector.exe XML looks like this
            <add key="MonitorPath" value="\\\\My server\drivers$\Capture\\"/>
            <add key="DriversSourcePath" value="\\\\My Server\drivers$\DRVSource\\"/>
            <add key="DriversPackagesSourcePath" value="\\\\My Server\drivers$\DRVPKG\\"/>
      The captured files are removed from the Capture folder.
      A new folder for the system is created in the DRVSource folder containing files.
      A new folder for the system is created in the DRVPKG folder, not containing files.
      
      In SCCM console Driver Package for the system is created, but no drivers are imported.
      Administrative Categories are created (why have a category for each driver type/class?).
      
      If I import the drivers manually, everything works fine.
      I run the script on the Primary site server.
      Any suggestions?
      
    • ConfigMgrDriverInjector.log
      
      Current subfolder : Realtek High Definition Audio	ConfigMgrDriverInjector.ImportDrivers	01.07.2016 10:11:29	0 (0x0000)
      
      INF file found : oem33.inf	ConfigMgrDriverInjector.ImportDrivers	01.07.2016 10:11:29	0 (0x0000)
      
      Driver version found :  6.0.1.7746	ConfigMgrDriverInjector.ImportDrivers	01.07.2016 10:11:29	0 (0x0000)
      
      Checking driver existence	ConfigMgrDriverInjector.ImportDrivers	01.07.2016 10:11:29	0 (0x0000)
      
      Error in ConfigMgrDriverInjector.CheckIfDriverExists The SMS Provider reported an error.	ConfigMgrDriverInjector.CheckIfDriverExists	01.07.2016 10:11:29	0 (0x0000)
      
      Error in ConfigMgrDriverInjector.CheckIfDriverExists The SMS Provider reported an error.	ConfigMgrDriverInjector.CheckIfDriverExists	01.07.2016 10:11:30	0 (0x0000)
      
      Checking driver existence	ConfigMgrDriverInjector.ImportDrivers	01.07.2016 10:11:30	0 (0x0000)
      
      Error in ConfigMgrDriverInjector.CheckIfDriverExists The SMS Provider reported an error.	ConfigMgrDriverInjector.CheckIfDriverExists	01.07.2016 10:11:30	0 (0x0000)
      
      Driver not foud, a problem occurred during the import process	
      
      ConfigMgrDriverInjector.ImportDrivers	01.07.2016 10:11:30	0 (0x0000)
      
      End of driver is import process	ConfigMgrDriverInjector.ImportDrivers	01.07.2016 10:11:30	0 (0x0000)
    • SMSProv.log
      
      *~*~e:\nts_sccm_release\sms\siteserver\sdk_provider\smsprov\sspobjectquery.cpp(1782) : Failed to parse WQL string SELECT * FROM SMS_driver WHERE ContentSourcePath='\\\\My Server\drivers$\DRVSource\\LENOVO_20FAS0PW00_Microsoft Windows 10 Pro_64-biters\\MEDIA\\Realtek High Definition Audio' AND DriverINFFile ='oem33.inf'~*~*	SMS Provider	01.07.2016 10:11:29	6388 (0x18F4)
      
      *~*~Failed to parse WQL string SELECT * FROM SMS_driver WHERE ContentSourcePath='\\\\My SErver\drivers$\DRVSource\\LENOVO_20FAS0PW00_Microsoft Windows 10 Pro_64-biters\\MEDIA\\Realtek High Definition Audio' AND DriverINFFile ='oem33.inf' ~*~*	SMS Provider	01.07.2016 10:11:29	6388 (0x18F4)
      
      
    • SCCM 1511
      Windows 10 client
      
      Can e-mail full log files if necessary.
      
      The part of the tool that is working is great, especially having the ability to write directly to a share is great when we have huge distances between offices, and not the heavies techs around.
      
      I notice categories for every driver type/class is created. I’ve never done this, why is this good practice? No biggie, but perhaps some adjustment possibilities here?
      
    • Hi !
      
      Every backslash in the config file must be escaped by another one. Your config file should look like this :
      
      <add key="MonitorPath" value="\\\\My server\\drivers$\\Capture\\"/>
      <add key="DriversSourcePath" value="\\\\My Server\\drivers$\\DRVSource\\"/>
      <add key="DriversPackagesSourcePath" value="\\\\My Server\\drivers$\\DRVPKG\\"/>
      
      Driver categories are just here for searching and filtering purpose. There are no best practice on this topic but as I wanted to have less config as possible on the tool to keep it simple I took the decision to create a category per item, so people who use it will have it and others won't care.
      
  • Drivers in SCCM
    2 Posts | Last post April 29, 2016
    • In Sccm, I have the Driver injector created a folder under Drivers with my Brand, model ect, but when I select the folder none of the drivers show up. Same thing with my driver package.  The driver injector created the package, but no drivers show.  I am sure this is due to something I am doing wrong, but I can't figure it out.  Any help would be appreciated, and thanks for this awesome tool.
    • Hi,
      
      Make sure that in the injector's config file you made no mistake. Also make sure you run the program as admin.
  • Drivergrabber missing files
    4 Posts | Last post April 29, 2016
    • Hi mponsot,
      
      Great tool, looking like we may have to recreate all out drivers/packages after an issue and this will save us a lot of time.
      
      Been testing it on our current models and having issues with a few drivers, driver grabber collects the inf files but none of the supporting files so when trying to load the driver windows errors with file not found.
      
      I've collected the debug log along with the resulting folder, registry and also the GhostedDrivers folder is what WinDriverGhost picks up for comparison. (problem device in this case is a Realtek NIC on HP Probook 450 G3) 
      http://1drv.ms/1oJiyFp
      
      Mark
    • Hi Mark,
      
      Thanks for the feedback and the files. I'll work on it ASAP.
      
      Regards,
    • Damn, I should have read this thread before losing a part of may day... :)
      I have the exact same problem with the Realtek PCIe GBE Family Controller on another type of computer (HP ProDesk 400 G3 MT).
      
      Indeed a great tool by the way.
      Thanks
    • Hi,
      
      Thanks for your feedback.
      I'm still trying to figure out how to manage it.
  • Any reason to doubt that this will work correctly on Windows 10?
    2 Posts | Last post April 29, 2016
    • Hi mponsot,
      
      This is a great tool. Is there any reason to doubt that this would work correctly for exporting drivers from a Windows 10 device?
    • Hi,
      
      Each test I've ran on Windows 10 worked. 
      
  • error code 2
    8 Posts | Last post December 18, 2015
    • which means error code 2?
      when I try to import some drivers
      such as Intel® Graphics Media Accelerator
    • i forgot..
      when i try to import through sccm all is ok !
    • but still wondering why and how to fix =)
    • oops 
      sry but sccm doent see too
      export looks like this 
      http://imgur.com/utchacb
    • This is on clean w7sp1 wo updates
    • i try download driver from intel site (manualy)
      this driver export ok with sccm inport wizard
      but injector gives me err (like in first post)
      
      smsprov says
      *~*~e:\qfe\nts\sms\siteserver\sdk_provider\smsprov\sspdriverci.cpp(712) : Failed to access driver INF file '\\thismyserver\source$\OSD\DriversSources\DEPO Computers_DQ45EK___Microsoft Windows 7 Professional_64-bit\Display\Intel(R) Q45\oem2.inf'.~*~*
      
      *~*~Failed to access driver INF file '\\thismyserver\source$\OSD\DriversSources\DEPO Computers_DQ45EK___Microsoft Windows 7 Professional_64-bit\Display\Intel(R) Q45\oem2.inf'. ~*~*
      
      
    • Hi, 
      I also have the same problem... 
      The program is a very good idea. Is this-that the sources are available?
      I also have a proposal of evolution: Ability to manually add drivers with ConfigMgrDriverInjector to preserve the architecture of sources files and packages.
    • Hi guys.
      
      Error 2 generally means "file not found". I guess that driver's metadata are referencing some files that either doesn't exist or could'nt be captured.
      
      Could one of you send me here or by mail a one drive link with a complete capture folder i'll try (when I'll have time) to implement more error control.
      
      D.Po could you clarify your evolution proposal ? 
  • Issues running Grabber
    2 Posts | Last post November 23, 2015
    • Dear mponsot,
      first thanks for this helpful script which made my life easier really. I have issues working with script. first if i use the GUI and capture All Drivers including MS Drivers, all works and i get list of all drivers exported, but if i use the CLI and use the switch /silent /destshare and /captureMSDriver i get a list of drivers that seems to be a little fewer than when i exported drivers using GUI ! what's wrong here?
      full command i use is this:
      configmgr-driver-grabber.exe /silent /destshare:d:\drivers /captureMSDriver
      another issue is when i run this command (V1.1 or V1.2) both versions giving me Errors like this :
      
      System.ObjectDisposedException: Cannot write to a closed TextWriter.
         at System.IO.__Error.WriterClosed()
         at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
         at System.IO.StreamWriter.Write(Char[] buffer, Int32 index, Int32 count)
         at System.IO.TextWriter.WriteLine(String value)
         at LogManagement.LogManager.CreateEntry(String strMessage, Int32 intLogType, String strComponent)
         at DriverGrabber.DriverBackup.backupDrivers(List`1 driverList, String backupLocation)
         at DriverGrabber.Form1.launchProcess()
         at DriverGrabber.Form1.button3_Click(Object sender, EventArgs e)
         at System.Windows.Forms.Control.OnClick(EventArgs e)
         at System.Windows.Forms.Button.OnClick(EventArgs e)
         at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
         at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
         at System.Windows.Forms.Control.WndProc(Message& m)
         at System.Windows.Forms.ButtonBase.WndProc(Message& m)
         at System.Windows.Forms.Button.WndProc(Message& m)
         at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
         at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
         at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
    • Hi,
      
      Destshare must be a UNC path if you want a local backup use \\localhost\d$ instead of d:
      
      For the difference of capture when using silent or gui it's not normal, I'll run some test on my side as soon as I'll have some time.
1 - 10 of 19 Items