• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Popular
    Log in to post
    • All Time
    • Day
    • Week
    • Month
    • All Topics
    • New Topics
    • Watched Topics
    • Unreplied Topics
    • All categories
    • F

      Fog 1.6.0.14 Master Storage Node not handing off to Slave Storage Nodes

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      17
      0 Votes
      17 Posts
      201 Views
      Tom ElliottT

      @FlareImp Great, thank you for testing it.

      Both fixes are now in dev-branch. Run updatefog.sh --branch dev-branch again on the main server to get them:

      The MAC tab shows the primary MAC as selected. A location whose Storage Group has no nodes no longer stops the PXE boot. FOG uses its own node and writes one line to the error log that names the location.

      Let me know how the other sites do, and whether the deploys spread across the nodes.

    • L

      Feature request: a way to handle USB Ethernet adapters shared between many hosts

      Watching Ignoring Scheduled Pinned Locked Moved Feature Request
      9
      0 Votes
      9 Posts
      78 Views
      Tom ElliottT

      @lperoma The next stable will be auto promoted from dev-branch -> stable on December 11th at some point in the day.

      11th of every month is when dev-branch fixes get pulled into stable.

      As to the “Version” it will be, it’s however many commits since.

      Right now .14 means there were 14 commits after master containing 1.6.0, 158 is the current stable branch meaning 158 total commits since it’s original release.

      Some months will be less, some will be much more.

      If you wanted you can install dev-branch but I understand the feeling of “well it’s not stable”.

    • rogalskijR

      FOG Agent on new image PC not communicating with server

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      2
      0 Votes
      2 Posts
      33 Views
      Tom ElliottT

      @rogalskij The host shows the agent enrolled, but it has not checked in since you approved it. On 0.1.24, two things cause that.

      Audit mode. If this PC is a reference machine in audit mode, or has not finished OOBE, the agent waits on purpose. It does nothing until Windows setup finishes. Check HKLM\SYSTEM\Setup\State\ImageState. Any value other than IMAGE_STATE_COMPLETE means the agent is waiting. It starts by itself after Sysprep and OOBE complete. You can capture the image with the agent in it. On each deployed PC, the agent sees a different hardware identity. It drops the reference machine’s certificate and enrolls as itself. An http:// server address. The server knows the agent only by its client certificate, and that works only over https. With an http:// address, enrollment works, but every check-in after approval fails. Install the 0.1.25 MSI by hand: it switches an http:// address to https:// on its own. Or reinstall with SERVER=https://your-server/fog.

      C:\ProgramData\FOG\fog-agent.log tells you which one it is. “Windows setup has not finished” means the first. “server refused this certificate” means the second. Please post that log if neither line is there.

      Two side notes. The agent opens no listening port, so it needs no firewall rule. The “No such device or address” ping status is the server failing to resolve the host name. It is not related to the agent.

    • C

      1.6.0.158 unable to approve agent

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      12
      0 Votes
      12 Posts
      103 Views
      Tom ElliottT

      @chscduo Glad it works, and thanks for running each check so quickly.

      The fix is in dev-branch, so the next FOG update includes it. The update replaces the helper you installed by hand with the same code, so you have nothing to undo.

    • 1 / 1