search

MSEndpointMgr / ModernDriverManagement

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

Apply Driver Pack process failed. #21

Open terraj01 opened 4 years ago

terraj01 commented 4 years ago

i am running invoke-cmapplydriverpackage.ps1 4.0.2

invoke-cmapplydriverpackage.ps1 -PreCache -Endpoint "pri02.xxx.net" -TargetOSVersion "2004"

the applydriverpackage.log all looks successful it reads the service account name from the TS variable but it failed to apply driver package process failed, please refer to previous error or warning. i am not seeing any errors in the log so i am not sure what is failing.

AlexanderZach commented 4 years ago

Hello,

I'm facing the exact same issue.

Additional infos:

MECM version: 1910 inc. all hotfixes and rollups (Customer wants to wait for MECM 2006 Slow Ring)

DAT 6.4.8 Hotfix 3

DAT was previously configured and tested successfully using the legacy Webservice and changed to use the admin service (according to your and the Microsoft docs) & Invoke-Script Version 4.0.2

TS command: invoke-cmapplydriverpackage.ps1 -BareMetal -Endpoint "xxx.xxx.xx" -TargetOSVersion 1909 (it made no difference putting the OS version in quotes or not)

SMSTS part:

smstslog

ApplyDriverPackage.Log:

ApplyDriverPackageLogPart1 ApplyDriverPackageLogPart2

Testing the driver installation in debug mode on a different client also failed with the same error message!

As an alternative we also tested the legacy webservice step and the legacy scripts 3.0.4 (which was used before switching to version 4) - same ERROR Test version 3.0.8 - same ERROR

We tested two different devices and none of them was working:

Lenovo T590 Lenovo T15 Gen 1

best regards Alex

terraj01 commented 4 years ago

I guess I’m glad I am not the only one seeing this.

NickolajA commented 4 years ago

Could you verify that all of your packages have at least a single SKU (4 chars) in the comments property? E.g. (Models included:1234)

CarValScott commented 4 years ago

Yes mine all have the SKU's listed in the comments. With running the debug scripts, I do find that the Dell Latitudes 5310's also gets the 5300 driver package. When deleting the 5300 drive package the debug script see's only one, but we still get the errors as listed above.

here is the WinPE log file.

ts2

Here is the debug log.

ts1

nodiaque commented 4 years ago

Verify something, is there space somewhere in the skus in the package? I had a similar problem, my script would just end nowhere no error. I had a package that had a space in the comment and because of that, it would kill the process. That might trigger a mistmatch here. Maybe try recreate the package with the latest driver automation tool?