search

MSEndpointMgr / ConfigMgr

Microsoft Endpoint Configuration Manager scripts and tools
629 stars 282 forks source link

Apply Drivers: #243

Open carlosalbaidiada opened 4 years ago

carlosalbaidiada commented 4 years ago

Hi,

I'm running into and issue applying drivers.

DAT is working, packages are distributed. Web Service is OK

But when I invoke the PS1 script for driver applying I get this error message ... [WebService]: Starting ConfigMgr WebService phase ApplyDriverPackage 7/3/2020 10:33:30 AM 8656 (0x21D0)

Thanks for your support ¡¡¡¡

carlosalbaidiada commented 4 years ago

By the way, as additional info.

I had working the old version of the script 2.2.3, using the last one is when crashed

carlosalbaidiada commented 4 years ago

Hi,

I deleted all old packages and download form scratch.

Now I get this error message from a bare metal deployment under WinPE, model ProBook 640 G5

[ApplyDriverPackage]: Apply Driver Package process initiated ApplyDriverPackage 06/07/2020 11:00:24 2388 (0x0954)

cincydash commented 3 years ago

~I'm having the same issue with the 3.0.4 script, it fails with HPs, works fine with Dell. If I use the 2.2.7 script, it works fine with both vendors. I guess I'm sticking with the v2.2.7 script until v3 gets fixed.~

Figured it out. Two changes I made seemed to fix the issue:

1) Changed -Filter from "Driver" to "Drivers"...since this still worked on Dell, I doubt this was the fix, but, just stating I changed this step, as it was modified in v3.0.3

2) https://github.com/MSEndpointMgr/ConfigMgr/issues/240 it appears HP drivers need explicit declaration of OS version. Added the -Targetosversion "18363" flag

carlosalbaidiada commented 3 years ago

Thank you so much for your answer ¡¡¡

I'll give a try and let you know

merlinfrombelgium commented 3 years ago

Please switch to using the scripts from this repository instead: https://github.com/MSEndpointMgr/ModernDriverManagement The legacy script is updated to v3.0.6

Please test with v4.0.1 and let us know how you go. It does require the AdminService so you need to have a current version of CM. And you need these instructions, as the documentatios has not yet been updated:

Changes in this version require a different set of parameters for the script to run. Should look something like Invoke-CMApplyDriverPackage.ps1 -Baremetal -Endpoint your.servername.here -TargetOSVersion 1909 -OSVersionFallback

Also, try the script from a device of the model you're having issues with and use the -DebugMode parameter. It's really helpful to see which drivers you'd get back, without having to wait for the Task Sequence to reach that step and fail.