• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. eric0626
    3. Topics
    E
    • Profile
    • Following 1
    • Followers 0
    • Topics 3
    • Posts 27
    • Groups 0

    Topics

    • E

      Upgrading from trunk 7394 (1.2.0) to latest 1.5.2

      Watching Ignoring Scheduled Pinned Locked Moved General
      3
      0 Votes
      3 Posts
      607 Views
      E

      @tom-elliott Great! Thank all of you for the great work!! πŸ™‚

    • E

      Chainload PXE from iPXE

      Watching Ignoring Scheduled Pinned Locked Moved FOG Problems
      12
      0 Votes
      12 Posts
      8k Views
      E

      Hello ALLLLLLLLLL!
      I did it!!! πŸ˜† πŸ˜† πŸ˜†
      The problem was when the client executes the chain command, it sends another request to the DHCP server, and it points the client back to the same iPXE server because that’s what the DHCP server has.

      The solution is to explicitly specify the PXE server with command β€œset net0/next-server iPXE-server-ip”.
      Please see below for my screenshot.
      0_1458935856581_upload-77255287-209f-40df-bbc4-b1e534ccd24a

      Thank you guys for all the help!!! πŸ˜€

    • E

      PXE boot to FOG 1.2.0 from FOG 0.32 menu

      Watching Ignoring Scheduled Pinned Locked Moved General
      33
      0 Votes
      33 Posts
      20k Views
      E

      I did a fresh installation of FOG 1.2.0 (without updating svn) and chainloading pxe is working now.
      I think there may be some updates in the svn which stop chainloading pxe. o_O

    • 1 / 1