Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Apply driver package step fails (returns errorcode 1) - Invoke-CMApplyDriverPackage.ps1 v4.0.1 #15

Closed
Noizcontroller opened this issue Jul 28, 2020 · 4 comments

Comments

@Noizcontroller
Copy link

Noizcontroller commented Jul 28, 2020

Hi

I'm trying to setup MDM on our MCEM 2002 environment. I was able to download and create the driver packages with the Driver Automation tool but the part for the task sequence does not work. I'm using version 4.0.1 of the Invoke-CMApplyDriverPackage.ps1 script. I was able to setup the AdminService on our MCEM and it is working correctly. I was also able to configure a read-only user and I added the credentials in the task sequence.

image

When the "Apply driver package" step runs, the script is able to connect to the admin service and filter the correct driver package but then it suddenly stops with exit code 1 and without decent logging what went wrong. Any suggestions what could be wrong? The package with the drivers is distributed to the DP.

20200728_142802

Kind regards
Niels

@wiesel24
Copy link

wiesel24 commented Aug 4, 2020

Same Problem! I've tried it Multiple Times but no success

@ABitBA
Copy link

ABitBA commented Aug 14, 2020

Same Problem here - Error 1

@NickolajA
Copy link
Member

Have you seen our new docs on how to use v4 of the script?

https://msendpointmgr.com/modern-driver-management/

@Noizcontroller
Copy link
Author

It's now working with the latest version (4.0.2) of the script. Thx!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants