I noticed today that the Dynamically Apply Drivers steps in both our Bare Metal and Refresh task sequences are failing with Error Code 1. I can't put my finger on it but this may have something to do with us recently enabling Enhanced HTTP on our primary site server and all our distribution points. It is important to note we are not using HTTPS or PKI in our infrastructure.
Attached is the smsts.log file from a machine that just failed during Bare Metal imaging, as well as the ApplyDriverPackage.log from a machine failing this step. Specifically we're receiving the following errors in the ApplyDriverPackage.log:
The remote AdminService endpoint certificate is invalid according to the validation procedure. Error message: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. 12/28/2021 10:49:10 AM
Will attempt to set the current session to ignore self-signed certificates and retry AdminService endpoint connection 12/28/2021 10:49:10 AM
Failed to retrieve available package items from AdminService endpoint. Error message: The remote server returned an error: (404) Not Found. 12/28/2021 10:49:17 AM
An error occurred while calling AdminService for a list of available driver packages. Error message: Cannot validate argument on parameter 'Message'. The argument is null or empty. Provide an argument that is not null or empty, and then try the command again. 12/28/2021 10:49:17 AM
[ApplyDriverPackage]: Apply Driver Package process failed, please refer to previous error or warning messages 12/28/2021 10:49:17 AM
We're using version 4.1.3 of the Invoke-CMApplyDriverPackage.ps1 script and running SCCM CB 2107.
I've verified this step is failing on all of our models, for all driver packages. We have approximately 700 packages in production.
I've also tried running the script in DebugMode from one of the PCs in question. I don't get back any errors, just a return back to the PowerShell command line after about 10 seconds.
I noticed today that the Dynamically Apply Drivers steps in both our Bare Metal and Refresh task sequences are failing with Error Code 1. I can't put my finger on it but this may have something to do with us recently enabling Enhanced HTTP on our primary site server and all our distribution points. It is important to note we are not using HTTPS or PKI in our infrastructure.
Attached is the smsts.log file from a machine that just failed during Bare Metal imaging, as well as the ApplyDriverPackage.log from a machine failing this step. Specifically we're receiving the following errors in the ApplyDriverPackage.log:
We're using version 4.1.3 of the Invoke-CMApplyDriverPackage.ps1 script and running SCCM CB 2107.
I've verified this step is failing on all of our models, for all driver packages. We have approximately 700 packages in production.
I've also tried running the script in DebugMode from one of the PCs in question. I don't get back any errors, just a return back to the PowerShell command line after about 10 seconds.
Any suggestions? smsts.log ApplyDriverPackage.log