none
UEFI PXE with WDS and DHCP on different VLANs RRS feed

  • Question

  • We've got a VLAN used for deployment that contains a WDS Server but with the general-use DHCP Server on another VLAN.  An IP Helper address is configured on the routers to direct all PCs to the DHCP Server and currently we have DHCP Options 66 and  67 to direct (BIOS) PXE to the WDS server just on the deployment VLAN's scope.

    Now we're trying to UEFI PXE boot too, we've discovered that DHCP Options are a no-go since you can only supply one network boot programme name.
    http://techthoughts.info/pxe-booting-wds-dhcp-scope-vs-ip-helpers/
    We tried removing the DHCP options but an attempt to PXE boot now does nothing.

    My question is, how does the WDS server (2012 R2) need to be configured to respond to BIOS and UEFI PXE clients in the absence of DHCP Options without messing up normal DHCP activity?

    Thanks for any help!

    Thursday, February 1, 2018 10:03 AM

All replies

  • Usually I simply tell customers to use DHCP policies as it is by far the easiest way to control legacy / UEFI booting behavior. Take a look at 2pint white paper: https://2pintsoftware.com/whitepaper-using-dhcp-uefi-bios-pxe-booting/

    Cheers,
    Anton

    Vacuum Breather Blog | Wing Commander Saga | Twitter

    Note: Posts are provided "AS IS" without warranty of any kind. If posts are helpful please don't forget to rate them as "Helpful" or as "Answer".

    Monday, February 5, 2018 2:11 PM
  • Thanks Anton.

    I've seen that whitepaper - it's very good.

    Unfortunately my DHCP server is 2008 R2 which doesn't support policies.  I can't upgrade it just yet as it's a DC too.

    I suspect I just need to untick both checkboxes on the DHCP tab of WDS to make my current setup work (having added extra IP Helper entries) but am a little cautious about doing so.

    Monday, February 5, 2018 4:44 PM