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(73.60000000000001, 93%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESV%3C/text%3E%3C/svg%3E)
Hi,
MEM (SCCM) 2010
When performing PXE boot at one of the sites, we observe that the PXE functionality suddenly stops working and the performance of the PXE Enabled DP Server severely deteriorates to the point of "Out of memory" errors. Also below entries are observed in SMS PXE logs indicative of insufficient system resources. We've also able to confirm similar errors in the event viewer logs indicating memory overload and consumption.
*
*> RegQueryValueExW failed for Software\Microsoft\SMS\DP, RootCACertificates SMSPXE 3/30/2022 7:30:31 AM 4148 (0x1034)
RegQueryValueExW failed for Software\Microsoft\SMS\DP, RootCACertificates SMSPXE 3/30/2022 7:30:31 AM 4152 (0x1038)
RegReadString failed; 0x800705aa SMSPXE 3/30/2022 7:30:31 AM 4152 (0x1038)
RegReadString failed; 0x800705aa SMSPXE 3/30/2022 7:30:31 AM 4148 (0x1034)
PXE::MP_GetList failed; 0x800705aa SMSPXE 3/30/2022 7:30:31 AM 4152 (0x1038)
PXE::MP_GetList failed; 0x800705aa SMSPXE 3/30/2022 7:30:31 AM 4148 (0x1034)
PXE::MP_LookupDevice failed; 0x800705aa SMSPXE 3/30/2022 7:30:31 AM 4152 (0x1038)
PXE::MP_LookupDevice failed; 0x800705aa SMSPXE 3/30/2022 7:30:31 AM 4148 (0x1034)
RegQueryValueExW failed for Software\Microsoft\SMS\DP, RootCACertificates SMSPXE 3/30/2022 7:30:31 AM 4152 (0x1038)
RegReadString failed; 0x800705aa SMSPXE 3/30/2022 7:30:31 AM 4152 (0x1038)
RegQueryValueExW failed for Software\Microsoft\SMS\DP, RootCACertificates SMSPXE 3/30/2022 7:30:31 AM 4148 (0x1034)
PXE::MP_GetList failed; 0x800705aa SMSPXE 3/30/2022 7:30:31 AM 4152 (0x1038)
RegReadString failed; 0x800705aa SMSPXE 3/30/2022 7:30:31 AM 4148 (0x1034)
PXE::MP_GetList failed; 0x800705aa SMSPXE 3/30/2022 7:30:31 AM 4148 (0x1034)
PXE::MP_ReportStatus failed; 0x800705aa SMSPXE 3/30/2022 7:30:31 AM 4152 (0x1038)
PXE::MP_ReportStatus failed; 0x800705aa SMSPXE 3/30/2022 7:30:31 AM 4148 (0x1034)
RegQueryValueExW failed for Software\Microsoft\SMS\DP, RootCACertificates SMSPXE 3/30/2022 7:30:31 AM 4172 (0x104C)
RegReadString failed; 0x800705aa SMSPXE 3/30/2022 7:30:31 AM 4172 (0x104C)
PXE::MP_GetList failed; 0x800705aa SMSPXE 3/30/2022 7:30:31 AM 4172 (0x104C)
PXE::MP_LookupDevice failed; 0x800705aa SMSPXE 3/30/2022 7:30:31 AM 4172 (0x104C)
RegQueryValueExW failed for Software\Microsoft\SMS\DP, RootCACertificates SMSPXE 3/30/2022 7:30:31 AM 4172 (0x104C)
RegReadString failed; 0x800705aa SMSPXE 3/30/2022 7:30:31 AM 4172 (0x104C)
PXE::MP_GetList failed; 0x800705aa SMSPXE 3/30/2022 7:30:31 AM 4172 (0x104C)
RegQueryValueExW failed for Software\Microsoft\SMS\DP, RootCACertificates SMSPXE 3/30/2022 7:30:31 AM 4168 (0x1048)
PXE Provider failed to process message.
Insufficient system resources exist to complete the requested service. (Error: 800705AA; Source: Windows) SMSPXE 3/30/2022 7:30:31 AM 4172 (0x104C)
RegQueryValueExW failed for Software\Microsoft\SMS\DP, RootCACertificates SMSPXE 3/30/2022 7:30:31 AM 4144 (0x1030)
RegReadString failed; 0x800705aa SMSPXE 3/30/2022 7:30:31 AM 4168 (0x1048)
B4:45:06:4A:46:6A, 4C4C4544-004E-3510-8036-B7C04F544733: Not serviced. SMSPXE 3/30/2022 7:30:31 AM 4172 (0x104C)
PXE::MP_GetList failed; 0x800705aa SMSPXE 3/30/2022 7:30:31 AM 4168 (0x1048)
RegQueryValueExW failed for Software\Microsoft\SMS\DP, RootCACertificates SMSPXE 3/30/2022 7:30:31 AM 4160 (0x1040)
PXE::MP_LookupDevice failed; 0x800705aa SMSPXE 3/30/2022 7:30:31 AM 4168 (0x1048)
PXE Provider failed to process message.
Insufficient system resources exist to complete the requested service. (Error: 800705AA; Source: Windows) SMSPXE 3/30/2022 7:30:31 AM 4152 (0x1038)
RegReadString failed; 0x800705aa SMSPXE 3/30/2022 7:30:31 AM 4160 (0x1040)
PXE Provider failed to process message.
Insufficient system resources exist to complete the requested service. (Error: 800705AA; Source: Windows) SMSPXE 3/30/2022 7:30:31 AM 4148 (0x1034)
PXE::MP_GetList failed; 0x800705aa SMSPXE 3/30/2022 7:30:31 AM 4160 (0x1040)
B4:45:06:4A:46:6A, 4C4C4544-004E-3510-8036-B7C04F544733: Not serviced. SMSPXE 3/30/2022 7:30:31 AM 4148 (0x1034)
B4:45:06:4A:46:6A, 4C4C4544-004E-3510-8036-B7C04F544733: Not serviced. SMSPXE 3/30/2022 7:30:31 AM 4152 (0x1038)
PXE::MP_LookupDevice failed; 0x800705aa SMSPXE 3/30/2022 7:30:31 AM 4160 (0x1040)
RegQueryValueExW failed for Software\Microsoft\SMS\DP, RootCACertificates SMSPXE 3/30/2022 7:30:31 AM 4168 (0x1048)
RegReadString failed; 0x800705aa SMSPXE 3/30/2022 7:30:31 AM 4168 (0x1048)
PXE::MP_GetList failed; 0x800705aa SMSPXE 3/30/2022 7:30:31 AM 4168 (0x1048)
PXE::MP_ReportStatus failed; 0x800705aa SMSPXE 3/30/2022 7:30:31 AM 4168 (0x1048)
RegQueryValueExW failed for Software\Microsoft\SMS\DP, RootCACertificates SMSPXE 3/30/2022 7:30:31 AM 4160 (0x1040)*
*
At the above site the no of machines being imaged simultaneously is about 26 computers (Which is not very high considering we've seen a much higher count). Also this problem started off late and there weren't any significant changes in the Infrastructure.
We have about 180 DPs (PXE) enabled with almost a similar configuration - 8 GB RAM, 1.2 TB HDD and we're not seeing a similar impact at any other sites except at the one above, and this has started off late.
We're considering replacing WDS with PXE Responder service, or NIC teaming (aggregation) for a higher NIC throughput. Apart from these can we have any suggestions or advice to remediate/analyse this issue?
Any info would be helpful and appreciated.
Thank You.
SV
Hi,
Thanks for posting in Microsoft MECM Q&A forum.
We could specify the PXE server response delay in the properties of PXE-enabled DPs to have a try. This option is to specify delay (in seconds) for the distribution point before it responds to computer requests when multiple PXE-enabled distribution points are used. This can reduce the number of simultaneously concurrent requests to save system resources.
By default, the Configuration Manager PXE service point responds first to network PXE requests. The reponse delay is provided by the PXE client, and it shows the time that has passed since the client started the PXE boot process (seconds elapsed since client began address acquisition or renewal process). A client sends requests to the server at intervals of 0 (default), 4, 8, 16, or 32 seconds.
Best regards,
Simon
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hi Simon,
Thank You very much for getting back. Will definitely explore this option of setting the PXE Server response delay and see how things go. For now we have configured the PXE responder service and we're monitoring the build situation.
Regards
SV
Hi @SAMUEL VALAPARLA ,
Thanks for your reply and information. Looking forward to hearing from you.
If the answer is helpful, it's appreciated that you could click "Accept Answer", this will help other users to search for useful information more quickly. Have a nice day!
Best regards,
Simon
Hi,
Hope everything goes well. We haven't heard from you for a few days and would like to know the current status of the problem. If there is any other assistance we can provide, please feel free to let us know, we will do our best to help you.
Thanks for your time.
Best regards,
Simon
As mentioned last, we've enabled PXE responder service and it's been going strong till now.. Without any interruptions. Should there be any further issues and if we have to resort to the PXE Server response Delay option, I will update this thread accordingly.
Thank You.
SV
Hi,
Thanks for your reply. Looking forward to hearing good news from you.
Best regards,
Simon