You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, using version 2.1.2 the script and 1.8.0 of ConfigMgrWebService it seems unable to find the bios package for this model
log is attached
I saw that the issue with models containing a "-" was fixed (issue #124 ) and indeed the script work as expected with a Latitude 3390 2-in-1 , and it doesn't look like it's missing the sku (as in issue #12 )
Unable to match computer model using detection method: SystemSKU (Latitude E5430 non-vPro)
Attempting to find a match for BIOS package: BIOS Update - Dell Latitude E5430-non-vPro (P01003D1)
copy pasting the log it seems to be an additinal - in the bios' package name for the 5430 , which is not present for the 3390 2-in-1
the Bios package were created using Driver Automation Toolkit (currently running version 6.3.1 but not sure on which version this specific package were created.
Allright after removing the additionnal - from the package name and corresponding folder name the script finds the correct bios package so that's great.
the issue seems to come from the Driver Automation Tool (or the way Dell named this particular model) as it's the only one that I see with an added - in the name
Hi, using version 2.1.2 the script and 1.8.0 of ConfigMgrWebService it seems unable to find the bios package for this model
log is attached
I saw that the issue with models containing a "-" was fixed (issue #124 ) and indeed the script work as expected with a Latitude 3390 2-in-1 , and it doesn't look like it's missing the sku (as in issue #12 )
Unable to match computer model using detection method: SystemSKU (Latitude E5430 non-vPro)
Attempting to find a match for BIOS package: BIOS Update - Dell Latitude E5430-non-vPro (P01003D1)
copy pasting the log it seems to be an additinal - in the bios' package name for the 5430 , which is not present for the 3390 2-in-1
the Bios package were created using Driver Automation Toolkit (currently running version 6.3.1 but not sure on which version this specific package were created.
ApplyBIOSPackage.log


The text was updated successfully, but these errors were encountered: