• Discord

    Announcements
    1
    0 Votes
    1 Posts
    141 Views
    No one has replied
  • FOG 1.6.0-RC-7 Available

    Announcements
    1
    0 Votes
    1 Posts
    101 Views
    No one has replied
  • Upgrade 1.5.10.2253 to 1.5.10.2482

    Solved FOG Problems
    2
    0 Votes
    2 Posts
    262 Views
    Tom ElliottT

    @jmeyer This is a bug in schema step 284 on MySQL. Your data did not cause it.

    Cause: on MySQL, an ALTER TABLE re-checks the default of every column. Your hosts.hostSecTime still has the old default 0000-00-00 00:00:00. MySQL’s default sql_mode (NO_ZERO_DATE) refuses that default, so the step stops. MariaDB servers do not show the problem.

    Fix: https://github.com/FOGProject/fogproject/pull/1838 is merged into dev-branch. While the steps run, the schema updater now relaxes the zero-date check for its own session.

    The fix reaches the stable release on October 11. To continue now, install from dev-branch:

    cd /root git clone -b dev-branch https://github.com/FOGProject/fogproject.git fogproject-dev cd fogproject-dev/bin ./installfog.sh -y

    The failed step changed nothing in your database, so you do not need to restore the backup. The backup the installer made is still at /home/fogDBbackups/fog_sql_1.5.10.2482_20261009_113907.sql.

  • Unable to capture image on NVME systems since 1.5.10

    Solved FOG Problems
    7
    0 Votes
    7 Posts
    634 Views
    D

    @Tom-Elliott
    Hi, the new EXP_20261001-163131 work like a charm without the postinit workaround. Thank you!

  • FOG 1.6.0-RC-6 Available

    Announcements
    1
    0 Votes
    1 Posts
    122 Views
    No one has replied
  • FOG 1.6.0-RC-5 Available

    Announcements
    1
    0 Votes
    1 Posts
    120 Views
    No one has replied
  • "Bad response" sending a restart task

    Solved FOG Problems
    3
    0 Votes
    3 Posts
    256 Views
    A

    @Tom-Elliott I wondered if that was the case, thank you.

  • You are not running the most current version of FOG!

    Solved Bug Reports
    5
    0 Votes
    5 Posts
    610 Views
    Tom ElliottT

    This is a bug in the version check on 1.5.10.2482, not in your install. Your version is current, and you can ignore the banner.

    The check takes the first tag in GitHub’s tag list as the latest stable release. Newer tags (an archive tag and the 1.6.0 release candidates) now sort ahead of 1.5.10.2482, so every stable install shows this warning.

    The fix is merged to dev-branch (https://github.com/FOGProject/fogproject/pull/1823). It asks fogproject.org for the current versions instead. It ships in the next stable release.

  • 0 Votes
    15 Posts
    1k Views
    S

    Hi @Tom-Elliott
    After moving from RC-2 to RC-4 the plugin, the WinPE image and the step that closes the task at the end of the WinPE flow all kept working. Only the Apache part needed a change.

    With RC-4 the whole vhost sits inside FOG’s managed block, so my earlier Alias plus rewrite exception was gone and /fog/winpe_3400/wimboot started answering 308 (FOG’s rewrite rule sends it to the API). Instead of putting the exception back, I now serve the files from /winpe_3400/ (no /fog/ prefix), with an Alias and a <Directory> in a separate conf-available file enabled with a2enconf. FOG’s rewrite rule only matches /fog/, so it never sees these requests, and nothing in 001-fog.conf should need restoring after an update. The only change in the plugin is its WIMBOOT_HTTP_PATH constant.

    Checked after the change: the Latitude fetches wimboot, BCD, boot.sdi and boot.wim from the new path (all 200), WinPE starts, and a full deploy on the Latitude 3400 and one on an HP with the normal FOS/Partclone flow both completed and closed their tasks.

  • FOG 1.6.0-RC-4 Available

    Announcements
    1
    0 Votes
    1 Posts
    180 Views
    No one has replied
  • FOG 1.6.0-RC-3 Available

    Announcements
    1
    0 Votes
    1 Posts
    169 Views
    No one has replied
  • Task 0

    Solved FOG Problems
    50
    0 Votes
    50 Posts
    5k Views
    K

    @Tom-Elliott
    These are the two machines that were just cloned!

    I deployed the Snap-in three times:
    the two newly cloned machines and one old machine to see if any certificate issues arise with the old computers. All of them were assigned Image B.

    The computer, which has not yet been cloned, did not process the snap-in.

    ec06f2be-575a-48f2-9f68-3a9f156dd330-grafik.png

    ------------------------------------------------------------------------------ --------------------------------Authentication-------------------------------- ------------------------------------------------------------------------------ 28.09.2026 07:38:56 Client-Info Version: 0.13.0 28.09.2026 07:38:56 Client-Info OS: Windows 28.09.2026 07:38:56 Middleware::Authentication Waiting for authentication timeout to pass 28.09.2026 07:40:56 Middleware::Communication Download: http://192.168.0.196/fog/management/other/ssl/srvpublic.crt 28.09.2026 07:40:58 Middleware::Communication ERROR: Could not download file 28.09.2026 07:40:58 Middleware::Communication ERROR: Die Verbindung mit dem Remoteserver kann nicht hergestellt werden. 28.09.2026 07:40:58 Client-Info ERROR: Failed to authenticate, will not run Module Looper.

    78935d01-cc19-4dd8-b5bc-fb03e7885c58-grafik.png
    Resetting the encryption settings, deleting the snap-in that wasn’t running, and restarting it didn’t help…

    Rebooting of the pc helped

  • FOG 1.6.0-RC-2 Available

    Announcements
    1
    0 Votes
    1 Posts
    163 Views
    No one has replied
  • FOG 1.6.0-RC-1 Available

    Announcements
    1
    0 Votes
    1 Posts
    171 Views
    No one has replied
  • Capture stalls after approx 35% every time

    FOG Problems
    1
    0 Votes
    1 Posts
    118 Views
    No one has replied
  • Windows 11 Fog Client install failing with HTTPS

    Solved FOG Problems
    4
    0 Votes
    4 Posts
    353 Views
    Tom ElliottT

    @astrugatch I don’t think it matters really. The issue was more about the initial pinning of the certificate during the install process. After it is pinned I think this is the correct expectation (it should only communicate to the FOG server over HTTPS).

  • 0 Votes
    3 Posts
    309 Views
    M

    @Tom-Elliott
    Hi!
    I have updated to the latest dev-branch version.
    No more updating database … failed error.
    The multicast session closing the right way.

    Thank you!

  • Fog - Supported OS

    Solved FOG Problems
    4
    0 Votes
    4 Posts
    407 Views
    J

    This can be closed. Thank you.

  • Fogserver 1.6 - Agent 0.1.9

    Solved FOG Problems
    3
    0 Votes
    3 Posts
    321 Views
    J

    Awesome and thank you. Confirmed working.

  • 0 Votes
    3 Posts
    299 Views
    G

    Hi Tom,

    In my case the culprit was /images/postdownloadscripts/fog.postdownload.

    echo "Activating boot partition..." sfdisk --activate /dev/sda 1 echo "Rebooting..." reboot -f

    Fix was simply commenting out (or deleting) those lines. After cleanup the file looks like this:

    cat /images/postdownloadscripts/fog.postdownload #!/bin/bash ## This file serves as a starting point to call your custom postimaging scripts. ## <SCRIPTNAME> should be changed to the script you're planning to use. ## Syntax of post download scripts are #. ${postdownpath}<SCRIPTNAME>

    Thanks for the pointer, Tom — saved me from chasing GPT partition tables for a problem that had nothing to do with them.