Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dell latitude e5430 non-vPro model not detected by Invoke-CMDownloadBIOSPackage 2.1.2.1 #178

Open
ersatyle opened this issue Aug 13, 2019 · 1 comment

Comments

@ersatyle
Copy link

ersatyle commented Aug 13, 2019

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
image
image

image

@ersatyle
Copy link
Author

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

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant