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

Getting error code 1 when running Invoke-CMDownloadBIOSPackage.ps1 #16

Open
RonDLS opened this issue May 4, 2022 · 3 comments
Open

Comments

@RonDLS
Copy link

RonDLS commented May 4, 2022

We're getting exit code 1 when running the Invoke-CMDownloadBIOSPackage.ps1 with the parameters -BIOSUpdate -Endpoint "endpointname". Any suggestions or ideas?

@jbudd0649
Copy link

Did you find a solution to your issue? I am getting the same error, but I am using -BareMetal and -Endpoint "endpointname" instead of -BIOSUpdate. I have looked through the SMSTSlog and the ApplyBIOSPackage log and don't see any other errors.

@jbudd0649
Copy link

jbudd0649 commented May 31, 2023

Did you find a solution to your issue? I am getting the same error, but I am using -BareMetal and -Endpoint "endpointname" instead of -BIOSUpdate. I have looked through the SMSTSlog and the ApplyBIOSPackage log and don't see any other errors.

I fixed my issue. My problem ended up being the Task Sequence Variables for the MDMUserName and MDMPassword. I had the variables in the same step as my Drivers, which was further down in the TS then my BIOS step. I moved the Variable up high in the TS above both the BIOS step and the Driver step and all is right in the world. Thanks

@akosipatpi
Copy link

Hi sorry to open this thread. I added the TS variable MDM accounts and it worked during my testing. But when I deployed the task sequence to prod, been getting the same error and I ran out of idea on how to fix this.

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

3 participants