Driver Automation Tool - Automate Driver Downloads & Packaging for SCCM/MDT

The script generates a PowerShell GUI to automate the processes of downloading, extracting and importing driver packages for Dell, Lenovo, HP and Microsoft systems.

 
 
 
 
 
4.9 Star
(74)
39,837 times
Add to favorites
System Center
1/6/2019
E-mail Twitter del.icio.us Digg Facebook
Sign in to ask a question


  • Unable to download HP BIOS
    2 Posts | Last post Sat 10:46 AM
    • When i try to download any kind of HP BIOS i get the error: Warning: Unable to retrieve BIOS Download. Any ideas ?
    • Same issue here. Can't download HP BIOS with version 6.1.4
  • Driver import Issue
    2 Posts | Last post Thu 11:15 PM
    • When I import some driver and had some network related issues where the process stops and I restart the process again, i get the following error.  I have verified that the package does not exist and I have deleted the new category created plus all of the files associated with the model and no package was ever created.  Any help will be greatly appreciated.
      
      error:
      
      an object with the specified name already exists
    • Its mean, that package is already in SCCM. Search packages.
  • Ongoing issue adding INF that aren't technically drivers
    1 Posts | Last post Thu 1:35 AM
    • I'd seen this issue before, especially with certain Dell CABs for Windows 7, but now for the first time I've seen it with a Win10 cab. New driver pack for the Optiplex 7040, Win10 version A13.
      
      Looking at the drivercatalog.log file on the site server, I see this:
      \\server\share\DriverSources\Dell\Optiplex 7040\Windows10-A13\7040\Win10\x64\video\X7YWM_A00-00\W10-x64\Display\WT6A_INF\C7323693.inf is not applicable to any supported platforms.
      
      It seems like SCCM is fully aware it's not a valid driver and is returning that error message back to this tool, but the tool is not handling that particular error very well. It stops at that driver, errors out and refuses to process any other INF files in that CAB, which is not ideal.
      
      For now I've had to import the drivers manually and create the package myself, but that's what this tool is supposed to automate, and I much prefer the automation. :)
      
      Any chance of some update that will recognize this (strangely common) issue with INF files that SCCM doesn't recognize as a valid driver, and just ignoring it, continuing on? That would be awesome.  I mean, if it's a real error of some sort (couldn't read the INF, couldn't parse it, etc) then by all means, error out, but in this case, a warning seems more appropriate.
  • Windows 7 drivers
    1 Posts | Last post Wed 5:02 PM
    • Impossible to download drivers for Lenovo T460 and T470 Windows 7
      
      ======== Processing Lenovo ThinkPad T460p Downloads ========	DriverAutomationTool	2019-01-15 15:09:45	23640 (0x5C58)
      Info: Starting Download, extract and import processes for Lenovo model: ThinkPad T460p	DriverAutomationTool	2019-01-15 15:09:45	23640 (0x5C58)
      Info: Setting Lenovo variables	DriverAutomationTool	2019-01-15 15:09:45	23640 (0x5C58)
      Info: Lenovo ThinkPad T460p matching model type: 20FX	DriverAutomationTool	2019-01-15 15:09:45	23640 (0x5C58)
      Info: Looking Up Lenovo ThinkPad T460p URL For Windows version win7	DriverAutomationTool	2019-01-15 15:09:46	23640 (0x5C58)
      Info: Searching for Lenovo ThinkPad T460p exe file on http://support.lenovo.com/downloads/ds112244	DriverAutomationTool	2019-01-15 15:09:46	23640 (0x5C58)
      Info: Passing through Windows version as 7	DriverAutomationTool	2019-01-15 15:09:46	23640 (0x5C58)
      Info: Passing through Windows architecture as x64	DriverAutomationTool	2019-01-15 15:09:46	23640 (0x5C58)
      
  • This is new.
    1 Posts | Last post Tue 3:04 AM
    • Error: The response content cannot be parsed because the Internet Explorer engine is not available, or Internet Explorer's first-launch configuration is not complete. Specify the UseBasicParsing parameter and try again. 
      
      I received this because on my workstation I removed Internet explorer as an available web browser.  This was using the 6.1.1 exe and the 6.1.3 ps1 file.  I do not get this when using the newest 6.1.4 version but then again it does not like how our proxy system works so I am stuck.  For me to use this I have to connect to configmgr with one account while logged on to my pc with a low rights account.  We are switching to a new style of proxy from Bluecoat called unified agent and my admin user profile does not load that when running the tool with right click run as...  Thought I would share this error as it was interesting
  • Seems to hang while trying to extract drivers
    2 Posts | Last post January 12, 2019
    • Hi,
      The application seems to hang while trying to extract drivers. I don't see any changes on the GUI nor the logs. The last entry is:
      
      ConfigMgr: Waiting for extract process (Process: tc_m920t-m920s-m720t-m720s-m920q-m720q-m920x-v530-p330tiny_w1064_201811) to complete..  Next check in 30 seconds
      
      This has been waiting a long time. Is there something I can check?
      
      Thanks!
      
    • It was a permissions issue. I ran this in a PS window as admin, not my all powerfull network creds :)
      
  • Dell Latitude 5290 2-in-1 Drivers Problem
    1 Posts | Last post January 11, 2019
    • Hi Maurice
      
      Thanks for all your great work. Saves us alot of time!
      
      There is still a small problem with the "Dell Latitude 5290 2-in-1" model.
      Somehow it always thinks the newest driver revision is "1". And in SCCM it will also put the version as "1". And because of that it always thinks it has the newest version. 
      I usually just set it to "0" when i know that there is a new version. But i thought maybe you might fix this one day :)
      
      Here's an example. As you can see the real version of the package it downloads is "A05" and not 1.
      
      ======== ConfigMgr Latitude 5290 2-IN-1 DRIVER PROCESSING STARTED ========	DriverAutomationTool	11.01.2019 13:34:05	7860 (0x1EB4)
      ConfigMgr: Retrieving driver pack site For Dell Latitude 5290 2-IN-1	DriverAutomationTool	11.01.2019 13:34:05	7860 (0x1EB4)
      ConfigMgr: URL found: https://downloads.dell.com//techcenter/enterprise-client/w/wiki/12454.latitude-5290-2-in-1-windows-10-driver-pack	DriverAutomationTool	11.01.2019 13:34:05	7860 (0x1EB4)
      ConfigMgr: Latest driver revision found - 1	DriverAutomationTool	11.01.2019 13:34:05	7860 (0x1EB4)
      ConfigMgr: Checking ConfigMgr for driver packages matching - Drivers - Dell Latitude 5290 2-IN-1 - Windows 10 x64	DriverAutomationTool	11.01.2019 13:34:05	7860 (0x1EB4)
      ConfigMgr: New driver package detected - Processing	DriverAutomationTool	11.01.2019 13:34:06	7860 (0x1EB4)
      ConfigMgr: Creating Latitude 5290 2-IN-1 download folder	DriverAutomationTool	11.01.2019 13:34:06	7860 (0x1EB4)
      ConfigMgr: Downloading 5290 2-IN-1-Win10-A05-VC21C.CAB driver cab file	DriverAutomationTool	11.01.2019 13:34:06	7860 (0x1EB4)
      ConfigMgr: Downloading from URL: https://downloads.dell.com/FOLDER05258946M/1/5290 2-IN-1-Win10-A05-VC21C.CAB	DriverAutomationTool	11.01.2019 13:34:06	7860 (0x1EB4)
      
  • I don't get Dell Bios
    1 Posts | Last post January 11, 2019
    • Dear Maurice
      
      I perform Download only and select BIOS for several Dell Devices.
      When i start the Download process, for every chosen model i get:
      
      "Error: Issues occurred while extracting XML file"
      
      Allready checked Access rights, ran the tool from exe and PS, ran the tool from my computer..
      Can you give me a hint?
  • Sloooooooooow
    3 Posts | Last post January 10, 2019
    • Why is importing driver inf so insanely slow. It can take up to 2 hours before the drivers for 1 models is fully imported. If I download the drivers and import them via import drivers in SCCM it takes about 10 minutes or less.
      
      Also most of the time it does not finish the importing process and comes with a message that sms provider has an error. From the 6 models 1 of them succeeded.
    • I have same experience, no idea what is a reason.
    • Slow performance of importing drivers (check time).
      
      ConfigMgr: Importing driver INF 71 of 166: SPUVCbv10.inf	DriverAutomationTool	2019-01-10 15:44:06	12412 (0x307C)
      ConfigMgr: Importing driver INF 72 of 166: SPUVCbv11.inf	DriverAutomationTool	2019-01-10 15:45:45	12412 (0x307C)
      ConfigMgr: Importing driver INF 73 of 166: SPUVCbv12.inf	DriverAutomationTool	2019-01-10 15:47:23	12412 (0x307C)
      ConfigMgr: Importing driver INF 74 of 166: SPUVCbv13.inf	DriverAutomationTool	2019-01-10 15:49:03	12412 (0x307C)
      ConfigMgr: Importing driver INF 75 of 166: SPUVCbv14.inf	DriverAutomationTool	2019-01-10 15:50:41	12412 (0x307C)
      ConfigMgr: Importing driver INF 76 of 166: SPUVCbv15.inf	DriverAutomationTool	2019-01-10 15:52:19	12412 (0x307C)
      ConfigMgr: Importing driver INF 77 of 166: SPUVCbv16.inf	DriverAutomationTool	2019-01-10 15:53:58	12412 (0x307C)
      ConfigMgr: Importing driver INF 78 of 166: SPUVCbv17.inf	DriverAutomationTool	2019-01-10 15:55:36	12412 (0x307C)
      ConfigMgr: Importing driver INF 79 of 166: SPUVCbv18.inf	DriverAutomationTool	2019-01-10 15:57:14	12412 (0x307C)
      ConfigMgr: Importing driver INF 80 of 166: SPUVCbv19.inf	DriverAutomationTool	2019-01-10 15:58:53	12412 (0x307C)
      
  • Slow performence
    1 Posts | Last post January 10, 2019
    • Driver import take a lot of time. Importing drivers takes one driver per 3 minutes.
      What could be a reason of that?
1 - 10 of 355 Items