• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. forte647
    3. Best
    F
    • Profile
    • Following 0
    • Followers 0
    • Topics 7
    • Posts 22
    • Best 3
    • Controversial 0
    • Groups 0

    Best posts made by forte647

    • RE: Disabling password requirement in boot menu + rearranging boot menu

      @forte647 said:

      Deleting those lines causes my Multicast Join entry to not work (like I can select it but it just knocks me back to the first menu). Is there a way to hard code the user and pass into the param of multijoin? If so, what would that look like? Like if I wanted to hardcode username “fog” and password “password”.

      Sorry for the double post, but I got ballsy and tried it myself and this worked for me. My multijoin params are:

      params
      param mac0 ${net0/mac}
      param arch ${arch}
      param username fog
      param password password
      param sessionJoin 1
      isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
      isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme

      got rid of the first login line (I guess that’s the login prompt) and then changed the user/pass lines from ${username} to a username I wanted (default account fog) and its ${password} “password”.

      Changing the default entry also worked, although in my mind I really wanted to arranged differently, but that’s okay too.

      Thank you, guys. 🙂

      posted in FOG Problems
      F
      forte647
    • RE: DHCP failed - undionly.pxe

      My company recently switched to Probook 455 G3s, and I had the same issue after the switch. Something about the NIC in these laptops isn’t playing nice with undionly.pxe? I switched my boot file to ipxe.pxe and it worked. So maybe try using ipxe.pxe and see what happens.

      posted in FOG Problems
      F
      forte647
    • RE: Multicasting without registration in 1.2.0

      @Wayne-Workman said:

      If you liked that, FOG Trunk will blow your socks off. 👍

      As far as I know, imaging unregistered computers using FOG Trunk only works with Unicast.

      You can set (in storage management) how many active tasks are allowed. I keep mine set at 2. Then you network boot all machines. 2 will start. The rest wait in line and automatically start.

      Thanks for the suggestion to move to trunk, and thanks Quazz for the clarification on whether or not multicast worked. This is exactly what I wanted/needed! 🙂

      For any wayward googlers:
      I upgraded my install to trunk using these instructions: https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk pretty straight forward.

      After the upgrade completed, I went back to image management in the web gui, selected multicast image, started a new session for the amount of clients I wanted, netbooted each client to fog’s boot menu and selected join multicast session. it goes when the specified number of clients connect.

      Wonderful. Thanks a lot, guys. 🙂

      posted in FOG Problems
      F
      forte647
    • 1 / 1