MSEndpointMgr / ConfigMgr

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

Multiple packages matched with different SystemSKU #277

Open tonycontorno opened 4 years ago

tonycontorno commented 4 years ago

Hello,

My apologies if this has already been brought up, but I am having an issue regarding Microsoft Surface 4 devices. I am receiving multiple matches despite the fact that the descriptions clearly don't have the Surface_Pro_4 listing in the description field. I am at a bit of a loss as to why that is happening. If anyone else has seen this behavior before and how to fix it, I would greatly appreciate some guidance.

Currently on 4.0.3 of the MDM solution, and 2002 for MECM.

image

image

tonycontorno commented 4 years ago

To add to it, I tried manually recreate one of the packages to see if maybe it was something odd with one of the automated packages, but it was returned as a possible driver package again.

simulacra75 commented 4 years ago

Seeing the same behaviour here when using script versions 3.08 and 3.09 with DAT ver. 6.4. 9

shaikh441 commented 4 years ago

Currently using latest MDM and PS script (SCCM 2004) and seeing exact same thing. OS version being deployed is 1809

shaikh441 commented 3 years ago

Any potential fixes to this? We are having to revert to the legacy driver packages for Surface devices as the latest tool/script will not work with Surface Pro 6 and 7 (not tested on earlier models yet)

Ar5had07 commented 3 years ago

Yeah it's been a known issue for a very long time, I am using an old script that still works but doesn't work with WIM & 7-Zip Compression and doesn't work over CMG. Works internally fine though. The script that works is version 3.04. So I have 2 scripts in my TS, 1 for all Surfaces and the other for the rest. I have tweeted at them, but no replies.

shaikh441 commented 3 years ago

Thanks for letting me know. I am currently putting in a wmi query to bypass the Surfaces when applying MDM drivers and use legacy driver packages for all surface devices only for now.

azulol commented 3 years ago

We have the same problem with script version 3.0.4. on the Lenovo T14s 20UJ (AMD Modell).

Has someone solved the issue?

Right now we are working with the wmi query and a driver package for this Modell to solve it for now.