search

maurice-daly / DriverAutomationTool

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

Lenovo BIOS Update - New-CMPackage fails #434

Open U3mi opened 1 year ago

U3mi commented 1 year ago

Hey,

I'm facing an issue with creating the BIOS Update packages and it shows me the following:

New-CMPackage : Validation of input parameters failed. Cannot continue. At line:19906 char:15

Set-CMPackage : No object corresponds to the specified parameters. At line:19909 char:16

Do you have an idea how this can be fixed?

BR Tim

Muri-dk commented 1 year ago

I have same issue

aropxt commented 1 year ago

Have the same issue here.

Specify a valid drive and folder path by using the :\ format. Or, specify a valid UNC path by using the \\ format. Specify a valid drive and folder path by using the :\ format. Or, specify a valid UNC path by using the \\ format. New-CMPackage : Validation of input parameters failed. Cannot continue. At line:19975 char:15

Set-CMPackage : No object corresponds to the specified parameters. At line:19978 char:16

Move-CMObject : Cannot bind argument to parameter 'ObjectId' because it is null. At line:19985 char:76

aropxt commented 1 year ago

Looks like the Path always have a normal slash on Lenovo BIOS and that could be the reason why the package always fail to create. The version come from Lenovo as Version/Subversion and the script goes on with it to generate the Paths. Example from the log: BIOS update directory set to ...Lenovo\ThinkPad T15 Gen 2 Type 20W4 20W5\BIOS\1.54/1.04\

MrMortensen commented 1 year ago

I have the same problem. I think it is because the T15 Gen 2 comes with 2 different chipset. And as aropxt writes, DAT tries to create a folder with a "/" which create a subfolder. So "1.54/1.04" becomes "1.54\1.04". I believe it takes the version from this file: https://download.lenovo.com/pccbbs/mobiles/n34uj21w_2_.xml. And If you look in the readme file for the BIOS: https://download.lenovo.com/pccbbs/mobiles/n34uj21w.txt You can see the version for the different chipset: Version 1.54 (BIOS ID:N34ET for Microchip EC) 1.04 (BIOS ID:N3WET for Nuvoton EC) I would be nice i DAT could handle it in some way. Does DAT check on release date or version? If it is release date, it should be easy to fix. /Morten

its-jaa commented 1 year ago

+1

aropxt commented 1 year ago

Hi all, Agree with you MrMortensen, I have tested with another laptop model and the version of the BIOS was diff from "1.54/1.04", it was like "1.54/1.54" and it did the package without any issue at all. So it need to be something about this particular Model/Version or that "0" is messing around with the underlying code.

MrMortensen commented 1 year ago

I can see the following models uses the same BIOS: ThinkPad P14s Gen 2i, 20VX,20VY ThinkPad T14 Gen 2i (Intel), 20W0,20W1 ThinkPad T15 Gen 2i (Intel), 20W4,20W5

TLawsonLenovo commented 2 months ago

From another comment.

I reviewed the Lenovo catalog with our catalog team and we have changed the forward slash '/' character to be an an underscore '_' in case this is contributing to this issue.