Open dannz87 opened 4 years ago
In the text up here you don't see what i've seen.
chop out everything in the description other than (Models included:80fd,8125), I had that issue and it was weirding out everything until I trimmed the driver descriptions. It was good for a while but new problems.
I was trying the latest version of the Invoke-CMApplyDriverPackage.ps1 and was trying it in debug mode and the script seemed to do a false positive on a package that doesnt have the SKU in its description. At this moment i've tried to do a
write-host $DriverPackageInputArray " hello"
under the line with the comment "# Attempt to match for each SystemSKU item based on computer data input"Here's what i've got in the first place : 807c 8079 hello 80fd 8125 hello <-
When i've seen this i came back to look at the package matching with "8125" and it was just like that : "Hewlett-Packard ProBook 650 G2 Notebook PC Windows 10 x64 Drivers (Models included:80fd,8125)"
But WHY did it match with 8549? Believe me or not, but i've just edited the text by removing the last two characters of the description and writing it back by hand. It solved my problem. I've had 4 other packages with this problem. Now they all seem good and my detection works with the new script.
So its a solved ISSUE, but its good to know.