maurice-daly / DriverAutomationTool

Home of the Driver Automation Tool
https://www.msendpointmgr.com
BSD 2-Clause "Simplified" License
382 stars 114 forks source link

Issues with driver packages imported with version 7.0.4 #351

Closed mherbert18 closed 2 years ago

mherbert18 commented 2 years ago

I recently updated DAT to be version 7.0.4 and I had imported several Dell Windows 10 drivers as well as Windows 11 drivers. When using the Invoke-CMApplyDriverPackage.ps1 in a dynamically apply drivers task sequence step, the step is failing now for every model I try to deploy using -BareMetal deployment options. I updated the script to be the latest version, 4.2.0 from 4.1.3, and used the new parameters to differentiate between Windows 10 and Windows 11 and it didn't work. I then reverted back to the 4.1.3 version and got rid of the additional parameters and any duplicate Win 11 driver packages for a specific model and I am still not able to get the dynamically apply drivers step to work. I've tried downloading and manually importing driver packages into SCCM directly from Dell, deleting and recreating script packages, deleting and retrying to import driver packages via DAT...nothing is working. It was working perfectly fine before I updated DAT and imported new drivers. I also cannot find any logs or get the script to run in debug mode. It also appears that DAT version 7.0.4 is setting driver versions to 5420 for the A08 and A12 driver packs for the Latitude 5420 when importing into SCCM, I have tried to change this manually to the correct driver version but that doesn't seem to change any outcomes. Regardless of the changes I make, I continually get error code 0x00000001.

lassekarlsen commented 2 years ago

Changes on dell driverpackage metadata(?) results in DriverPackage.wim notcontaining or containing wrong data on select models

DriverPackageVersion is replaced with Model Example : image

Current models I've see this on is

DAT v7.0.4 Invoke-CMApplyDriverPackage.ps1 v4.2.0

I've fixed the issue by manully mounting the wim and adding the driverpack files. Then updating the CMPackage

mherbert18 commented 2 years ago

Thank you, that was definitely part of it. It is working now!