"Immediate Task" does WOL, Client boots via PXE, but Task is only executed on second boot
First of all: Thanks for this fantastic project! It is making a usable IT-infrastructure possible in schools!
FOG 1.2.0 on Debian 7 (Linux fogserver 3.2.0-4-amd64 #1 SMP Debian 3.2.65-1+deb7u2 x86_64 GNU/Linux)
Client-OS: Xubuntu 14.04, x32
Client-Hardware: hp ProDesk 600 G1
Setting a Download-Task for one Client via Web GUI,
Expectation: Client is startet via WoL, boots via PXE, fog-stuff starts, imaging happening, client reboots to OS on HDD.
What is acutally happening: the fog-stuff is loaded via PXE, but has no idea that imaging should start. Have to manually reboot the client, then imaging works.
Speculation: It seems as if the client is booting so fast that the pxe-image is not ready when it is loaded from the server.
If I try this on a VM which has to be started manually, it is working fine, so it seems as if this is only happening with real hardware (and: it is not depending on the type of the real hardware!)
Any hints how I could handle this error to avoid dropping that cocktail and start imaging while sitting at the beach? :D
@Tom-Elliott Yeah, will try to make a video tomorrow or on Friday. So far I have an Acer Laptop and a bunch of PCs based on Asus P5G41T-M which have the same behavior.
Somehow I managed to reply to my own message but not to your reply… My answer is above, not below - haven’t found how to edit ist :-/ sorry!
The only thing I can think of is maybe the improper boot files are being used? Which other manufactures are doing this? Can you capture a video with system shut down and scheduling a tasking recording the wol and so forth? Can you do the same with all the manufacturers that are having the issue?
thanks for your fast reply!
Actually, it is booting from network (yeah, hp has some features™…), as I can see the fog/iPXE-stuff, after showing DHCP-request and mentioning the correct IP for the TFPTing from the fogserver and some orange-ish text (if I remember correct).
The same thing is happening with other manufacturers, too.
This a problem with HP. The WOL isn’t set to boot to network, but rather set to boot to disk. When you do your “second boot” it’s booting how the BIOS is determined to boot. Check your bios settings.