spgsitsupport Posted February 2, 2017 Report post Posted February 2, 2017 While doing PXE boot, wherever settings I have in DHCP server (for options 66/67) work just fine But using Hyper-V Gen2 VM boot seems to insist on \Boot\x64\wdsmgfw.efi Why not \SMSBoot\x64\wdsmgfw.efi ? Where to change it? Also does anybody use DHCP Policies on Server 2012 R2 as per: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence Seb Quote Share this post Link to post Share on other sites More sharing options...
SMSNewb Posted February 2, 2017 Report post Posted February 2, 2017 I'm also looking for information on this. How to do UEFI OSD but also have 32bit OSD. Right now, if I set my UEFI TS to my 64bit boot image, it breaks all my 32bit OSD... very annoying Quote Share this post Link to post Share on other sites More sharing options...
spgsitsupport Posted February 2, 2017 Report post Posted February 2, 2017 But that is not behaviour I see with all UEFI machines, ie Surface Pro boots fine to UEFI network stack & TS works fine So just inconsistent Quote Share this post Link to post Share on other sites More sharing options...
Rocket Man Posted February 4, 2017 Report post Posted February 4, 2017 DHCP options are not supported, use IP helpers instead which are configured on the core switches of the network. Right now, if I set my UEFI TS to my 64bit boot image, it breaks all my 32bit OSD You cant image an x86 machine using a x64 boot image but you can however image an x64 machine using an x86 boot file, would that be what you mean by it breaks my 32bit OSD Quote Share this post Link to post Share on other sites More sharing options...
spgsitsupport Posted February 5, 2017 Report post Posted February 5, 2017 DHCP options are not supported, use IP helpers instead which are configured on the core switches of the network. Sorry, but who says that? https://2pintsoftware.com/whitepaper-using-dhcp-uefi-bios-pxe-booting/ Quote Share this post Link to post Share on other sites More sharing options...
Rocket Man Posted February 6, 2017 Report post Posted February 6, 2017 It is not a supported function from Microsoft! https://support.microsoft.com/en-us/help/259670/pxe-clients-computers-do-not-start-when-you-configure-the-dynamic-host-configuration-protocol-server-to-use-options-60,-66,-67 quote: Important: Microsoft does not support the use of these options on a DHCP server to redirect PXE clients It is after all a Microsoft product you are using, so I would imagine Microsoft would not recommend best practices otherwise! FYI: I had similar issues to what you are describing, but when options where removed as recommended from numerous blogs and IP helpers configured all worked seamlessly whether its a BIOS or UEFI boot. Also another reason as to why you should use IP helpers: https://www.windows-noob.com/forums/topic/15029-can-only-uefi-pxe-nce-no-longer-pxe-boots-afterwards/ Quote Share this post Link to post Share on other sites More sharing options...
spgsitsupport Posted March 10, 2017 Report post Posted March 10, 2017 [sOLVED] No, it works fine in the end. I do prefer to tell my systems what to do, instead of some file making "guess" on my behalf. In the end I do not need PXE server at all! Quote Share this post Link to post Share on other sites More sharing options...
Rocket Man Posted March 10, 2017 Report post Posted March 10, 2017 In the end I do not need PXE server at all! While doing PXE boot, wherever settings I have in DHCP server (for options 66/67) work just fine spgsitsupport to say this is confusing is an understatement Quote Share this post Link to post Share on other sites More sharing options...
spgsitsupport Posted March 11, 2017 Report post Posted March 11, 2017 That was the solution for me, gave UP on PXE server calls all together. In flat network DHCP only works fine for either legacy BIOS or UEFI network boot It is not confusing (unless the naming is confusing, but I can not change it), I started with network boot (also called client PXE boot) using PXE server, ended up doing network boot with DHCP only (no more PXE server) I boot what I want, not what the system (which is not easily configurable) gives me Quote Share this post Link to post Share on other sites More sharing options...
