DHCP Scope Policy Change

david_2_3_5 1 Reputation point

Thank you for your time.

I have a long running WDS 2016 server.
That UEFI support was just added.

When first setup wdsmgfw.efi was first configured as the value for DHCP 067 Bootfile Name. Works great. We are able to access our PE.

Now I would like to switch to using pxelinux. As we do with our bios boot computers.

I changed the 067 Bootfile Name option value to syslinux.efi.

The UEFI clients still boot from wdsmgfw.efi.
I have
updated server
removed and recreated the policy
restarted dhcp service
restarted wds service
restarted the server

Simply put I do not know enough about windows based servers to know if there is some type of settings cache to clear?
Just not certain what I am not understanding.

Thanks again for your time.

Windows DHCP
Windows DHCP
Windows: A family of Microsoft operating systems that run across personal computers, tablets, laptops, phones, internet of things devices, self-contained mixed reality headsets, large collaboration screens, and other devices.DHCP: Dynamic Host Configuration Protocol (DHCP). A communications protocol that lets network administrators manage centrally and automate the assignment of Internet Protocol (IP) addresses in an organization's network.
926 questions
Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
8,272 questions
No comments
{count} votes

5 answers

Sort by: Most helpful
  1. Candy Luo 12,461 Reputation points

    Hi ,

    As far as I know, DHCP boot option 67 can only support one boot method. If you want to set up multiple boot methods, please use 'IP helper' router.

    For more details, you could refer to the following article:

    You want to PXE Boot? Don't use DHCP Options

    Best Regards,


    If the Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    No comments

  2. david_2_3_5 1 Reputation point

    Thank you for replying.

    I was changing or replacing the 067 entry. I do not need wdsmgfw.efi once I get syslinux working.

    I only need one boot method. I am attempting to make that one boot method syslinux.efi.

    Thanks again for replying

    No comments

  3. Candy Luo 12,461 Reputation points

    Hi ,

    Thanks for your clarify. Please understand, we are not familiar with Linux boot method. I am not sure if this boot method can work with DHCP 067 Bootfile Name. I would suggest you contact Linux support for further help.

    Best Regards,

    No comments

  4. david_2_3_5 1 Reputation point

    Ignore that I am using an unfamiliar boot method.

    The symptoms should be that it fails if it does pxelinux did not support 67.

    For example I have gone into my policy and changed 067 string to 'intentional failure'.

    UEFI continues to boot wdsmgfw.efi and MBR uses syslinux whose MBR file I can not recall (Been years since I configured it).

    It is working, where me with my limited understanding think it should not.

    No comments

  5. David Gill 1 Reputation point

    bumping this to see if anyone has any suggestions.

    No comments