@dws88 shutdown and restart options are for interaction with the fog client running on client computers and for wake on lan, not IPMI or any other hardware interface level of management.

also, you can create a custom css for the interface and tell fog to use it
FOG Configuration > Web Server > FOG_THEME
you’ll want to keep a backup copy of it, in case it get’s removed during an upgrade.

it’s worth mentioning that when moving files between linux and windows systems, file permissions are NOT preserved. just something to keep in mind

@Tom-Elliott i’m going to disagree with tom on the speed sacrifice with -19 setting. deploy speed, you won’t sacrifice much, and maybe even gain, but on capture it’s going to take quite a while longer. for me, i use -11.

@froydo to get it to work natively, you’ll need to buy a supported adapter. it looks like Dell makes one that will work:
http://en.community.dell.com/support-forums/laptop/f/3518/t/19621206

@sylkyls i am unable to reproduce this so far. what settings did you create the VM with?

@froydo this may seem like a silly test, but try having both plugged into the computer and ethernet. i’ve seen situations were a nic was supported by bios for pxe (and would load ipxe) but ipxe didn’t work well with that nic (so it wouldn’t work) but if another adapter was connected that ipxe DID work well with, it would switch over to using that one. after all, ipxe will attempt using all available network adapters once it’s loaded.

@Wayne-Workman i know that “back in the day” we had weird permissions issues that could happen if people created a user named “fog” when they set up the computer, and especially if they used that user to run the installer (this in spite of the instructions for setup explicitly saying not to create a user named “fog” because the installer would create one. of course, i discovered this bug the first time i set up a fog server, because that’s what i did…)

perhaps this is related since OP mentions logging in as the user “fog” which is typically not done

@froydo sorry to hear that. i must have been thinking of the XPS 14 or 15 (or maybe something completely different, i can’t be certain)

@froydo are you trying with a pxe supported usb network adapter, or are you still trying the dock? the adapter must be supported for boot by the computer’s firmware, and we have not established that this dock is.

@froydo i believe i’ve worked on that model before. it only supports pxe with a supported usb nic, and i think you even have to get the right usb port (that model has usb 3.0 on one side and 2.0 on the other, right?)

@John-Sayce update to RC13, problem will go away

@Tom-Elliott besides that, if you set a compression type as a default, the compression level only has to be relevant to that type you chose. so multiple settings are not needed. (though maybe we should add some helper text to tell people what is supported and recommended for each compression type?)

@sudburr the downloadable clonezilla boot cd, at the very least, will not include the needed program to decompress a zstd file, it does however contain the program to decompress a gzip file.

other important information to know

we used PIGZ because it was a parallel implementation of gzip. it took better advantage of multicore/multithread processors than standard gzip while maintaining complete compatibility with the widely used gzip compression.
gzip has been around for a long time and is a widely used standard. it, however, even using pigz, does not multi-thread well.
gzip/pigz compression can go from 1-9, or you can crank it to 11 for a very intensive compression at high cpu cost (there is no compression level 10)

zstd (zstandard) is a new type of compression. zstandard hasn’t been around long enough to become widely adopted, so if you ever want to use the files created by fog with another program, like clonezilla, that needs to be kept in mind. zstandard multi-threads well, and has better performance overall than gzip.
zstd compression can go from 1-22. 20-22 are “ultra” settings that will fail to work if the system you’re using to capture does not have a high amount of ram.

my personal experience in converting an image from pigz -6 compression to zstd -11 are as follows:
capture ~20% faster
size ~26% smaller
deploy ~36% faster

@rbotn so this is a M.2 SSD drive, correct? was the original one you created the image on also the same style of drive?

@Polii123 after you reset the encryption data, it takes a while for the clients to all check in and get up to date.

@george1421 i actually don’t think this is as massive of a rewrite/change as you imagine. Tom put a lot of flexibility in the code. I honestly think this could probably all be done with a plugin.

i mean, it’s beyond MY skill level. but someone could do it.

what are you using as your dhcp server?

@george1421 yuck, you’re right about the line wrap. it would look better and work just as well to make that:

set net0/next-server <otherPXEbootServerIP> 
set filename <whateverFile> 
chain tftp://<otherPXEbootServerIP>/<whateverFile> ||