Thanks for clarifying it.
The default bzImage kernel already had the network drivers needed for my setup (onboard Realtek NIC). I checked the WoL status of the ethernet adapter with ethtool. It showed:

Supports Wake-on: pumbg
Wake-on: d

So WoL was supported, but disabled.
Then I followed this guide to enable WoL on boot: https://wiki.archlinux.org/title/Wake-on-LAN
I created the /etc/udev/rules.d/81-wol.rules file in init.xz and init_32.xz, and added this rule:

ACTION=="add", SUBSYSTEM=="net", ATTR{address}!="00:00:00:00:00:00", RUN+="/usr/sbin/ethtool -s $name wol g"

I use ATTR{address} instead of NAME, so this rule would apply to any network interface (except loopback), regardless of the interface name.
With this rule in place I can wake up computers after a shutdown task (deploy with shutdown or capture with shutdown).

TLDR; I only needed to add an udev rule to the pre-built init.xz and init_32.xz (https://github.com/FOGProject/fos/releases/latest) to enable WoL.

Thanks for clarifying it.
The default bzImage kernel already had the network drivers needed for my setup (onboard Realtek NIC). I checked the WoL status of the ethernet adapter with ethtool. It showed:

Supports Wake-on: pumbg
Wake-on: d

So WoL was supported, but disabled.
Then I followed this guide to enable WoL on boot: https://wiki.archlinux.org/title/Wake-on-LAN
I created the /etc/udev/rules.d/81-wol.rules file in init.xz and init_32.xz, and added this rule:

ACTION=="add", SUBSYSTEM=="net", ATTR{address}!="00:00:00:00:00:00", RUN+="/usr/sbin/ethtool -s $name wol g"

I use ATTR{address} instead of NAME, so this rule would apply to any network interface (except loopback), regardless of the interface name.
With this rule in place I can wake up computers after a shutdown task (deploy with shutdown or capture with shutdown).

TLDR; I only needed to add an udev rule to the pre-built init.xz and init_32.xz (https://github.com/FOGProject/fos/releases/latest) to enable WoL.

After I deploy a computer with the shutdown option, I can’t wake it up anymore.
Wake on LAN works fine, when the computer has been shut down from either Windows or Linux (it enters the S5 power state). But after a FOG deployment WoL no longer works.
I assume the problem is with FOS (FOG Operating System) itself.
I tried to rebuild FOS (kernel 6.1.63) with every ACPI option I could find with “make menuconfig” in both the kernel (bzImage) and the FS (init.xz).
I tested this custom build with the “Debug” task. FOS loads fine. WoL still doesn’t work after shutting down the computer from FOS with the “poweroff” command.
Acpitool command supports only sleep (S3, S4), but not shutdown (S5).
What options are needed for FOS to support S5? Is it even possible to build a custom FOS from the official repo with S5 support: https://github.com/FOGProject/fos ?

@Arrowhead-IT The 8100 series seems to be “special”. This is the only HP series (from 7800 to 8300), where i ran into this issue (booting WinPE 5.0 ISO restarts the computer and iSCSI boot via sanboot errors out).
I already contacted HP, because even the iSCSI boot built into the bios auto-negotiates and works only at 10 Mbps, which makes iSCSI kinda useless. I guess if they fix the iSCSI issue, then ipxe might work as well.

On HP 8100 Elite computers undionly and ipxe loaders caused some troubles for me (FOG Trunk version).
Loading some ISOs simply restart the computer (mostly customized WinPE5.0 x64), and iSCSI boot doesn’t work at all.
When i use intel.kpxe or undionly.kpxe.INTEL, everything works fine. But there is a huge drawback though: these Intel loaders only negotiate and work at 10 Mbps.

Hi,

Is it possible to add custom advanced tasks or modifying existing ones?
I would like to add some more tasks to the task management to start Acronis products on specific hosts.
Even modifying existing tasks would be great, because i don’t need most of them (ClamAV, Test Disk, Full Wipe, etc).
I’ve already figured out, that these files are responsible for creating the tasks:

/var/www/fog/commons/functions.include.php
/var/www/fog/management/lib/Host.class.php
/var/www/fog/management/includes/tasks.advanced.include.php (this one is the advanced task management page)

I have the kernel and initrd files for various Acronis products and i can boot them fine using the PXE menu:

LABEL fog.acrtrimg
[INDENT=1]kernel fog/acronis/acrmem[/INDENT]
[INDENT=1]append initrd=fog/acronis/acrtrimg quiet vga=0x314[/INDENT]
[INDENT=1]MENU LABEL Acronis True Image Home[/INDENT]
[INDENT=1]TEXT HELP[/INDENT]
[INDENT=1]Boot Acronis True Image Home[/INDENT]
[INDENT=1] [/INDENT]
This one boots Acronis True Image Home (i renamed the original kernel to acrmem and the original initrd to acrtrimg).
If i manually create a PXE file for a specific host (in /tftpboot/pxelinux.cfg) similar to what the task manager creates, then it works as well:

DEFAULT send
LABEL send
kernel fog/acronis/acrmem
append initrd=fog/acronis/acrtrimg quiet vga=0x314

(I named this one 01-08-2e-5f-08-99-b7, because the mac is 08:2e:5f:88:99:b7)
The problem with this method is that i must manually create the host specific PXE file myself everytime i want to automatically boot a host into a custom program (for example Acronis True Image Home), and manually delete the PXE file after it has loaded. Using the task manager would be more convenient.

I tried to modify the ‘Test Disk’ task, and it works to some degree. The only problem is, that FOG won’t delete the task after it has finished (=the program booted successfully). I can kill the task on the ‘Active Tasks’ page though.
The only thing i modified was the $output string in both functions.include.php and Host.class.php. I didn’t touch the task name, variables or anything else.

$output = “DEFAULT send\n
[INDENT=2]LABEL send\n[/INDENT]
[INDENT=2]kernel fog/acronis/acrmem\n[/INDENT]
[INDENT=2]append initrd=fog/acronis/acrtrimg quiet vga=0x314”;[/INDENT]
[INDENT=2] [/INDENT]
For me it seems that only FOG’s own tasks can work properly (which uses the FOG ramdisk), because custom tasks can’t report the status to the FOG server, and thus the tasks will never finish.
Can anyone help me further with this?