This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(278.4, 54%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBJ%3C/text%3E%3C/svg%3E)
I am trying to setup a distribution point to use the built-in PXE capabilities and not use WDS. Our SCCM environment is HTTPS.
I have it setup but, when I attempt to PXE boot a device, it gets "no valid offer received". The SMSPXE.log shows a lot of 0x80070490 errors such as:
PXE::MP::GetMPListAndConnectionInfo failed; 0x80070490
PXE::MP::IsKnownMachine failed; 0x80070490
The smsdpusage.log shows error 80072ee5 such as:
Cannot connect with winhttp; 80072ee5
Failed to get information for MP: . 80072ee5.
I suspect this is a certificate issue for HTTPS communication. Does this scenario need a client authentication cert as described here under "Site systems that have a distribution point installed"?
And would it be installed under the DP properties on the Communication tab replacing the self-signed cert there? Should the subject name be the FQDN of the DP?
Skip
I try to remember, that PXE does not need its own certificate, and DP's cert is enough to launch PXE. I did setup last SCCM infra about 5-6 years ago, but even then the PXE cert was not needed. Back very old old days there was certificate inserted into boot image, but that should not be needed anymore.
So, first make sure that can you download any content from that DP using Software Centrer, does the traffic works at all?
When I was tinkering with WDS, devices were able to download the boot WIM but the task sequence wizard never appeared. So the DP can send content.
@Benninghouse, John D - DOT pulling WIN does not actually tell you the certificate validation, because PXE boot happends on different protocol. I think it would be easier to solve the case if you would try to download application installation content from that DP and ensure it works. Just remember to disable any fallback, so that DP is one and only which is available.
