2008-09-20

ERROR: PXE Cert not set. This might cause client failures.

ERROR: PXE Cert not set. This might cause client failures.
WARNING: _SMSTSSiteSigningCertificate Not Set. This might cause client failures in native mode.
WARNING: _SMSTSRootCACerts Not Set. This might cause client failures in native mode.
WARNING: _SMSTSCertStoreName Not Set. This might cause client failures in native mode.
WARNING: _SMSTSCertSelection Not Set. This might cause client failures in native mode.

The PXE Cert Not Set message in the SMSPXE.log may be corrected by either resetting the expiration date (the typical forum response) or by checking the CA certificate.

Try opening the Certificates | PXE node in SCCM. Find the certificate that is not "blocked" and right-click to Open it. Check the status of the CA Certificate. I found that it was "Not Trusted" in my environment. When I clicked the Install button and selected the Trusted Root CA Authorities, the certificate was then "valid" when I reopened the certificate. My SMSPXE.log no longer reflected that the certificate was not set.

1 comment:

averagejoe_70 said...

what do you mean by..Try opening the Certificates | PXE node in SCCM. Do you mean to go to IIS on the PXE service point and look at the certificates?