none
Clients looking at wrong DP servers. RRS feed

  • Question

  • We recently added a new MP/DP to our second domain, to ease traffic going through the firewall. We have adjusted the boundaries accordingly, so now Boundary Group in DomainA only have DomainA servers and Boundary Group in DomainB only has the one Server.

    When we try and build devices on any boundary in DomainB, after the PXE booting stage, the SMSTS.log shows:

    "Using user defined MP locations: http://<DomainA_MP_DP>; <DomainA_MP_DP>"

    ......

    "Error received 0x80072ee2 from WinHttpSendRequest"

    .....

    "socket 'connect' failed; 8007274c"

    Can't get the log file, as it in a test Vm setup. I have a ticket logged with Microsoft, but they seem stumped. It should be using only the one server in DomainB.

    Any guidance would be appreciated.

    Thanks


    Matthew Currie

    Tuesday, November 19, 2019 9:24 AM

Answers

  • Managed to sort this out ourselves.

    Build is failing after PXE booting and before Task Sequence selection. The information its using is from the Boot.WIM.

    Updated the boot image, which should now include the new MP. Redistributed, redeployed, now working.


    Matthew Currie

    • Marked as answer by mdc.111 Monday, November 25, 2019 9:08 AM
    Monday, November 25, 2019 9:08 AM

All replies

  • Try to create boot media with dynamic MP (Domain B MP) and and check the deployment again

    Check also the below thread 

    https://social.technet.microsoft.com/Forums/en-US/226affab-deaf-4d1b-94fb-87908d17b054/choose-the-right-management-point-from-winpe?forum=configmanagerosd

     
    Tuesday, November 19, 2019 10:11 AM
  • Hi Matthew,

    Try to configure your boundaries based on IP address range or VLAN network and update the members of the both boundary groups.

    Make sure also that the boot images are already distributed to the new DP.

    Regards,

    SAAD Youssef

    ______

    Please remember to mark the replies as answer if they help, thank you!

    • Edited by SAAD Youssef Tuesday, November 19, 2019 11:07 AM
    Tuesday, November 19, 2019 11:06 AM
  • Hi Matthew Currie,

    Thanks for posting in TechNet. Please try to associate the new DP with boundary group in Domain B and make sure the contents are distribute to the new DP in Domain B. 

    1. The error 0x80072EE2 means network connection-related errors. Please help check if the firewall is configured correctly. Here is a similar thread for your reference:
    TS failed randomly: Error. Received 0x80072ee2 from WinHttpSendRequest

    2. The error 8007274d means "No connection could be made because the target machine actively refused it". Please help check if the correct certificates are in place. For more information, please refer to:
    SCCM OSD Error Socket Connect Failed 8007274d

    Thanks for your time.

    Best regards,
    Simon

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, November 19, 2019 11:43 AM
  • Have you enabled MP affinity using the option on the General page of the Hierarchy Settings that reads "Clients prefer to use management points specified in boundary groups"?

    Jason | https://home.configmgrftw.com | @jasonsandys

    Tuesday, November 19, 2019 2:57 PM
  • Hi,

    May we know the current status of the question? 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 and regards,
    Simon 

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, November 22, 2019 1:46 AM
  • Managed to sort this out ourselves.

    Build is failing after PXE booting and before Task Sequence selection. The information its using is from the Boot.WIM.

    Updated the boot image, which should now include the new MP. Redistributed, redeployed, now working.


    Matthew Currie

    • Marked as answer by mdc.111 Monday, November 25, 2019 9:08 AM
    Monday, November 25, 2019 9:08 AM
  • Hi Matthew,

    Thanks for posting in TechNet and your sharing. Here's a short summary for the problem.

    Problem/Symptom:
    ===================
    Clients looked at wrong DP servers in different domain. 

    Solution:
    ===================
    Updated the boot image, redistributed and redeployed

    Thanks again for your time.

    Best regards,
    Simon

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, November 26, 2019 5:43 AM