Categories

  • Get help with your FOG system.
    FOG Problems Hardware Compatibility Windows Problems Linux Problems Mac Problems General Problems
    13k Topics
    115k Posts
    V

    @Tom-Elliott When searching for a solution I recall seeing a related post on GitHub but that was not me. Today I created a new VM that was 70GB with 2GB EFI partition and after sysprep and it yielded the similar resize error during capture.

    I then tried Windows 11 25H2 June 2026 Build 26200.8655 with 60GB VM and it generated the resize error. 25H2 with 60GB VM and 2GB EFI also generated the resize error after sysprep during capture.

    The AI suggested defrag C : /X

    I ran the defrag before sysprep and capture was succesful.

    The pre optimization total fragmentation was 22% and post defragmentation it was also 22%

    To my understanding the /X flag consolidates free space. How was this the solution to my issue?

    Per the FOG Project wiki I found that defrag is recommended before sysprep:

    "…
    Before Running Sysprep
    Other steps to consider are:

    Run Chkdsk /f /p prior to imaging
    Defrag the drive
    Make sure 2gb of disk space is free or the NTFSresize will fail
    Make sure the FOG service is installed and properly configured
    Update your hostnamechange.dll file
    …
    "
    https://wiki.fogproject.org/wiki/index.php/Client_Setup

  • Get the latest news on what's happening.
    Security Advisories
    184 Topics
    825 Posts
    A

    @Tom-Elliott I really appreciate that you are putting effort into providing more frequent releases, which makes it easier for everyone to deploy new security fixes in time. Keep up the good work!

  • View tutorials or talk about FOG in general.
    General Tutorials
    2k Topics
    19k Posts
    C

    Hi there !

    I’ve been working the last few days on a fog docker image. I think it have reached a point were it could be great for me to get some testing and report (especially with the unfs3 server). The image seems to work fine, but i did only test it in a small home lab, and didn’t try things like snapping, wol, ping host and such. Consider this a work in progress.

    I’m very bad at readme and such (boring!) but i did try to write a small one which should help to understand how it work (and the challenge behind this image). It is available on my github.

    I can’t wait for your feedback, and i hope you’ll like it ! In the meantime, here is a docker compose sample to get up and running in a few seconds (i hope!):

    services: fog: image: cpasjuste/fog restart: unless-stopped #privileged: true # for nfs-kernel-server mode environment: HTTP_ADDRESS: 192.168.0.83 # also used for ftp/tftp/nfs/... # you can use a custom http port, but storage "Node Disk Usage" # and "Bandwidth" graphs wont display correctly. # this can be fixed with a reverse proxy (or use port 80) HTTP_PORT: ${HTTP_PORT:-9445} PHP_FPM_PORT: ${PHP_FPM_PORT:-9444} # listen on localhost, no need to open port in firewall WEB_PASSWORD: ${WEB_PASSWORD:-password} # web user (fog) password MYSQL_PASSWORD: ${MYSQL_PASSWORD:-dockerfogsql} # mysql user (fog) password # builtin storage (shell/nfs/ftp/tftp...) password # use alphanumeric because it is not handled correctly by fog (php?) STORAGE_PASSWORD: ${STORAGE_PASSWORD:-dockerfogstorage} USE_UNFS3: true # use userland nfs server (no need for privileged mode) volumes: - database:/var/lib/mysql - /images:/images # on host: sudo mkdir /images && chown -R 1000:1000 /images #- /lib/modules:/lib/modules:ro # for nfs-kernel-server mode network_mode: host # needed ports: https://github.com/Cpasjuste/docker-fog/blob/main/README.md volumes: database:

  • Report bugs, request features, or get the latest progress.
    General Feature Request Bug Reports
    2k Topics
    21k Posts
    K

    @Valer Hi Valer,

    You can see my tutorial on using Secure boot with Shim, and my thoughts on what 2.0 means for Secure Boot with FOG here: http://forums.fogproject.org/post/158170

96

Online

12.7k

Users

17.6k

Topics

156.7k

Posts