search

MSEndpointMgr / ConfigMgr

Microsoft Endpoint Configuration Manager scripts and tools
634 stars 281 forks source link

HP EliteBook 840 G5 #182

Open simulacra75 opened 5 years ago

simulacra75 commented 5 years ago

Downloaded the 1903 versions of the drivers with Driver Automation Tool. Attempt to use an 1809 Task Sequence, would have expected the TS to use the 1903 drivers (even though they're newer than the OS been laid down), it doesn't work. ApplyDriverPackage.log seems to indicate that there's detection of "HP EliteBook 850 G5" and "HP EliteBook 840 G5" and ends up using neither package and TS errs out.

This did not happen when installing an 1809 TS with an Elite X2, it installed the 1903 drivers just fine. Anyone else seeing this?

MichaelGibsonAltrad commented 4 years ago

I've noticed this on a couple of models where it detects the SKU and there are multiple packages. It then searches the description looking for the specific model, finds one but only searches for the Windows version e.g. 1903 and if it doesn't find that in the package name it skips past it. I've amended the detection to search for "Windows 10" if it fails searching for the specific OS version number and this fixed it.

king-matthew-g commented 4 years ago

The Model detection step actually stripped away non-matching versions and not non-matching models. I've proposed a fix in a different issue but am reposting it here to try and kill two birds with one stone.

image