In the case of the T460, the download included 09 of the embedded controller software, where as the T460S contained version 11. You might ask then if that is the case then surely a single package would work for both, and where as you might be correct we found that the T460s BIOS download in this instance contained a subtle difference in the sub version relating to the embedded controller was different. If multiple packages are found, we then try to match on the name of the package against the product name (obtained from Get-WmiObject -Class Win32_ComputerSystemProduct | Select-Object -ExpandProperty Version value). The reason for this is clear if we take the example of the ThinkPad T460 and the T460S, both similar but separately named models so you would imagine that the machines would distinct in their model type codes, however this is not the case To cater for Lenovo systems we have updated our BIOS Package Detection script so if you are already using this, please update the script.īIOS Package Detection Script (At least version 1.0.4):Īs you can see there are 10 distinct product type values which should provide a match for this package, so during the Invoke-CMDownloadBIOSPackage.ps1 stage we obtain a full list of packages which contain a match based on the first four digits of the Get-WmiObject -Class Win32_ComputerSystem | Select-Object -ExpandProperty Model value, which should coincide with the model types.
The same process used in the original post linked at the top of this post is used, the process uses a web service and WMI queries in PowerShell to match available packages. Note that I am not going to step through the entire process in this post, so please refer to the original post for set up instructions. So here is the first of which, the update being for Lenovo systems:Īs my current environment is virtually all Dell, I had to reach out to come members of the ConfigMgr community to perform tests of modified scripts so I would like to thank Zeng Yinghua (aka Sandy – Eugeny Korneev ( and Lauri Kurvinen ( ) for putting in long hours of testing on their Lenovo devices. Following the post we had numerous requests to apply the same logic for other manufacturers.
0 kommentar(er)
