Open snarkDADMin opened 1 year ago
After several hours of trying another boot image, etc. I looked closer at the logs and realized I should look at the package ID it was trying to pull, and that the Driver Automation Tool had created a generic package named "Drivers - Dell - Windows 11 x64"
I am not sure if this is a bug with the Driver Automation Tool or with Modern Driver Management, or both, so I am leaving this open as a possible bug due to incorrectly matching. I will also note that the DAT packages I downloaded the other day did not put "Optiplex" in the package name before the model number, only "Dell 5090", but that is likely something I need to report on that repo. I am providing that tidbit here in case it helps on this side.
We have updated the Driver Automation Tool and I have grabbed the latest version of the ModernDriverManagement script from this repo. We have recently updated our ADK and Windows PE to the latest version (10.0.2262.1, Windows 11 ADK) and drivers are failing to properly detect and deploy. I have the Target OS parameter set and the latest copy of the script is on the distribution point.
The way we currently image PCs, we cannot image any PCs until this is resolved. I am currently trying to downgrade our boot image to a Windows 10 ADK version, but I wanted to post this and try to get some help.
I have attached a sanitized version of the ApplyDriverPackage.log file, and below are the arguments being used by OSD on the script:
-BareMetal -Endpoint 'configmgr.redacted.redacted' -TargetOSName 'Windows 10' -TargetOSVersion '21H2'
It looks like there may be some conflict between the Windows PE being built against the Windows 11 codebase, and looking for Windows 10 drivers. You can see that the log file reports that Windows 10 is the target OS, but it's got Windows 11 x64 in the detection methods line right before the error.
`` ApplyDriverPackage.log