What's new
Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

SOLVED Added new DP in remote location. Can't deploy os over PXE.

  • Thread starter Thread starter nandgate
  • Start date Start date
  • Replies Replies 4
  • Views Views 11K
Status
Not open for further replies.
N

nandgate

New Member
Messages
3
Reaction score
1
Points
3
Hi.

We have added a new dp in a remote office to deploy windows to computers in the new office. We are actually using that method to deploy W10 to our machines in central office "A" without any issues but when we try to do same way in office "B" we can see errors in pxe, in the computer we see PXE-E55 error. This is the "smspxe.log" content (from the remote dp "B" with issues):

Begin validation of Certificate [Thumbprint 4BA2212CB66572BD8FE44C19A14515C378F4E8DC] issued to 'c269716c-5622-4d1e-9f82-94d5655f2aca' SMSPXE 07/06/2018 9:54:20 4100 (0x1004)
Completed validation of Certificate [Thumbprint 4BA2212CB66572BD8FE44C19A14515C378F4E8DC] issued to 'c269716c-5622-4d1e-9f82-94d5655f2aca' SMSPXE 07/06/2018 9:54:20 4100 (0x1004)
Begin validation of Certificate [Thumbprint 4BA2212CB66572BD8FE44C19A14515C378F4E8DC] issued to 'c269716c-5622-4d1e-9f82-94d5655f2aca' SMSPXE 07/06/2018 10:54:20 4296 (0x10C8)
Completed validation of Certificate [Thumbprint 4BA2212CB66572BD8FE44C19A14515C378F4E8DC] issued to 'c269716c-5622-4d1e-9f82-94d5655f2aca' SMSPXE 07/06/2018 10:54:20 4296 (0x10C8)
Begin validation of Certificate [Thumbprint 4BA2212CB66572BD8FE44C19A14515C378F4E8DC] issued to 'c269716c-5622-4d1e-9f82-94d5655f2aca' SMSPXE 07/06/2018 11:54:20 3780 (0x0EC4)
Completed validation of Certificate [Thumbprint 4BA2212CB66572BD8FE44C19A14515C378F4E8DC] issued to 'c269716c-5622-4d1e-9f82-94d5655f2aca' SMSPXE 07/06/2018 11:54:20 3780 (0x0EC4)
socket 'connect' failed; 8007274c SMSPXE 07/06/2018 12:09:39 4452 (0x1164)
sending with winhttp failed; 80072ee2 SMSPXE 07/06/2018 12:09:39 4452 (0x1164)
Unsuccessful in getting MP key information. 80072ee2. SMSPXE 07/06/2018 12:09:39 4452 (0x1164)
PXE::MP_InitializeTransport failed; 0x80072ee2 SMSPXE 07/06/2018 12:09:39 4452 (0x1164)
PXE::MP_LookupDevice failed; 0x80070490 SMSPXE 07/06/2018 12:09:39 4452 (0x1164)
socket 'connect' failed; 8007274c SMSPXE 07/06/2018 12:09:51 3144 (0x0C48)
sending with winhttp failed; 80072ee2 SMSPXE 07/06/2018 12:09:51 3144 (0x0C48)
Unsuccessful in getting MP key information. 80072ee2. SMSPXE 07/06/2018 12:09:51 3144 (0x0C48)
PXE::MP_InitializeTransport failed; 0x80072ee2 SMSPXE 07/06/2018 12:09:51 3144 (0x0C48)
PXE::MP_LookupDevice failed; 0x80070490 SMSPXE 07/06/2018 12:09:51 3144 (0x0C48)
socket 'connect' failed; 8007274c SMSPXE 07/06/2018 12:10:15 3592 (0x0E08)
sending with winhttp failed; 80072ee2 SMSPXE 07/06/2018 12:10:15 3592 (0x0E08)
Unsuccessful in getting MP key information. 80072ee2. SMSPXE 07/06/2018 12:10:15 3592 (0x0E08)
PXE::MP_InitializeTransport failed; 0x80072ee2 SMSPXE 07/06/2018 12:10:15 3592 (0x0E08)
PXE::MP_LookupDevice failed; 0x80070490 SMSPXE 07/06/2018 12:10:15 3592 (0x0E08)
socket 'connect' failed; 8007274c SMSPXE 07/06/2018 12:10:21 4452 (0x1164)
sending with winhttp failed; 80072ee2 SMSPXE 07/06/2018 12:10:21 4452 (0x1164)
Unsuccessful in getting MP key information. 80072ee2. SMSPXE 07/06/2018 12:10:21 4452 (0x1164)
PXE::MP_InitializeTransport failed; 0x80072ee2 SMSPXE 07/06/2018 12:10:21 4452 (0x1164)
PXE::MP_ReportStatus failed; 0x80070490 SMSPXE 07/06/2018 12:10:21 4452 (0x1164)
PXE Provider failed to process message.
Unknown error (Error: 80070490; Source: Unknown) SMSPXE 07/06/2018 12:10:21 4452 (0x1164)
MAC ADDRESS OF COMPUTER IN REMOTE LOCATION: Not serviced. SMSPXE 07/06/2018 12:10:21 4452 (0x1164)
socket 'connect' failed; 8007274c SMSPXE 07/06/2018 12:10:33 3144 (0x0C48)
sending with winhttp failed; 80072ee2 SMSPXE 07/06/2018 12:10:33 3144 (0x0C48)
Unsuccessful in getting MP key information. 80072ee2. SMSPXE 07/06/2018 12:10:33 3144 (0x0C48)
PXE::MP_InitializeTransport failed; 0x80072ee2 SMSPXE 07/06/2018 12:10:33 3144 (0x0C48)
PXE::MP_ReportStatus failed; 0x80070490 SMSPXE 07/06/2018 12:10:33 3144 (0x0C48)
PXE Provider failed to process message.
Unknown error (Error: 80070490; Source: Unknown) SMSPXE 07/06/2018 12:10:33 3144 (0x0C48)
MAC ADDRESS OF COMPUTER IN REMOTE LOCATION: Not serviced. SMSPXE 07/06/2018 12:10:33 3144 (0x0C48)
socket 'connect' failed; 8007274c SMSPXE 07/06/2018 12:10:57 3592 (0x0E08)
sending with winhttp failed; 80072ee2 SMSPXE 07/06/2018 12:10:57 3592 (0x0E08)
Unsuccessful in getting MP key information. 80072ee2. SMSPXE 07/06/2018 12:10:57 3592 (0x0E08)
PXE::MP_InitializeTransport failed; 0x80072ee2 SMSPXE 07/06/2018 12:10:57 3592 (0x0E08)
PXE::MP_ReportStatus failed; 0x80070490 SMSPXE 07/06/2018 12:10:57 3592 (0x0E08)
PXE Provider failed to process message.
Unknown error (Error: 80070490; Source: Unknown) SMSPXE 07/06/2018 12:10:57 3592 (0x0E08)
MAC ADDRESS OF COMPUTER IN REMOTE LOCATION: Not serviced. SMSPXE 07/06/2018 12:10:57 3592 (0x0E08)


