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(166.4, 64%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJT%3C/text%3E%3C/svg%3E)
Migrated to a new site system that is currently on 2211 site version 5.0.9096.1000 Site system and DP's are running Server 2019. Running only Http on on systems. Migrated Distribution points over and tried to pxe. We started to receive 0xc000000f when the device attempts to load/launch pxe boot. Checked the WDS log files on the DP and seen this. The PXE server processed a request from a client of architecture x64uefi. However there were no boot images installed for this architecture. PXE clients of this architecture will not be able to complete the boot process successfully. To resolve this problem, add at least one boot image for this architecture. Steps Taken so far:
pxe log on DP:
InstallBootFilesForImage failed. 0x80004005 SMSPXE 4/6/2023 2:48:52 PM 3048 (0x0BE8) Warning: Failed to copy the needed boot binaries from the boot image F:\RemoteInstall\SMSImages\DR200002\boot.DR200002.wim. The operation completed successfully. (Error: 00000000; Source: Windows) SMSPXE 4/6/2023 2:48:52 PM 3048 (0x0BE8) Failed adding image F:\RemoteInstall\SMSImages\DR200002\boot.DR200002.wim. Will Retry.. Unspecified error (Error: 80004005; Source: Windows) SMSPXE 4/6/2023 2:48:52 PM 3048 (0x0BE8) RequestMPKeyInformation: Send() failed. SMSPXE 4/7/2023 10:34:24 AM 5580 (0x15CC) Unsuccessful in getting MP key information. 80004005. SMSPXE 4/7/2023 10:34:24 AM 5580 (0x15CC) PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 4/7/2023 10:34:24 AM 5580 (0x15CC) PXE::MP_LookupDevice failed; 0x80070490 SMSPXE 4/7/2023 10:34:24 AM 5580 (0x15CC) Using values from 'AllowedMPs' key. SMSPXE 4/7/2023 10:34:24 AM 5580 (0x15CC) Using Management Point: dcwinfp079.datarecognitoncorp.com SMSPXE 4/7/2023 10:34:24 AM 5580 (0x15CC) Not in SSL. SMSPXE 4/7/2023 10:34:24 AM 5580 (0x15CC) RequestMPKeyInformation: Send() failed. SMSPXE 4/7/2023 10:34:24 AM 5580 (0x15CC) Unsuccessful in getting MP key information. 80004005. SMSPXE 4/7/2023 10:34:24 AM 5580 (0x15CC) PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 4/7/2023 10:34:24 AM 5580 (0x15CC) PXE::MP_ReportStatus failed; 0x80070490 SMSPXE 4/7/2023 10:34:24 AM 5580 (0x15CC) PXE Provider failed to process message. Element not found. (Error: 80070490; Source: Windows) SMSPXE 4/7/2023 10:34:24 AM 5580 (0x15CC) CC:96:E5:7C:AF:1F, 4C4C4544-0048-4D10-804A-B1C04F325433: Not serviced. SMSPXE 4/7/2023 10:34:24 AM 5580 (0x15CC)
So I switched imaging to the Main Site server since I kept getting mp key errors on the DP and that works via Pxe using WDS. This is not ideal since its our main site system. I am still working through the same errors above on the DP's but seems to be a start. I have found two problems one was the Task sequence from our old SCCM server seems like its corrupt. Created a new TS with a boot image we already had for testing and Pxe loaded. I thought that was the full problem, so I moved imaging back to the DP and it fails still with the same 0x0000000f error. Not a solution but a work around for the moment since we have had imaging down for 2 weeks now.
I was able to get new distribution points to work with pxe booting by removing the dhcp scope options 66 and 67 and 60. I then setup IP helpers