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
42,954 times
Add to favorites
System Center
E-mail Twitter Digg Facebook
Sign in to ask a question

  • Find Models Not working for Dell
    2 Posts | Last post Tue 2:09 AM
    • Good day, I recently installed the D.A.T. and was able to list and import drivers from Dell last week, but for some reason come Monday, I am unable to pull a list of Dell models. I am able to pull Lanovo models, but we are a Dell shop. I have run a repair on the package, but have not had any success. Any help would be appreciated and thank you for the work. Config: Deployment Platform- ConfigMgr - Driver Pkg, Download type- All, Operating system - Windows 10, Architecture - 64 bit, No Proxy Server Used...
      Info: Reading driver pack XML file - C:\Program Files\SCConfigMgr\Driver Automation Tool\Temp\DriverPackCatalog.xml
      Info: Found: 33 known Dell models
      Info: No Dell models found. If you are using a proxy server please specify the proxy in the Proxy Server Settings tab
    • I ended up deleting the "C:\Program Files\SCConfigMgr\Driver Automation Tool\Temp\" and then all was working again.
  • Import Models not working for HP
    3 Posts | Last post May 16, 2019
    • If I enable the option to Import Models it imports and selects EVERY HP Model - even ones that I have not previously selected.
    • Can you please advise the steps to reproduce this issue?
    • I'm having the same problem. just does this when i check the "import model" as yes.
      If i disable this, nothing gets selected.
      i worked around it by adding the models i want to the config file, as unchecking "import model".
  • Download BIOS packages
    2 Posts | Last post May 16, 2019
    • Hi,
      Anyone else having problems when downloading HP BIOS packages?
      For me, the operation just times-out:
      "Info: URL is	DriverAutomationTool	2019-05-16 14:39:27	4816 (0x12D0)
      ======== Errors(s) Occurred ========	DriverAutomationTool	2019-05-16 14:44:28	4816 (0x12D0)
      Error: An error occurred while attempting contact - The operation has timed out.	DriverAutomationTool	2019-05-16 14:44:28	4816 (0x12D0)"
      If i visit the URL manually, both from SCCM site server or my personal computer, then it downloads the cab just fine.
      Drivers work, and the tool works otherwise.
    • The same thing for every HP model, it's about 35 models.
  • MDT imports x86 and x64
    1 Posts | Last post May 16, 2019
    • Hi Maurice,
      Not sure if this is a known issue.
      While importing the "Dell Optiplex 9010 AIO" drivers, I noticed that the driver automation tool is ignoring my architecture selection of x64. It's importing both x86 and x64 into MDT.
      It works as expected if I change line 14812 from:
      Import-MDTDriver -path "$MDTDriverPath" -SourcePath "$DriverExtractDest"
      Import-MDTDriver -path "$MDTDriverPath" -SourcePath "$DriverFolder"
      I'm using version 6.2.0
      Thank you,
  • $SiteCode isn't being configured
    2 Posts | Last post May 15, 2019
    • I've read the user guide and have met all the prerequisites but can't seem to get it to connect to SCCM. When it runs Set-Location -Path ($SiteCode + ":") it returns an error: Cannot find path 'C:\Program Files\SCConfigMgr\Driver Automation Tool\:' because it does not exist
      I trawled through the DriverAutomationTool.ps1 and I can't find it setting the value of $SiteCode anywhere
    • Derp.. It had the MP not Primary as the site server. Seems to be connecting now. 
  • Schedule Job in MDT environment
    2 Posts | Last post May 10, 2019
    • Hi Maurice,
      I am trying to get the silent run via scheduled task to work in my MDT environment with version 6.1.7. Does that work or does it require SCCM? I have set it up with the highest privilege possible, it creates the task, Logs, Settings and Temp folders. Then it gives an error message saying "ConfigMgr PowerShell Module Not Found". I don't know if that is a requirement? 
      Then it proceeds to "Info: Download Type: Drivers" but the scheduled task stops without saying why. See the log below.
      Error: ConfigMgr PowerShell Module Not Found
      Mode: Silent running switch enabled
      Update Alert: Newer Version Available - 1.0.1
      ======== Querying Model List(s) ========
      Info: Downloading Dell Product List
      Info: Downloading Dell Driver Pack Cabinet File from
      Info: Expanding Dell Driver Pack Cabinet File: DriverPackCatalog.xml
      Info: Reading Driver Pack XML File - C:\DriverAutomationTool\6.1.7\Silent\Temp\DriverPackCatalog.xml
      Info: Importing Into Products: MDT
      Info: Download Type: Drivers
      Any ideas?
    • Same issue here, but than with ConfigMgr.
  • The tool is timeing out?
    1 Posts | Last post May 09, 2019
    • Had initiated drivers and bios download for ~20 dell models. After had worked for about 1.5 hours and processed few models the tol stopped responding. No errors in log were recorded. The last message "ConfigMgr: Creating Package for Dell Latitude 7280 (Version A10)". Any comments on what went wrong? I'm using standard sccm packages. 
  • Incorrect Lenovo Driver Download
    1 Posts | Last post May 08, 2019
    • Not sure how often this may come up, but when trying to download drivers for a T480 Win 10 1809 the tool kept grabbing 1709 drivers because of the file name "tp_t480_w1064_1703_201809.txt"
      Lines 11266-11268
      $Win10VersionLink = $MatchingLink | Where-Object { $_ -match $OSVersion } | Select-Object -Last 1
  • Error: An object with the specified name already exists.
    3 Posts | Last post May 08, 2019
    • I deleted a package inadvertently and an having trouble getting it recreated. When I run the tool it detects a new driver package available, downloads the .cab, extracts the files, and begins to import drivers but immediately throws "Error: An object with the specified name already exists".
      I have confirmed the driver package is deleted, the individual drivers were deleted, the Driver Category was deleted, the driver source folder was deleted, and the driver package folder was deleted.  I can't figure out what it's running into that makes it believe the name already exists.  What did I miss?
    • It was actually the previous version of the driverpkg that still existed causing the issue.  Dell packages all have the same name, I added the version number to the title of the previous package and it created the new one just fine. 
    • Looks like this could be resolved by adding $DriverRevision the string used to set $CMDriverPackage 
  • Automate HP and Dell Drivers
    3 Posts | Last post May 06, 2019
    • Is there a way to automate HP Windows 10 1809 and Dell Windows 10 driver download? When I select one of booth the others are deleted from the XML.
    • This is to do with the fact that Dell do not release drivers based on the individual Windows 10 builds. If they were to switch to this model, then there would be no issues in doing so, bit for now you will have to run a selection for Dell and then a separate selection for HP.
    • Thank you for your answer Maurice. Is there a way to automates HP and Dell on a single machine or do I need 2 machines for this? Thank you!
1 - 10 of 459 Items