I'm new in sccm, so any help will be apreciated. The site status in sccm console seems to be ok, everything is green. I have dhcp options configured:
60: PXEClient
66: IPAddress of the remote dp "B"
67: \SMSBoot\x64\pxeboot.com

Seems that the computer obtains ip address, but then receive the error PXE-E55
PXE-E55: ProxyDHCP service did not reply to request on port 4011

The WDS in remote dp "B" has the checkbox "not listen in dhcp ports" marked. "configure dhcp options as this is also pxe server" checked too.

Any ideas?

Thank you so much.
 
Sort by date Sort by votes
PXE::MP_LookupDevice failed; 0x80070490 SMSPXE 07/06/2018 12:09:51 3144 (0x0C48)
socket 'connect' failed; 8007274c SMSPXE 07/06/2018 12:10:15 3592 (0x0E08)
sending with winhttp failed; 80072ee2 SMSPXE 07/06/2018 12:10:15 3592 (0x0E08)
Unsuccessful in getting MP key information. 80072ee2. SMSPXE 07/06/2018 12:10:15 3592 (0x0E08)

Let me know if this helps - https://prajwaldesai.com/sccm-osd-error-socket-connect-failed-8007274d/
 
Upvote 0 Downvote
Prajwal Desai said:
PXE::MP_LookupDevice failed; 0x80070490 SMSPXE 07/06/2018 12:09:51 3144 (0x0C48)
socket 'connect' failed; 8007274c SMSPXE 07/06/2018 12:10:15 3592 (0x0E08)
sending with winhttp failed; 80072ee2 SMSPXE 07/06/2018 12:10:15 3592 (0x0E08)
Unsuccessful in getting MP key information. 80072ee2. SMSPXE 07/06/2018 12:10:15 3592 (0x0E08)

Let me know if this helps - https://prajwaldesai.com/sccm-osd-error-socket-connect-failed-8007274d/
Click to expand...


Hi Prajwal. Thanks for the reply, we do not have HTTPS option enabled for comunication between clients and dps. I double-checked and we are only using HTTP, and the main dp (which is actually deploying w10 through pxe successfully) don't have any ssl certificate configured in IIS "bindings" for https. So the issue we have, seems that isn't related to certificates or https since we are using HTTP for client-dp comunications.

Thanks.
 
Upvote 0 Downvote
Hi Prajwal. Seems to be a networking issue, the firewall was blocking ports that configmgr needs to have opened in the remote location. That's why pxe can't boot properly. Solved!
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

  • PENDING Deploy Visual Studio Updates Using ConfigMgr
  • PENDING Software Update deployment windows dialog instead of toast notification
  • PENDING SCCM Surface PRO 9 5G (ARM64) PXE no boot with Dongle Microsoft Thunderbolt 4
  • SOLVED Secondary Site Prerequisite Check fails.
  • PENDING Primary Site added WSUS Admin IIS site after running Post-Install

    • Forum statistics

    Threads
    7,070
    Messages
    27,624
    Members
    17,879
    Latest member
    santoshseel

    Latest posts

    Trending content
    Back
    Top