PC not finding SCCM Server

Eaven HUANG 2,166 Reputation points
2024-07-08T01:01:25.38+00:00

Dear Experts,

I'm in the middle of deploying OS via SCCM and I followed some instructions on the internet to set up my DHCP subnet with

066 Boot Server Host Name: 10.xx.xx.xx

067 Bootfile Name: \smsboot\x64\wdsnbp.com

After the PC boots up, it starts over ipv4 then nothing happens, it didn't find out or contact the SCCM server and boot into its existing OS directly. I know that many experts recommend using IP Helper, but it's quite challenging our network team and I would need a quick solution for some projects at this stage. Do I also need to configure something for my WDS hosted on the same SCCM server? I didn't add any boot images there but some posts mentioning it needs to be authorized by DHCP

Microsoft Configuration Manager
{count} votes

2 answers

Sort by: Most helpful
  1. AllenLiu-MSFT 44,496 Reputation points Microsoft Vendor
    2024-07-08T05:48:23.55+00:00

    Hi, @Eaven HUANG

    Thank you for posting in Microsoft Q&A forum.

    DHCP options can be problematic and might not work reliably or consistently. Also, using DHCP options to control PXE requests in Configuration Manager is not supported by Microsoft.

    The recommended and supported method for PXE booting client computers on remote subnets is to use IP Helpers.

    Check the article for more details:

    https://video2.skills-academy.com/en-us/troubleshoot/mem/configmgr/os-deployment/troubleshoot-pxe-boot-issues#solution-1-verify-ip-helpers


    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Add comment".


  2. Rahul Jindal [MVP] 10,041 Reputation points MVP
    2024-07-08T07:32:35.2966667+00:00

    Pxe responder with IP helpers is the recommended and supported way. Microsoft introduced these to address these kind of issues.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.