• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Mikeee89
    3. Topics
    M
    • Profile
    • Following 0
    • Followers 0
    • Topics 3
    • Posts 9
    • Groups 0

    Topics

    • M

      FOG 1.6.0.158 - Multicast error (session has already started with 0 clients)

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      3
      0 Votes
      3 Posts
      13 Views
      Tom ElliottT

      @Mikeee89 Thanks for the log, it shows the cause. The first line of the udp-sender command has --max-wait 10. That value is seconds, not minutes.

      The Session Timeout field on the Multicast page asks for minutes, but FOG stored the number as seconds. So your 10-minute session waited only 10 seconds after it started. After that, the PXE menu treats the session as already started and refuses the join, even with 0 clients connected.

      The fix is in https://github.com/FOGProject/fogproject/pull/2114 and goes to dev-branch.

      Until you update, either of these works on your current install:

      Enter the timeout in seconds. For 10 minutes, enter 600. Or leave the timeout blank. FOG then uses the global setting FOG_UDPCAST_MAXWAIT (in minutes) and converts it correctly.

      Cancel the stuck session first, then create a new one.

    • M

      Multicast: "No Active Task found for Host" on 1.5.10.2482 despite #1391 — msClients stays 0

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      3
      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!

    • M

      PXE boot failed some computers

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      7
      0 Votes
      7 Posts
      3k Views
      M

      I had some problems with AMD computers and found this

      https://knowledge.broadcom.com/external/article/269598/firmware-settings-for-ipxe-boot-on-lenov.html

      "Resolution
      During iPXE troubleshooting it has been determined that the following settings in Firmware/BIOS for Lenovo Thinkpad L15 Gen 3 need to be adjusted to allow for a successful iPXE boot:

      Memory protection - Set to ‘disabled’
      AMD V™ Technology - Set to ‘disabled’

      There also may be certain environments that require further changes. For further information contact Lenovo Support.

      Additional DS (Deployment Solution) and GSS (Ghost Solution Suite) files can be found in KB article Updated 64-bit ipxe.efi (ipxe v1.21.1+) binaries

      NOTE: The files in the above KB article are not a pointfix but are new version binaries signed by Microsoft"

      Leaving it here, because it solved my problem and it sounds like your problem

    • 1 / 1