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


  • Moving source folders, Driver package comment field and custom drv. packages, Hyper-V drv.?
    1 Posts | Last post Wed 6:19 PM
    • 1.Tried moving some source folders because I one time set the wrong source folder in DrvAutoTool and then I also updated "Data Source" in properties of the specific drv packages that I´ve moved and updated the distribution points, but something seems to break because clients requiring driver package that was moved just stops at the download step "MODERN DRIVER MANAGEMENT". Then I deleted those packages and once again imported via your tool and now is is working? Any idea why that happened? and do I have to update/restart something when moving source folders when using Modern Driver Management?
      
      2. Does the Modern Driver Management match the Models with those in the "Properties"->"General" -> "Comment Field"?
      
      3. Any advice on steps to do when creating a Custom drv. package that needs to be used in Modern Driver Management? I need to prepare models for a new department far away and I have no possibility to test first only one device of each type at that department. What I am most worried about is the matching of models and related to my question no. 2 :-). Really appreciate any advice. And I know I need to update/check drv. in PE boot image.
      
      4. I need to create a custom package for Hyper-V test clients any advice is greatly appreciated. Do I just run the tool on an Hyper-V client and export drivers or any download source for Hyper-V driver packages out there?
      
      5. Any plans for adding Windows PE boot drv. administration to this great tool?
      
  • ThinkCentre E73+M73 Not in Win 10 64-bit list?, but Lenovo made SCCM package available
    2 Posts | Last post Wed 4:54 PM
    • Hi Maurice
      
      First thank you so much for sharing and development on this tool. Really makes life easier being an SCCM admin :-).
      
      I´ll soon have to make SCCM driver packages for Lenovo ThinkCentre E73+M73, but they are not in the models list of Lenovo Win 10 (not specific build), 64-bit.
      
      However Lenovo have SCCM packages ready for those models. Can you help?
      
      I am running ver. 6.1.7 of your tool.
      
      Wishlist:
      In the process log or other tab show status for each import model failed/Success and at what step it failed maybe + date and driver version. One time I tried import many models and one failed, but had to scroll to find it and it was only because I was looking at the process log live I saw one driver failed.
      
      One more question for all. The download speed of the driver packages from SCCM during Task Sequences takes really long time and slow speed. I know there are many smaller files, but anyway to speed up this step?
      
      I am using the OSD branchcache tools from 2Pint in my WinPE and task seq.
    • Sorry I´ve now realized that the missing E73+M73 is dependent on Lenovo updating the XML and not your tool :-).
      
      In addition to the feature failed/success of import then it could be nice to have the tool test automatically/manually if there are updated version to any of the already imported drivers maybe a column that show existing ver. and the new ver. if any.
      
      One more feature that I could use is choose to remove the driver drom all DP´s if a new version is imported, but keep the package and source for "fallback". This would free up space on the DP´s and then only distribute manually if fallback to previous driver ver. is needed.
  • Possible bug?
    1 Posts | Last post Tue 3:42 AM
    • I'm not sure if this is a bug with the script, but I'm finding that every once in a while - randomly, the folder\Temp\DriverPackCatalog.xml will randomly disappear and render the program unusable.  I'm not sure where this file is going, or if the program itself is wiping it out.
  • Error "Cannot determine the remote site server version"
    11 Posts | Last post Mon 11:12 PM
    • When I launch the tool, after a bunch of exporting and importing cmdlets, the text logging box says "Cannot determine the remote site server version. Cmdlets may not function as expected or may corrupt your site's configuration if they are a different version than your site." Happened with a version I downloaded last week as well as the brand new one I got today.
      
      I can go ahead and choose drivers etc. in the tool, but it fails to actually import them into ConfigMgr (driver pkg). Same error when run from my Win 10 workstation or from the CM primary server.
    • Hi Anne,
      
      Do you have remote WMI enabled on the site server, the configuration manager console installed locally and sufficient rights under your user profile to create packages?
      
      Maurice
    • Hi Anne/Maurice,
      
      I too have experienced this error, however I did get around it by creating a batch file which launches Powershell in bypass mode using the command on Page 20 in the 6.1.6 instructions which launches DriverAutomationTool.ps1 script.
      
      Obviously this error is a bit scary, Maurice would you be able to advise how to ensure that the application has determined the site server version? when I check the log I can see that it discovers the site code, DPs etc but couldn't find it determining the site version, I just need to verify this before I do anything further so as not to cause an issue per the warning.
      
      Regards 
      
      James
      
    • Feels like this might be the same as the "Issue replacing driver packages" question, i too get the "cannot determine site version" in my logs, but can import drivers without problem as long as there isnt a driverpack with the same name.
    • I have the same problem with "Cannot determine the remote site server version", launching DriverAutomationTool.exe locally on the SCCM 1810 server, DriverAutomationTool.ps1 is Updated 2019-02-22.
    • As do I
    • I think I ran into this when updating the Driver Automation tool from version to version.  I thought i would be slick and just unzip/overwrite the previous version with the new version zip from the gallery.  Worked for a while, but there was a time where the powershell stuff popped up some same errors like you have seen after one of the last few updates.  I blew away the extracted files, and extracted a fresh clean version, and setup all the necessary parameters again and things worked.  That worked for me.  
    • Me too. Any help will be appreciated. Also having issues getting web services diagnostics showing my packages and drivers. It says connected, with response time but won't show drivers or packages
    • As u/SomeoneHasMyNameAgain stated, I too was able to get 6.1.7 to launch without error by launching PS with execution policy bypass and then call the DriverAutomationTool.ps1.
      
      When the error occurs just by launching the exe (or the shortcut to the exe), and is ignored, driver downloads begin but typically fail creating the driver package, continue on and then eventually encounter a catastrophic failure and exits the download/package creation.
    • The PowerShell script contained within the download is not signed, hence running it with bypass will be required in some circumstances. The exe file should be run as administrator. In regards to the version checking, there was an update on the SCConfigMgr blog enforcing HTTPS, and due to the way in which the URL was called via HTTP, it caused issues. This has been updated in 6.1.7.
    • >Do you have remote WMI enabled on the site server, the configuration manager console installed locally and sufficient rights under your user profile to create packages?
      
      I do have all of these. As others suggest, when I launch the DriverAutomationTool.ps1 from PS after setting execution policy bypass, the cannot determine site version error goes away. That plus tweaking my path choices has gotten the driver import to work.
  • XML error when trying to import BIOS packages in 6.1.6
    3 Posts | Last post March 15, 2019
    • Hi Maurice,
      
      I get the following when I try to import BIOS packages (as well as driver) 
      
      <![LOG[======== Processing Dell OptiPlex 3040 Downloads ========]LOG]
      <![LOG[Info: Starting Download, extract and import processes for Dell model: OptiPlex 3040]LOG]
      <![LOG[Info: Setting Dell variables]LOG]
      <![LOG[Info: Dell System Model ID is : 06BB]LOG]
      <![LOG[Info: Using SCCM console BIOS package folder - SERVER:\Package\BIOS Packages\Dell]LOG]
      <![LOG[Info: Using SCCM console Driver package folder - SERVER:\Package\Driver Packages\Dell]LOG]
      <![LOG[======== OptiPlex 3040 BIOS PROCESSING STARTED ========]LOG]
      <![LOG[======== Downloading Dell XML Catalog  ========]LOG]
      <![LOG[Info: Downloading Dell XML catalog cabinet file from https://downloads.dell.com/catalog/CatalogPC.cab]LOG]
      <![LOG[Info: Expanding Dell XML catalog cabinet file: CatalogPC.cab]LOG]!
      <![LOG[======== Errors(s) Occurred ========]LOG]
      <![LOG[Error: Issues occured while extracting XML file]LOG]
      
      I have never seen this issue before, I tried an older version of the tool and it had the same issue. I can download drivers fine but not create a package like I have in the past. It doesn't matter if I select BIOS, Drivers or both. Any ideas?
    • Delete the cab file in the temp folder created where the tool is run from. That will force the cab to download again
    • Actually, the CatalogPC.CAB file on the Dell download site is broken.  Again.
      
      They uploaded a new one on 12/3 and the XML file in it is corrupt
  • surface
    1 Posts | Last post March 14, 2019
    • the surface driver catalog doesn't seem to be updated how can we do it?
  • Wrong package being downloaded
    3 Posts | Last post March 13, 2019
    • I just tried to download the Win 10 1809 driver package, but it started downloading the package for 1703.
      
      ======== Processing Lenovo ThinkPad X1 Carbon 6th Downloads ========	DriverAutomationTool	12/03/2019 10:37:52	7880 (0x1EC8)
      Info: Windows 10 build lookup required	DriverAutomationTool	12/03/2019 10:37:52	7880 (0x1EC8)
      Info: Windows 10 build 10.0.17763.1 and version 1809 identified for driver match	DriverAutomationTool	12/03/2019 10:37:52	7880 (0x1EC8)
      Info: Starting Download, extract and import processes for Lenovo model: ThinkPad X1 Carbon 6th	DriverAutomationTool	12/03/2019 10:37:52	7880 (0x1EC8)
      Info: Setting Lenovo variables	DriverAutomationTool	12/03/2019 10:37:52	7880 (0x1EC8)
      Info: Lenovo ThinkPad X1 Carbon 6th matching model type: 20KH	DriverAutomationTool	12/03/2019 10:37:53	7880 (0x1EC8)
      Info: Looking Up Lenovo ThinkPad X1 Carbon 6th URL For Windows version win10	DriverAutomationTool	12/03/2019 10:37:54	7880 (0x1EC8)
      Info: Searching for Lenovo ThinkPad X1 Carbon 6th exe file on https://support.lenovo.com/downloads/ds502283	DriverAutomationTool	12/03/2019 10:37:55	7880 (0x1EC8)
      Info: Passing through Windows version as 10	DriverAutomationTool	12/03/2019 10:37:55	7880 (0x1EC8)
      Info: Passing through Windows architecture as x64	DriverAutomationTool	12/03/2019 10:37:55	7880 (0x1EC8)
      Info: Driver package URL -  https://download.lenovo.com/pccbbs/mobiles/tp_x1carbon_mt20kg-20kh_w1064_1703_201809.exe	DriverAutomationTool	12/03/2019 10:38:02	7880 (0x1EC8)
      Info: Using SCCM console BIOS package folder - *\Package\BIOS Packages\Lenovo	DriverAutomationTool	12/03/2019 10:38:15	7880 (0x1EC8)
      Info: Using SCCM console Driver package folder - *\Package\Driver Packages\Lenovo	DriverAutomationTool	12/03/2019 10:38:15	7880 (0x1EC8)
      Info: Driver extract location set - \*\Drivers\DriverAutomationTool\Lenovo\ThinkPad X1 Carbon 6th\Windows10-1809-x64-201809	DriverAutomationTool	12/03/2019 10:38:15	7880 (0x1EC8)
    • Fixed it.
      
      Line 11203. 
      Replaced:
      $_ -match $OSVersion
      
      With:
      $_ -match "_$($OSVersion)_"
    • Added another fix.
      
      Line 11184.
      Replaced:
      if ($Link -like "*w$($OS)$($Architecture)_*" -or $Link -like "*w$($OS)_$($Architecture)*") {
      
      With:
      if ($Link -like "*w$($OS)$($Architecture)_*" -or $Link -like "*w$($OS)_$($Architecture)*" -or $Link -like "*win$($OS)$($Architecture)_*" -or $Link -like "*win$($OS)_$($Architecture)*") {
  • Delete Driver Cab folder after extraction
    1 Posts | Last post March 13, 2019
    • Any way to delete the "Driver Cab" folder after extraction?
      
      I set the following:
      <RemoveDriverSource>True</RemoveDriverSource>
      
      But the folder and the .exe file remains within it after the package has been created.
  • Config MGR Web Service Diags
    1 Posts | Last post March 13, 2019
    • Hi, When I connect to the WebService diagnostics I get the Status Code, Status Description and a Response Time but not the Driver Package Count, BIOS Package Count or the Returned Package List. I can't seem to make the webservice list the CM package too. Any  help?
  • Issue with drivers
    2 Posts | Last post March 12, 2019
    • Hi,
      
      I am having a issue with a couple of remote sites.  They are not getting the drivers installed, when looking in the Driver logs under CCM we are getting the following errors.
      
      ===== SCConfigMgr Invoke-CMApplyDriverPackage Version 2.1.6 ====	ApplyDriverPackage	1392 (0x0570)
      Driver download package process initiated	ApplyDriverPackage	1392 (0x0570)
      Manufacturer determined as: Dell	ApplyDriverPackage		1392 (0x0570)
      Computer model determined as: OptiPlex 7060	ApplyDriverPackage	1392 (0x0570)
      Computer SKU determined as: 085A	ApplyDriverPackage		1392 (0x0570)
      Fallback SKU determined as: 085A	ApplyDriverPackage		1392 (0x0570)
      An error occurred while calling ConfigMgr WebService for a list of available packages. Error message at line 586: There is an error in XML document (1, 2385).	ApplyDriverPackage	1392 (0x0570)
      
      The bios installs without any issues.   I have redistributed the package and drivers package but it has made no difference.    
      
      Has anybody seen this before?
    • Downgraded the ConfigMgr WebService from version 1.7 back to 1.3 and everything is working as it should now.   
      
      When we ran the following powershell command 
      
      {
      		$WebService = New-WebServiceProxy -Uri $URI -ErrorAction Stop
      	}
      	catch [System.Exception] {
      		Write-CMLogEntry -Value "Unable to establish a connection to ConfigMgr WebService. Error message at line $($_.InvocationInfo.ScriptLineNumber): $($_.Exception.Message)" -Severity 3; exit 1
      	}
      # Call web service for a list of packages
      	try {
      		$Packages = $WebService.GetCMPackage($SecretKey, $Filter)
      		Write-CMLogEntry -Value "Retrieved a total of $(($Packages | Measure-Object).Count) driver packages from web service" -Severity 1
      	}
      	catch [System.Exception] {
      		Write-CMLogEntry -Value "An error occurred while calling ConfigMgr WebService for a list of available packages. Error message at line $($_.InvocationInfo.ScriptLineNumber): $($_.Exception.Message)" -Severity 3; exit 2
      
      It was giving us errors sometimes, sometimes it would return the correct info.
1 - 10 of 418 Items