MSEndpointMgr / ModernDriverManagement

Official repo of Modern Driver Management from MSEndpointMgr.com
https://www.msendpointmgr.com
MIT License
133 stars 80 forks source link

MDM - Multiple packages have been matched but with different SystemSKU #228

Open johnediri opened 1 year ago

johnediri commented 1 year ago

We have lately been mass deploying HP 840 G8 Windows 10 21H2 builds. MDM has been used to create the Driver package and all is well in that front. when we run a deployment, the task sequence gets to MDM detection stage and then errors with the below

_**- WARNING: Computer detection method is currently 'SystemSKU', and multiple packages have been matched but with different SystemSKU value

looking further up in the script we see the below

[DriverPackage:HBL004B3]: Processing driver package with 4 detection methods: Drivers - HP EliteBook 840 G8 Notebook PC - Windows 10 21H2 x64

and then we see another detection for a totally incorrect model

[DriverPackage:HBL0050F]: Processing driver package with 4 detection methods: Drivers - HP ZBook Firefly 14 inch G8 Mobile Workstation PC - Windows 10 21H2 x64

we have removed the HP ZBook Firefly 14 inch G8 Mobile Workstation PC - Windows 10 21H2 x64 for now and the HP 840G8 are now building correctly.

we are using version 4.2.0 - (2022-03-05) of the Invoke-CMApplyDriverPackage420.ps1 script (we are aware that there is a slightly newer version and will be updating to that shortly) but was just wondering if anyone in the community has come across this?

Note : no other models are effected by this so far

ApplyDriverPackage.log

stephannn commented 1 year ago

I think your problem is that you also have Windows 11 packages in your repository and if I remember correctly the old version does not like it without any modifications. You could try change line 1508 from: if ($DriverPackageItem.PackageName -match "^.*Windows.*(?<OSName>(10)).*") { to: if ($DriverPackageItem.PackageName -match "^.*Windows.*(?<OSName>(10|11)).*") {