Your best bet to have a standalone solution is to deploy the image to a temp computer and then capture the image with clonezilla. Both FOG and Clonezilla use partclone to capture the image, but FOG uses an image compression format not understood by partclone. You won’t have the FOG service capabilities with clonezilla but imaging will work standalone.
@sebastian-roth It appears the -100 -200 -300 numbering is based on the FC release and not to indicate a patch level.
So that means I’m back to trying to figure out how to diff all of the files between FC version and linux version of 4.13.9.
@rayco said in Customized image of Windows10 1803 RS4, partition resize issue:
I’m traying diferents methods but with unlucky results.
What exactly have you tried and which errors occurred? We can’t help without knowing more details from you.
Hi there, we have trouble installing Fog on Ubuntu 18.04.1, see
https://github.com/FOGProject/fogproject/issues/258
Do you have an estimate when Ubuntu 18 will be supported out of the box?
@louis-csusa @George1
Hi Louis,
George1421 created a great post, scroll down to part 2a. You will see the info you need. https://forums.fogproject.org/topic/7727/building-usb-booting-fos-image/3 I added George Incase there’s any new info. Maybe Fog will support APFS? Since I seen reports that Clonezilla can imaged using DD. Also this usb script does not support the new T2 15inch MacBook Pro keyboard. However using a usb hub to connect an usb Ethernet, keyboard I was able to pxe boot and register it. Please note you will need to disable secured boot on an T2 chip Mac.
@briancurry said in PXE Boot Errors:
Now the endpoint boots to what looks like the FOG imaging menu but then goes away after about 2 seconds.
There is a boot menu timeout that FOG has. The value is set in the FOG-Settings menus (sorry don’t remember off the top of my head). If you hit the up or down arrow within the 2 seconds you should be able to navigate the fog ipxe menu
