The iPXE boot loop is kinda strange. I think I’ve never seen this! Why was default.ipxe missing in the first place. How did you get it back? Can you please post the content of that file here in the forum. You should find this text file in /tftpboot/default.ipxe on youf FOG server (18.104.22.168).
@Jarl2.0 If you are using zStd capture speed will be much slower than deploy speed. That is the nature of the compression tool. With gzip you don’t get as good of compression ratio or deploy speeds, but capture and deploy are similar in speed. For Zstd 11-13 is probably a pretty good range to stay in.
@guilherme.lima As Bob said, FOG is an imaging tool, you need/want a vdi (virtual desktop interface) environment.
You can diskless boot linux. That has been available for years. You just connect the user’s home drive to a server so all of their profiles info is saves between diskless boots. Its more trouble diskless booting MS Windows.
Instead of VDI, have you ever considered using a terminal server (both windows and linux)? Maybe explaining why you are trying to do this or what goal do you hope to achieve, can give me an idea how to answer you better.
i like the idea of using /quit instead of /shutdown and getting sure the shutdown is a real one with shutdown -s -t 0 -f
I never used the chkdsk portion but it would not do any harm but wasting time :p… well i do a defrag instead.
If there is still a hdd i think it would make sense to defrag before you write cereal to it
Hello. I know this is quite an old Post but it is quite close to my issue. I managed to deploy a dualbootloader (grub legacy) with a Ubuntu and a Windows 7 OS. Now i just wanna replace the Windows 7 with another Image but i wanna keep the existing Bootloader and all other OS in it. Is there a way to deploy a single OS into this bootloader or do i have to deploy the whole thing again (Grub+Ubuntu+ Windows 7)? Also is it possible to deploy an OS and then integrate it into the original FOG Bootmenu (Not just an iso i mean the native os)?
.WIM is only used with Windows Image. These files cannot simply be added to the FOG Server and used as the image data on the server. Fog uses Partclone to create its images, and partclone is NOT the same as WDS/MDT/WIM files. We store the files with the .img extension so people know it’s an image file, but these are compressed (typcially). We don’t add the compression extension as users are now able to select their own method of compressing the image.