PXE Boot Task Sequence Failing

[Maso]

Hi

 

Have set up a new SCCM 2012 R2 installation to replace a test installation we had been running successfully.

 

When trying to deploy a task sequence to a client, the PXE boot fails with error:-

 

"pxe-e53 no boot filename found"

 

and the SMSPXE.log has the following:-

 

cannot connect with winhttp; 80072ee5 SMSPXE 10/09/2014 15:01:37 4324 (0x10E4)
Failed to get information for MP: . 80072ee5. SMSPXE 10/09/2014 15:01:37 4324 (0x10E4)
PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 10/09/2014 15:01:37 4324 (0x10E4)
PXE::MP_LookupDevice failed; 0x80004005 SMSPXE 10/09/2014 15:01:37 4324 (0x10E4)
cannot connect with winhttp; 80072ee5 SMSPXE 10/09/2014 15:01:37 4324 (0x10E4)
Failed to get information for MP: . 80072ee5. SMSPXE 10/09/2014 15:01:37 4324 (0x10E4)
PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 10/09/2014 15:01:37 4324 (0x10E4)
PXE::MP_ReportStatus failed; 0x80004005 SMSPXE 10/09/2014 15:01:37 4324 (0x10E4)
PXE Provider failed to process message. 
Unspecified error (Error: 80004005; Source: Windows) SMSPXE 10/09/2014 15:01:37 4324 (0x10E4)

We are using HTTPS, and I've confirmed that the certificates are correct, both were generated from our own internal CA.

 

I've tried searching this error, the only thing I've found that is similar was when users hadn't added the certificates to either the SCCM or IIS.

 

Would appreciate any suggestions / pointers on how best to diagnose what is going on here as I'm out of ideas.

Thanks

Paul

[Peter van der Woude]

Did you configure the distiribution point certificate?

[Maso]

Peter,

 

Yes I created a certificate template on the CA with intended purpose "Client Authentication". I added this too the SCCM server, then exported it with the private key and imported it into the Distribution Point.

 

If I look under Administration > Security > Certificates, I can see the certificate and it is unblocked.

 

The certificate is trusted all the way up to the root CA.

 

Are there any steps I've missed?

 

Thanks

Paul

[Maso]

HI

 

Sorted it, was the certificate on the IIS server, the name was right, but the server name was upper case, the certificate was lower case. Re-issued it with the correct name and it works fine.

 

Thanks

Paul

[anyweb]

so the moral of the story here is that certificates are case sensitive I guess, thanks for the update.