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
Using the latest version of the Lenovo Invoke scripts, we are seeing an issue where Apply BIOS step is trying to constantly re-apply the current version of the BIOS during OSD.
The script seems to think the BIOS needs updated when the version I have packaged is the same version that is installed. Having a quick look at logs, it seems like the dates don't match up.
Not sure if the issue is on Lenovo's end with poorly labeled BIOS version dates, or the way the script is reading the date.
The text was updated successfully, but these errors were encountered:
I've noticed that myself. Get-WmiObject -Class Win32_BIOS | Select-Object -Property SMBIOSBIOSVersion shows the correct version number on the models that I've checked, but the code used to detect updated versions compares the ReleaseDate property in WMI to the value set in the SCCM package description when the BIOS package is downloaded.
In the few that I've spot-checked in my environment, the date that gets set on the package doesn't even match up with what I find on Lenovo's website, though the version numbers still seem to match.
Using the latest version of the Lenovo Invoke scripts, we are seeing an issue where Apply BIOS step is trying to constantly re-apply the current version of the BIOS during OSD.
The script seems to think the BIOS needs updated when the version I have packaged is the same version that is installed. Having a quick look at logs, it seems like the dates don't match up.
Not sure if the issue is on Lenovo's end with poorly labeled BIOS version dates, or the way the script is reading the date.
The text was updated successfully, but these errors were encountered: