Enable PXE Responder without WDS (Windows Deployment Service)

In this post I will be showing you how to enable PXE responder without WDS (Windows Deployment Service). PXE responder service is now introduced in SCCM and offers many advantages.

We know that SCCM 1806 is released and comes bundled with lots of useful features. In my previous post we discussed about installing SCCM 1806 update. I also listed some of the best features of SCCM 1806.

With SCCM 1806, you enable PXE responder and get rid of WDS as it isn’t required anymore. This is a great feature because the PXE-enabled distribution point can now be a client or server OS.

In addition it can be a Windows Server Core. This new PXE responder service supports IPv6, and also enhances the flexibility of PXE-enabled distribution points in remote offices.

Enable PXE Responder without WDS (Windows Deployment Service)

To enable PXE responder without WDS, go to distribution points. Select the distribution point, right click and click Properties.

On the PXE tab of the distribution point properties, check Enable a PXE responder without Windows Deployment Service.

This new option enables a PXE responder on the distribution point, which doesn’t require Windows Deployment Services (WDS). On the confirmation box, click Yes to enable ConfigMgr PXE responder.

Enable PXE Responder without WDS

Note – Once you enable PXE responder, notice that all the options under Multicast tab are greyed out. That makes sense because previously whenever you enabled multicast, WDS was installed on the servers.

I need to add two basic rules here :-

  • If you enable PXE responder, Multicast options are greyed out / disabled.
  • If you enable multicast to simultaneously send data to multiple clients, then you cannot use PXE responder service.

Enable PXE Responder without WDS

Take a look at the status message details of SMS_DISTRIBUTION_MANAGER, you will find two things. First of all PXE is enabled on distribution point.

Confirm if PXE is enabled on distribution point

Take a look at status message details. On the SCCM distribution point we see the multicast is disabled.

Status Message Details

To confirm PXE responder service installation, launch services.msc. You will find ConfigMgr PXE Responder Service in the list of services.

ConfigMgr PXE Responder Service manages requests made by PXE enabled client computers. If this service is stopped, PXE-enabled client computers will be unable to install Windows remotely.

ConfigMgr PXE Responder ServiceI am going to test the OSD after enabling PXE responder in my prod setup. Let me know how PXE responder is working for you in comments section.

Leave a Reply

Your email address will not be published. Required fields are marked *


  1. Avatar photo Stévin Negi says:


    Don’t works for me.

    When I try to boot on PXE, I get an IP adress and the boot skip.



  2. hello,

    I am tried to deploy 1-PC with SCCM 1706

    win 10 image

    and I was skipped the f12 press button to boot PXE process by this kb

    now the deploy starts on this pc without press F12 but still need to push next on the pc

    how can I do this automatically without push next in task sequence wizard

    1. What do you mean by push next to PC ?. If you have set a TS password, yes you have to manually enter it and choose the task sequence. Otherwise deploy the TS as required and test it.

  3. Muito Obrigado, Prajwal Desai! Deu certo aqui

  4. Is there anything outside of this article that also needs configuring…such as ip helpers on the switches?

    I followed this article but our clients can’t communicate with the DP (they are on different subjects/VLANS.)

    I do t understand how the clients know about the PXE server otherwise.

      1. Avatar photo Raghu Chintamani says:

        Never configured.
        Would be useful if you can post one.

        1. The IP helpers would be configured on the network stack. Its basically a DHCP relay directing the clients request for pxe boot to the correct place during DORA.

          To configure an ip helper:
          enter global config,
          enter interface, cmd: interface g0/0/0
          set iphelper, cmd: ip helper-address x.x.x.x

  5. I am setting this up using DHCP helpers and wondering what settings I need in the options for UEFI

    I put in:

    option 67 ascii “SMSBoot\x64\wdsmgfw.efi”

    option 66 ip

    I am unfortunately getting “No valid offer received”

    I tried switching option 6:

    option 67 ascii “SMSBoot\x64\wdsnbp.com”

    I then got “Server response timeout”

    In smsboot\x64\ I have:







    1. Avatar photo Bert Vangeel says:

      Hi Jim,
      did you ever resolve this issue? I’m getting the same exact error and no idea why it’s failing.

  6. Avatar photo sean archer says:

    We are running a non wds pxe environment and seem to be having an odd issue. Some times it takes several attempts before a UEFI boot is successful. When it fails the message is PXE-E16 No valid offer received and I can see the smspxe logs (PXE: Sending reply to 10.128.???.???, PXE) but if i keep retrying the pxe boot it eventually succeeds, we run two pxe servers but i disable one when testing and still get the same issue on either server.

    Any idea’s are appreciated

  7. Avatar photo Joe Weatherton says:

    Hello, thank you so much for your great tutorials. I am attempting to get PXE without WDS working and i always get a pxe error stating no boot file name received. I have configured IP helpers in the router for the vlan that the unknown computer is on. I have a pxe enabled DP also on that same vlan. the IP helpers point two places one IP is the dhcp server and the other to the ip of the DP. how do i unsure that a bootfile is passed by the DP?

    1. Did you try redistributing the boot images to the DP and restarted the PXE responder service ?. I would recommend keeping one DP for one VLAN just to avoid the confusion.

      1. Avatar photo Joe Weatherton says:

        I have just initiated that redistribution thanks for the tip. I also found this is the last line in the smspxe.log after each attempt.
        TFTP: cannot open smsboot\SC100005\x64\wdsmgfw.efi. SCCMPXE 3/12/2020 10:04:32 AM 4824 (0x12D8)

  8. Hello
    I upgrade my config manager to 1806 and I follow all the steps, now I could not boot my unknown clients after pressing F12.

  9. Hi – Not working for me. Trying to PXE boot an unknown computer. (This works fine using usb boot media)…

    Log below:

    Client Boot TS reply:

    PXE: C8:D3:FF:A1:B1:91: No Task Sequence deployments.

    PXE: C8:D3:FF:A1:B1:91: Sending abort.

    PXE: Sending reply to, DHCP.

    TFTP: connected.

    TFTP: not able to open smsboot\x86wdsmgfw.efi.

    1. Avatar photo Christophe Girardy says:

      Did you find the answer to your problem ? I’m trying to setup a 1902 LAB but I have the same problem.
      I don’t have any option in DHCP (no 67 or other option setup) as in all my other installations.
      I have tried reinstalling everything from scratch 5 times (1 AD server / 1 SCCM / 1 SQL using HTTPS only) but without success. I have tried 1905 TP, it gives me the exact same error. I don’t remember having so many difficulties in the past installing a LAB on my laptop. I’m running W10 Enterprise 1903 with Hyper-V. I’ve done hundred of LABS without any problem in the past. It’s the first time I’m stuck with a PXE problem.
      Deploying apps / clients is working perfectly. I’m just stuck with this PXE thing…
      Can anyone help me please?

    2. C8:D3:FF:A1:B1:91: No Task Sequence deployments – Are you manually importing the computer info into SCCM using Mac address ?.

  10. Avatar photo Tomas Kozina says:

    Hi, I’m having a trouble booting.
    SMSPXE.log says:
    TFTP: connected. SCCMPXE 9. 8. 2018 10:00:40 5476 (0x1564)

    TFTP: not able to open smsbootx86wdsnbp.com. SCCMPXE 9. 8. 2018 10:00:40 5476 (0x1564)

    DHCP Option 67 is set “smsbootx64wdsnbp.com”
    When I set it to “smsbootx86wdsnbp.com” then log says “not able to open smsbootx64wdsnbp.com”

    1. Are all the files present inside smsboot > x86 folder ?. You need to verify it once.

      1. Avatar photo Tomas Kozina says:

        Yes, they are. When I try to test TFTP from a different computer in the same VLAN by running tftp -i GET smsbootx64wdsnbp.com I get “Connect request failed” so I think there’s a problem with TFTP communication.

        1. Avatar photo Tomas Kozina says:

          Problem was that when I turned of WDS it didn’t uninstall properly. When we directed option 67 directly to the boot package smsboot/AB000005/x64/wdsnbp.com (AB00005 is package of created boot image) and it works correctly.

          1. I didn’t understand the solution. Please can you explain more ?