Well it is finally here, the latest update to the Driver Automation Tool. Sorry this has taken a while to put together but there have been significant changes to both the tool in this build, all of which is thanks to community interaction. In fact the Driver Automation Tool reached something of a milestone recently, with over 20k downloads in the first year of becoming available, so thank you everyone!
So lets go through the list of feature changes:
The new version gets rid of the previous list boxes used for model listings and selected models in favor of a data grid format, this should be more intuitive to use and now includes the ability to search for specific models within the list. This has taken a considerable number of hours to complete, however I think the tool now feels more functional for it.
Below is an example showing the results for a search for ProBook models against the HP model list:
HP Driver Catalogue
In response to those of you using HP hardware and who have mentioned about the fact things like hotkey support require additional drivers, I have added a new tab – HP Driver Catalogue. Here you will see a full list of all additional drivers available based on the OS selection. This way you can automate the download and packaging of those additional drivers;
Note that we will be updating our GitHub scripts section with an automated script to install the content. It is also worth noting that the XML file used for the drivers is around 25MB so it can take a few moments to download
One of the main topics that kept coming up was the fact that the tool created packages in the root folder. So in this version, both drivers and BIOS downloads will create their own folder structure within the packages folder based on the following naming – Driver/BIOS Packages\Make
Revised Settings Tab
Now all of the settings which were previously spread out over several sections are now contained within the ConfigMgr Settings page.
Note: For MDT and download only jobs you will still need to specify the storage locations on the ConfigMgr Settings tab
Storage Location Changes
As requested BIOS packages will now be created in the same location as driver packages.
There are a number of minor fixes in the latest release, most noticeably are is a fixes for packages not distributing correctly after creation, and for Dell Precision Tower model downloads.
The Driver Automation Tool can be downloaded from Microsoft Technet – https://gallery.technet.microsoft.com/Driver-Tool-Automate-9ddcc010
If a new version of the driver download is available the script errors out when creating the driver package. The error is that an existing object exists. I have to manually remove the old driver package on SCCM and re-run the script. Is this consistent behavior? I have the option to clean up old packages checked.
Can you provide the steps to reproduce or a log file demonstrating this?
Hello, I have downloaded the the latest Driver Automation Tool (version 6.0.7). All is working fine. However the HP Driver Catalogue is not populating. Looking at the logs I see the following errors:
Error: Cannot validate argument on parameter ‘Source’. The argument is null or empty. Provide an argument that is not null or empty, and then try the command again
Error: You cannot call a method on a null-valued expression
Can you point me to the source it is referring to?
There have been a few changes in the CAB file. 6.0.8 should be out to date and will resolve this.
Well, grabbed the bull by the horns and went through the invoke-Driverdownload.ps1 script, and can see that you/it actually doesn’t use baseboard name, which it says in the documentation, but systemSKU. After adding that to my custom package, everything seems to work.
I’ve found an issue with selecting HP known models. It won’t select any of our Prodesk 600 G1,G2,G3s Desktop Minis. I believe this is because the logs shows that the imported name for the model is “ProDesk 600 Gx DM” and not the full name. Could this be addressed in a future release?
I am new to SCCM, I have the SCCM Console installed on my workstation, how come I cannot get this to open up on my machine. I am running it as the credentials with sccm permissions. Any help would be greatly appreciated. Thank you.
Where did Dell Latitide E7450 go?
Love the new update, except for one thing. I cannot seem to change the proxy config in the UI. Tried locally on my workstation (win 10 1709) and server (2016).
I would love to use your tool for MDT with automated BIOS downloads too.
Thank you for all your hard work, these changes look great! Can’t wait to use the updated version.
Hello, This is a great tool, but we found that the Lenovo driver packages that it downloads, do not download the latest drivers for said model. Is there a way to grab the latest drivers per model for Lenovo Systems?
That’s a Lenovo problem. They release new drivers but don’t update their catalog right away:
Guessing it’s by design, it’s not uncommon to see this, even from other manufacturers. Drivers release all of the time, catalog probably updates monthly or quarterly