PENDING SCCM 1511 Upgrade errors

[meakjoe]

Hello all,

We're attempting to upgrade out SCCM 1511 server to a newer version to support Windows 10 rollout this summer and we seem to be stuck trying to do the In Console updates.

We first tried going to 1610 and although that seemed to be going smoothly, it eventually came up with an Update failed, with the error code 0x80004005. After that happened we weren't able to reattempt the install, or start anything previous updates. It all seemed to stop working and we couldn't even open the console.

We then restored the VM back to a working version prior to the update, shut it down and have recreated the VM and Data from the previous day when it was all working and prior to the update, on another host to test and hopefully get working.

We attempted to do the update to 1606 this morning and that didn't work either. The CMUpdateLog showed the following, and it keeps retrying but always comes up with the same errors....

ERROR: Failed to find ManifestVersion node
Failed to verify redist file for update C:\Program Files\Microsoft Configuration Manager\CMUStaging\0D256560-ED2C-45B5-8D75-4D38AB3F758C\redist\ConfigMgr.Manifest.cab
ERROR: Failed to process configuration manager update.

We also get these errors in the dmpdownloader logs...

WARNING: Failed to obtain easy setup payload. Retry in the next polling cycle

Failed to verify that the last certificate in file 'C:\Program Files\Microsoft Configuration Manager\AdminUIContentPayload\ConfigMgr.AdminUIContent.AUC' is MS signed.
WARNING: The downloaded AdminUI content cab signature could not be verified.

Which led us to this post which we attempted but didn't work for us unfortunately... https://social.technet.microsoft.co...e-from-1511-to-1602?forum=ConfigMgrDeployment

We've also tried a manual install through the splash.hta but it says something like command line install is not available and fails.

If anyone has had the same issue or has suggestions for us to try it would be really appreciated as we really are stuck between a rock and a hard place.

Thank you!

 

[Prajwal Desai]

We first tried going to 1610 and although that seemed to be going smoothly, it eventually came up with an Update failed, with the error code 0x80004005. After that happened we weren't able to reattempt the install, or start anything previous updates. It all seemed to stop working and we couldn't even open the console.

Simple question, for the above error why did you restore the VM ?. Didn't you check the monitoring node > update installation status to see what went wrong ?. Can you upload dmpdownloader.log file ?.

 

[Prajwal Desai]

Alright you mentioned that you couldn't even open console which is a strange issue.

 

[meakjoe]

Hi there,

Please find the log attached. Yes the console issue is very odd, we could still see things happening through the logs but could not get on. We wonder if its a case that the upgrade files from Microsoft are too old now and the Signatures/Certificates have expired?

Thank you.