@hvaransky if you’re wanting high compression, you’ll want to switch to zstd. it’s faster and compresses better. don’t bother with maxing it out though, you’ll triple the time it takes to compress and only save a few % in size. comparing gzip -6 to zstd -11 ( our recommended settings ) my testing showed zstd was 10% faster at capture, 26% smaller in final file size, and 36% faster on deployment

@compman while that’s true, in practice zstd at a higher compression level will return a faster overall process when the bottleneck is the network.

when you create the VM, classify it as a windows 7 machine in it’s settings, even though you’re going to put windows 10 on it. also, if you’re going to use a vm to create your golden image for physical hosts, make sure you don’t put the vmware tools on it. it can make your hosts act in ways you don’t want, like laptops that will never sleep.

@tcs_taylor this doesn’t sound like expected behavior. we’re probably going to need help from the other developers if we can confirm this bug. we’ll also need details on exactly what version of fog you’re running

@tcs_taylor in your advanced menu text field you can put something like this:

:MENU
menu
item --gap -- ---------------- iPXE boot menu ----------------
item return return to previous menu
item Win7SP1x64 Win7 SP1 64bit Sysprepped
choose --default return target && goto ${target}

:Win7SP1x64
kernel bzImage root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp web=${fog-ip}/fog/ consoleblank=0 loglevel=4 type=down img=Win7SP1x64 ftp=${fog-ip} imgType=n imgPartitionType=all osid=5 storage=${fog-ip}:/images/ capone=1
imgfetch init.xz
boot ||
goto MENU
:return
chain http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac} ||
prompt
goto MENU

@tcs_taylor as an alternative to modifying the code, you can create an advanced menu that is only the deploy tasks for the desired images. this will allow the menu to persist seamlessly through upgrades

@foglalt if an imaging task is taking place, the database is updated by the computer being imaged with the progress. you know the progress bar that says how complete the task is? that’s in the database.

@foglalt said in Disappearing hosts from host list:

as far as I know about fog database updates are done upon things finish and starting point. I mean if i change mac during deployment, database is updated on change and upon task finish

actually, it’s updated every couple of seconds during the task with the progress of the task.

can we just rename it to “PXE menu only”? because i rely on that to give our student workers access to only the features of fog that you can use from the ipxe menu. (i would remove the mobile interface manually after updates)