• Server
    • FOG Version: 1.3.5-RC-10
    • OS: Ubuntu 14.04

    Has anyone had any luck yet getting UEFI to work with Windows Server 2008 DHCP? I’ve been following this link: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence which states that no one has gotten it to work with 2008 yet. I’ve tried all the available PXE options listed and no go, but it also just reboots to startup menu instead of displaying what the issue is after it tries to network boot so I can’t get much more information. Wireshark reports it as Arch:00007:UNDI:003016.

    I’m working on getting some images captured for our new Windows 10 HP Probook 450 G4 machines that are coming in and I would prefer to keep them UEFI rather than switch back to Legacy. Anyone have any other tips on possibly getting this to work?

  • Moderator

    @Grizzly In the long run, you will not be sorry you upgraded. Plus extended support for 2008 is only for just a few short years.

  • @george1421 That was my worry. I went ahead and got approval to upgrade our DHCP to 2012 R2 fearing that 2008 just wouldn’t work. Thanks for the reply!

  • Moderator

    We have had no joy getting Windows 2008 dhcp to hand out the right file name based on the pxe booting type. 2012 works as advertised. For the 2008 dhcp server the only option is to use dnsmasq (after compiling 2.76) to dynamically hand out the right file name based on the dhcp booting hardware.

    The only other option to to manually switch dhcp option 67 {boot-file} between the hardware arch. Its not a very good solution if you have a moderate size campus.