jasava.blogg.se

Unfortunately, the ones I've listed are the only ones I needed to care about.

Save this in the same folder that contains the two detect folders.ġ Function Start-ProcessGetStreams 87 88 $LastScriptRun = Get-Date -Format "yyyy-MM-dd HH:mm:ss" 89 90 New-Item -Path "HKLM:\Software\Inventory\Hardware\ThunderboltFirmware" -Force | Out-Null 91 92 New-ItemProperty -Path "HKLM:\Software\Inventory\Hardware\ThunderboltFirmware" -Name "NvmVersion" -Value $nvmVersion -Force | Out-Null 93 New-ItemProperty -Path "HKLM:\Software\Inventory\Hardware\ThunderboltFirmware" -Name "LastScriptRun" -Value $LastScriptRun -Force | Out-Null 94 New-ItemProperty -Path "HKLM:\Software\Inventory\Hardware\ThunderboltFirmware" -Name "Status" -Value $status -Force | Out-Null 95 96 Write-Output "NvmVersion = $nvmVersion | Status = $status"Īs you can probably tell, this script will look at the system type of the host system and then run the appropriate Detection method for it. While useful for checking one laptop at a time, we'll want to build a better method to run this across our fleet.

This is only here for those who don't want to go through the hassle of finding them in your firmware update extractions.ĭepending on the model laptop, you can now run one or the other of the detection binaries to get your firmware version, as shown below: Important: Please please please validate the digital signature on all of the files inside the Zip and don't randomly trust downloaded binaries from a blog.

If you'd rather not go hunting for them, you can download them from me here. You're looking for one that has detect1909ur.exe and one that has detect2008.exe. Below, I'll share the steps you can use to gather this information yourself.įirst, you'll need to gather up the DETECT folders from the downloaded Firmware updates (after you extract them).

Through trial and error, I found that although there are dozens of different firmware updates, the detection binaries from just two of them covered my entire fleet. The only solution I found in the forums was to collect the data using the firmware update itself. When Lenovo announced HT508988 back in late 2019, I found there was no built-in method to get the firmware version on impacted Lenovo models using traditional hardware inventory or WMI.