1,071 questions
Haven't seen that error before, but does pxe work with an unknown device?
Issues with PXE OSD
![](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(150.4, 33%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBZ%3C/text%3E%3C/svg%3E)
Bojan Zivkovic
606
Reputation points
Hi, we have secondary site with Windows 10 Distribution Point - all of a sudden we are experiencing PXE OSD issues:
reply has no message header marker SCCMPXE 11/3/2022 4:54:11 AM 7876 (0x1EC4)
PXE: A6:29:11:18:CC:C2: Unsuccessful client info request. 0x80004005. SCCMPXE 11/3/2022 4:54:11 AM 7876 (0x1EC4)
PXE::MP::IsKnownMachine failed; 0x80070490 SCCMPXE 11/3/2022 4:54:11 AM 7876 (0x1EC4)
It is very vague so it can be anything. I reinstalled proxy management point hosted on secondary site server but in vain. Any help would be highly appreciated.
Microsoft Security | Intune | Configuration Manager | Deployment
{count} votes
-
Simon Ren-MSFT 40,346 Reputation points Microsoft External Staff2022-11-04T08:37:19.16+00:00 Hi,
Per my experience, the PXE errors 0x80070490 and 0x80004005 usually indicates that the management point isn't functioning properly. Please help check if the reinstalled proxy management point is working fine. Also review the MPSetup.log, MP_CliReg.log and mpcontrol.log on the management point to see if there is any error.
Thanks for your time.
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.
Sign in to comment
8 answers
Sort by: Most helpful
-
Rahul Jindal [MVP] 10,911 Reputation points MVP2022-11-03T22:24:17.74+00:00 -
Bojan Zivkovic 606 Reputation points
2022-11-04T08:57:40.41+00:00 No, it was imported into CM (MAC).
Sign in to comment -
-
![](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(240, 43%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EG%3C/text%3E%3C/svg%3E)
Gideoney 446 Reputation points2022-11-04T07:08:10.69+00:00 1.You can use IE to see if http://servername/sms_mp/.sms_aut?mplist and http://servername/sms_mp/.sms_aut?mpcert do work.
2.Check your MPControl.log on your SCCM server and the smspxe.log on your pxe server. The pxe log will be in the SCCM client area while the MPControl.log will be in the SCCM server logs.
3.Besides, the error is very similar to the thread below, the link for your reference:
failed-to-get-client-identity-0x80004005-in-sccm-pxe
configmgr-pxe-error-0x80070490-0x80004005-
Bojan Zivkovic 606 Reputation points
2022-11-04T08:59:15.747+00:00 Threads you mentioned - I tried with latter and MP reinstallation did not make any difference whatsoever. On the other hand, since this is Windows 10 DP not having WDS at all but ConfigMgr PXE Responder I doubt former will help me either.
Sign in to comment -
-
Bojan Zivkovic 606 Reputation points
2022-11-04T11:33:17.753+00:00 I reinstalled MP yesterday.
-
Simon Ren-MSFT 40,346 Reputation points Microsoft External Staff
2022-11-07T09:23:23.583+00:00 Hi,
1,Can we see any error in the mp logs?
2,Please check if there is any DNS issue. Also check if IIS is running or firewall blocks incoming traffic.
3,Are you using HTTPS only mode? If yes, please make sure the DP and MP have valid certificates. Similar thread for your reference:
SCCM OSD Error Socket Connect Failed 8007274dBest regards,
Simon
Sign in to comment -
-
Bojan Zivkovic 606 Reputation points
2022-11-07T12:31:27.113+00:00 In one branch OSD on desktop/laptop started to work with new network drivers in boot image. OSD on VMs was working all the time. In other branch error still persists. Unfortunately, we do not have vSphere in this troublesome location.
reply has no message header marker SMSPXE 11/7/2022 1:10:51 PM 8976 (0x2310)
Failed to send status message (80004005) SMSPXE 11/7/2022 1:10:51 PM 8976 (0x2310)
Unsuccessful in sending status message. 80004005. SMSPXE 11/7/2022 1:10:51 PM 8976 (0x2310)
PXE::MP_ReportStatus failed; 0x80070490 SMSPXE 11/7/2022 1:10:51 PM 8976 (0x2310)
PXE Provider failed to process message.
Element not found. (Error: 80070490; Source: Windows) SMSPXE 11/7/2022 1:10:51 PM 8976 (0x2310)mpcontrol log is errorless and CM itself does not report any issues on this MP/DP server (component status).
Honestly I am running out of ideas anymore.
-
Gideoney 446 Reputation points
2022-11-08T01:50:42.557+00:00 You are great. You've done a lot of work. Let's move on to troubleshooting solutions.
I noticed that what you said works in virtual machines and in one branch, while others don't. Can these branches ping MP/DP servers and PXE servers? My thinking is that maybe it has something to do with boundary groups.