Repository navigation
Dell Pro Max 16 Plus MB16250 #343
Description
Activity
I pulled the ApplyDriverPackage.log file and it looks like it isn't finding a driver match so it goes to failover and still doesn't find a driver even though one is there. Not sure where to go from here.
Would you be able to share:
- the command line in your task sequence step that calls the drive management script
- the ApplyDriverPackage.log
We use that model in our environment and the package is applied correctly
This is from my task sequence. It has been working for the last 2 years or so. Just as an FYI, when I look at the properties for the driver, there is no "Manufacturer" property like other make/model drivers.
Invoke-CMApplyDriverPackage.ps1 -BareMetal -Endpoint 'cssm-mecm01.win.udel.edu' -TargetOSName 'Windows 11' -TargetOSVersion '24H2' -OSVersionFallbackAh; looks like the CM package for that driver may be mal-formed then.
Here's what ours looks like:
Here's what's in the comment box so you can copy & paste:
Models included: 0D12
Reacted by Rob SpottsHere's mine...I guess I'm not understanding the issue. Thanks for looking into this!!
So, if a systemsku is detected, it matches on that before model. Per your log, it's pulling the systemsku as 0E86:
On your package for the MB16250 modify the comment to:
Models included: 0D12, 0E86That should solve the detection issue. Not sure why that SKU isn't listed with that model yet.
Reacted by Rob Spotts
@maurice-daly would be nice to have a option to report stuff for like missing baseboard directly in the right click menu maybe this could allow some kind of reactive community contributionThank you for all your help! Testing now after the adjustment.
Update: It is now working! I'll be more mindful next time.
I'm running the latest Driver Automation Tool and Invoke-CMApplyDriverPackage.ps1 script. I'm running into this issue with the Dell Pro Max 16 Plus. I've update the driver package. I've looked at the smsts.log file and it looks like a try/catch error...not sure where. Any suggestions on how to troubleshoot this issue?