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
(109)
45,500 times
Add to favorites
System Center
8/3/2019
E-mail Twitter del.icio.us Digg Facebook
Sign in to ask a question


  • 7490 Bios
    1 Posts | Last post Sun 9:05 AM
    • Hi Maurice
      
      Can't get the 7490 bios to download on the latest version but drivers download
  • Not enough diskspace to complete the task
    2 Posts | Last post Thu 1:03 AM
    • Thank you for your tool. I am running into problem when trying to use your tool. It shows error not enough disk space on C: drive to complete the extraction. What is minimum requirement of hard drive space for this tool to run? I've checked C: drive on server and it still have at least 20GB of free space.
      Can we change extraction process on different drive?
    • Wonderful tool!!!!!! Can't say enough about it. 
      
      I tried looking for this in his powershell, but I couldn't find it. This would be a great idea to change the extraction location. 
      
      
  • 2-in-1 Versions incorrect
    1 Posts | Last post Wed 11:55 PM
    • Having a lot of success with this tool, but found an issue with the Dell 2 in 1 models that we have. Apologies if this is already been raised, I checked a few pages of comments and didn't see anything yet. We're only using Dell so I have no idea if this is a similar issue for Lenovo and HP
      
      I've not dug too deep yet, but from what I can tell the tool gets the model name and version from the DriverPackage data in the catalog. Here are three examples.
      
        <DriverPackage ... dellVersion="A02" path="FOLDER05714171M/1/5300 2-IN-1-win10-A02-R52GX.CAB" ...>
        <DriverPackage ... dellVersion="A02" path="FOLDER05725674M/1/7200 2-in-1-win10-A02-JPV2H.CAB" ...>
        <DriverPackage ... dellVersion="A02" path="FOLDER05716588M/1/5300-win10-A02-8Y1TG.CAB" ...>
      
      The folder and package for the 5300 is correct:
        Name    - Drivers - Dell Latitude 5300 - Windows 10 x64
        Version - A02
        Folder  - Latitude 5300-Windows10-x64-A02
      5300 2-in-1 is incorrect:
        Name    - Drivers - Dell Latitude 5300 2-IN-1 - Windows 10 x64
        Version - 1
        Folder  - Latitude 5300 2-IN-1-Windows10-x64-1
      7200 2-in-1 is incorrect:
        Name    - Drivers - Dell Latitude 7200 2-in-1 - Windows 10 x64
        Version - 1
        Folder  - Latitude 7200 2-in-1-Windows10-x64-1
      
      My guess at this stage is that additional "-" in the naming is causing the split to get mixed. Normally 0 would be model, and 2 would be the version. With the extra "-" in 2-in-1 its all getting a bit mixed up.
      
      Thanks for this. It is so much better than Dell Command!
  • Thank you...
    1 Posts | Last post Wed 8:57 AM
    • Thank you for a great tool and all your hard work!
  • SCCM Standard PKG
    2 Posts | Last post Wed 1:31 AM
    • I have installed and setup the tool.  It downloads and creates the folder stucture fine, But I was under the assumption that this would create the packages in SCCM, but it doesn't seem to be.
      
      Danny
    • Never mind.  Found them.  Folder was called Packagetype under "Packages".  All good.
      
      
  • Dell 5300 2-in-1 missing
    2 Posts | Last post Tue 10:14 AM
    • Although I can find the Dell 5300 2-in-1 in the CatalogPC.xml file, it is not shown in the Model selection. System-ID is 08B6. I've downloaded the most recent version from https://downloads.dell.com/catalog/ - it is the same Drive Automation Tool has downloaded. However I can only find the "normal" 5300. Invoke-CMApplyDriverPackage.ps1 is failing with exit code 9 on this device.
      
      Any suggestions? 
    • This is fixed now in the list, but it was incorrectly labeled 5300V by Dell originally...sorry for the late help
  • Running Run-DriverAutomationToolSvc.ps1 in MDT only
    1 Posts | Last post September 13, 2019
    • Hi Maurice,
      
      Is the scheduled script Run-DriverAutomationToolSvc.ps1 supposed to work on a only MDT server? I have gotten as far as:
      
      Info: Reading Driver Pack XML File - C:\DriverAutomationJob\Temp\DriverPackCatalog.xml
      Info: Importing Into Products: Download Only
      Info: Download Type: Drivers
      Pre-Check: Respository Path Set To E:\DriverDownloads
      ======== Starting Download Processes ========
      Info: Models selected: Precision Tower 3620
      Info: Operating System specified: Windows 10
      Info: Operating System architecture specified: x64
      Info: Site Code specified: P01
      Info: Respository Path specified: E:\DriverDownloads
      Info: Package Path specified: \\server\name
      ======== Processing Precision Tower 3620 Downloads ========
      Info: Starting Download,Extract And Import Processes For Precision Model: Tower 3620
      
      But then it stops. If I run the script manually it complains on row 1177:
      
      You cannot call a method on a null-valued expression.
      At C:\DriverAutomationJob\Run-DriverAutomationToolSvc.ps1:1177 char:5
      + ...$DriverPackageDir = ($DriverCab).Substring(0, $DriverCab....
      + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      + CategoryInfo: InvalidOperation: (:) [], ParentContainsErrorRecordException
      + FullyQualifiedErrorId: InvokeMethodOnNull
      
      Run-DriverAutomationToolSvc.ps1 requires a <Repository> tag in DATSettings.xml, inside the <StorageSettings>. I cannot find that value anywhere in the application GUI so I don't know what to set it to...do you?
      
      The script has not been updated since 2017 so I'm wondering if it's maybe missing something?
      
      Regards,
      Mikael
  • Import to MDT - HP issue
    1 Posts | Last post September 13, 2019
    • First of all - BIG thanks for this tool - its just amazing!!!
      
      My issue - models from HP are incorectly imported to MDT so it causes problems with our Total control of drivers…
      Make and model are for example:
      Make: HP
      Model: HP EliteBook 840 G6
      
      BUT from Driver automation tool it is imported as:
      Make: Hewlet-Packard
      Model: Elitebook 840 G6 Notebook PC
      
      Result is failed instalation of drivers if not manually corrected :(
  • Lenovo Driver searching not correct
    1 Posts | Last post September 12, 2019
    • I have been noticing of late that there are a number of newer Lenovo hardware that will not show up when I select Windows 10 1903 (Like ThinkPad P52) but when I select just Windows 10 I can see it pull down the 1903 driver file.
      
      Just wanted to let you know what I am seeing, extra steps but at least I can get the newer drivers.
  • Driver packages not being added to OS/Drivers
    1 Posts | Last post September 12, 2019
    • Hi, I cannot use the driver packages because they have been added to \Software Library\Overview\Application Management\Packages, not to \Software Library\Overview\Operating Systems\Driver Packages. Therefore they are unavailable to me when applying drivers in the task sequence. What am I missing here?
      Thanks!
1 - 10 of 527 Items