Categories

• Technical Help

  Get help with your FOG system.

  FOG Problems Hardware Compatibility Windows Problems Linux Problems Mac Problems General Problems
  13k Topics

  115k Posts

  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!

• Announcements

  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!

• General Topics

  View tutorials or talk about FOG in general.

  General Tutorials
  2k Topics

  19k Posts

  R

  Now I read the AI summary and got what I need:

  It stores one row for each address in the hostNetwork table. Limits of this method The sleeping host must run fog-agent. The server uses the sleeping host’s own last report to find its subnet. A host with the legacy FOG Client, or with no client, has no rows, so the relay cannot help it. The old path still runs for it.

  So If I populate the hostNetwork table for the hosts that I need manually, It will work. Thank you for the details.

• Developers

  Report bugs, request features, or get the latest progress.

  General Feature Request Bug Reports
  2k Topics

  21k Posts

  S

  Hi @Tom-Elliott
  Here’s the table comparison you asked for:

  Win10 (23H2), SSSTC drive:
  label: gpt, protective MBR
  p1: start=2048 size=204800 EF00 EFI
  p2: start=206848 size=32768 0C01 MSR
  p3: start=239616 size=498573824 (237.7 GiB) 0700 Basic Data
  p4: start=498813440 size=1304576 (637.0 MiB) 2700 WinRE
  Free: 2157 sectors (1.1 MiB), no problems found

  Win11 (25H2), Toshiba drive:
  label: gpt, protective MBR
  p1: start=2048 size=204800 EF00 EFI
  p2: start=206848 size=32768 0C01 MSR
  p3: start=239616 size=498344448 (237.6 GiB) 0700 Basic Data
  p4: start=498584064 size=1533952 (749.0 MiB) 2700 WinRE
  Free: 2157 sectors (1.1 MiB), no problems found

  Type GUIDs, attributes, partition order, and start sectors for p1/p2/p3 are identical between both. The only difference is where the p3/p4 boundary falls — Win11’s WinRE partition is ~112MB larger, which just shifts that one boundary. No extra/hidden partitions, no reordering, no odd attributes on either side, no MBR anomaly (both show “protective” cleanly). I don’t see anything in the table itself that looks like a red flag.

  Given how clean this diff is, I’m not expecting the bisection’s first step (sgdisk -Z, table-only) to change anything, but running it now anyway as instructed. Will report whether F2/Setup opens after that, and if not, move to zeroing the ESP start next.

  Thanks