I recently did a Site Restore of a ConfigMgr 1810 Site on to a new System using Configuration Manager Site Recovery. After finishing the restore, the PXE Component (new PXE Responder without WDS) seemed to be broken and new PXE-boot attempts ended up with the following lines in SMSPXE.log.
Failed to create certificate store from encoded certificate. Verify the provided Certificate was provisioned correctly. . An error occurred during encode or decode operation. (Error: 80092002; Source: Windows)
Failed to create certificate store from encoded certificate. Verify the provided Certificate was provisioned correctly. . An error occurred during encode or decode operation. (Error: 80092002; Source: Windows)
PXE::MP::GetMPListAndConnectionInfo failed; 0x80092002
PXE::MP::IsKnownMachine failed; 0x80092002
I quickly stumbled over the Knowledge Base Article called “ConfigMgr PXE does not work because a self-signed certificate is not created“. However, after performing all the listed steps, the error above remained.
What solved it for me, was regenerating the Distribution Point Certificate. For this to happen, you can adjust the expiration date of the self-signed Certificate to a newer date. In this case here, I changed the Year from 2115 to 2116.
You can verify the regeneration of the Certificate by opening the Certificates Node in the Administration Workspace. Here you find a new Distribution Point Certificate with the specified end date. The old Certificate should be blocked as seen below.
A new attempt to PXE boot worked on the first try without the previous errors in SMSPXE.log.
Great post. Thank you sharing knowledge.
Maybe it will be useful for someone, once new certificate is created you might face issue with you boot image now.
error: installBootFilesForImage failed 0x80004005
To solve it delete the boot image from DP first manually by deleting the content from:
RemoteInstall\SMSImages\
Than remove if from DP in SCCM console and resend after few minutes.
thanks for this post it helped me fix my issue!
Worked like a charm! Thank you for posting this.
Thanks for the post. I spent 2 days trying to resolve the issue in our server and recreate the cert worked like a charm
I spent several days trying to solve PXE boot issues after SCCM migration.. And now I see the “2 clicks” fix here…
God save Simon Dettling! 😀
Thanx mate! Just helped me solve a problem with my PXE boot failure!
Hello,
I have this eror in our SMSTS.log file. However, my DP logs are fine and PXE works. When I ceate a required deployment to run my Task Sequence PXE works, the OS is installed and the drivers are installed. The next step is to install the Config Mgr client, then finally the software. My machines restart at the end of the OS install and boot into Windows without continuing with the Task Sequence. However, if I manually run the Task Sequence using PXE the Task Sequence succeeds.
Danke Simon, hat mir heute geholfen!
Grüße
André