Okey, I sticking my neck out here, far out... but I think it's a bug in the EFI boot loader. This is why MS doesn't "support" using DHCP options, its not working as it should. And since it's not a lot of people in the world that can read native C which the loader is made of they have just dismissed it and said "not supported".
If I set Option 60 in my DHCP scope when DHCP and PXE server are on different servers the MS EFI loader starts working, i.e. it talks to the right host. Opposite of BIOS behavior... hmmm... I bet it's a TRUE/FALSE statement or possibly AND/OR evaluation that fails. I haven confirmed with a debugger but I am pretty sure. I can boot any EFI loader from WDS using a wide range of hardware, without Option 60. As soon as I try with the WDSMGFW.EFI, it loads and then hits a brick, trying to contact my DHCP server instead. If I set Option 60 it goes directly to the PXE server. Opposite land of BIOS... Strange huh? Best regards, //Andreas ############################## Co-Founder +46 727 253995 http://2pintSoftware.com<http://2pintsoftware.com/> https://twitter.com/AndHammarskjold
