Issues with PXE OSD

Bojan Zivkovic 441 Reputation points
2022-11-03T11:56:04.433+00:00

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 Configuration Manager Deployment
Microsoft Configuration Manager Deployment
Microsoft Configuration Manager: An integrated solution for for managing large groups of personal computers and servers.Deployment: The process of delivering, assembling, and maintaining a particular version of a software system at a site.
924 questions
{count} votes

8 answers

Sort by: Most helpful
  1. Rahul Jindal [MVP] 9,551 Reputation points MVP
    2022-11-03T22:24:17.74+00:00

    Haven't seen that error before, but does pxe work with an unknown device?


  2. Gideoney 446 Reputation points
    2022-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


  3. Bojan Zivkovic 441 Reputation points
    2022-11-04T11:33:17.753+00:00

    I reinstalled MP yesterday.


  4. Bojan Zivkovic 441 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.

    0 comments No comments

  5. 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.

    0 comments No comments