How to use both PXE and WoL on windows 10?
-
Server
- FOG Version: 1.3.5
- OS: Centos 7
Client
- Service Version:
- OS: Windows 10
Description
I have a wee bug I think is with intel nic. Using windows 10 enterprise, the nic is I217-lm on board a Dell Optiplex 9030 AIO. I can boot to pxe with WoL disabled on the card or I can enable WoL and use it but pxe doesn’t work. I am using uefi only with ipv4. Has anyone seen this before?
-
@Andy-Nicolson I have seen similar, but not exact. It’s difficult to change the boot order of UEFI. I don’t quite understand how it determines boot order - I don’t see any plain-english options in any of the firmware I’ve seen in UEFI mode. I’d imagine the piece to this puzzle is properly setting the boot order somehow.
-
Thanks Wayne. It’s something to try I suppose, Nothing else seems to work. It seems when WoL is enabled, after a restart the nic doesn’t even look for an IP at boot even though it’s set to boot from ipv4, and comes up saying its trying. If i shut it down and let it sit or do a cold power off, it works. I think it’s to do with the windows 10 hybrid shutdown. Not having pxe on a reboot is a real pain.
-
So if WoL is disabled and you boot the computer, it goes straight to PXE?
-
@Quazz Yep, When i restart with wol disabled on the nic through windows, It picks up an IP and boots to pxe, turn wol on, after a restart it times out at getting an ip. All other energy saving is disabled on the nic. Also has the latest drivers.
-
@Andy-Nicolson Any BIOS updates available per chance?
Sounds like a bug on that end.
-
@Andy-Nicolson It does look like bios version A8 and A11 touch on wol and pxe booting enhancements. And A07 addresses “Fixed the UEFI Network boot option will not show up when Load Legacy Option ROM is not enabled”
I would surely update to the latest bios/firmware. If that doesn’t address the issue and this 9030 is still under support call dell because this does sound like a firmware bug.
-
@george1421 @Quazz Thanks for this. There was a bios update it’s at A15 now but still the same problem. It’s almost like a switch is set on the nic and isn’t reset until it goes through hard shutdown. Maybe Dell will have the answer.
-
@Andy-Nicolson What boot file are you using?
-
@Andy-Nicolson You just said something that has me thinking.
Does WOL and PXE boot work if you unplug the power from the computer wait 10 seconds and then replug the power? What I’m trying to identify is that if everything works from a power up state vs a windows shutdown/restart. I remember reading somewhere that win10 can disable change the function of wol. This is because a normal windows 10 shutdown isn’t really a shutdown, but an enhanced sleep state to facilitate a faster startup. I’m not saying this is the case with this hardware (you should see this in others too), but it could be A issue if windows 10 specifically turns it off.
ref: http://www.sysadminshowto.com/how-to-configure-wake-on-lan-in-windows-10-and-windows-8-1/ -
@Tom-Elliott Hi, it’s set to ipxe.efi as default. But I think the problem is before pxe, almost like it’s in a hibernate state till windows starts
-
@Andy-Nicolson That’s almost EXACTLY the case. Windows 10, as @george1421 suggested, typically defaults to a “Fast boot” system. Essentially this puts a flag on the HDD that tells the hdd to pass pieces of information back into ram. While in “fast boot” mode, a shutdown doesn’t use any “power” persay, but when you turn the system on the cached drivers/memory items are reloaded into memory.
So with that said, a “reboot” from Windows 10 should remove this oddness. Maybe if you “reboot” and when the system is going through post you power it off?
-
@george1421 I think that’s the issue but I can’t find a way to get both WoL and pxe working from a restart as we use both and often restart the computers to image.
-
@Tom-Elliott I completely forgot about this. Fast startup screws so many things up, it’s unreal.
-
@Tom-Elliott @george1421 @Quazz Thanks for the info, Don’t suppose there is a “full shutdown” restart command you know of? I often use remote restart from powershell, maybe I should look into a wee script.
-
@Andy-Nicolson shutdown /s (followed by any other switches you’d use)
But it might be easier to just turn off fast startup in Win 10
-
@Quazz Thing is, fast startup is off. It’s got me flummoxed.
-
@Andy-Nicolson What about the NIC driver in Windows 10 itself? Its settings have influence on WoL and what not as well afaik.
Follow up question/test scenario: a machine without installation/without hard drive. Does this one WoL into PXE correctly?
-
@Quazz That’s what i see. default behaviour is full shutdown is fine. restart and the problem exists. remove wol and all power saving settings from the windows nic driver, the restart works fine with pxe, put just wol back on, problem returns. So it does pxe but only after a complete shutdown.
-
@Andy-Nicolson So shutting it down, calling WoL it will boot into FOG Menu, correct?
Very strange how a reboot would be the only situation where it would trip up. Perhaps there’s some setting in the BIOS that is causing this odd behavior?
