• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. scottmcmullan8
    3. Topics
    S
    • Profile
    • Following 0
    • Followers 0
    • Topics 6
    • Posts 30
    • Groups 0

    Topics

    • S

      FOG::HostnameChanger Domain Error! ('Unknown Error' Code: 2)

      Watching Ignoring Scheduled Pinned Locked Moved FOG Problems
      5
      0 Votes
      5 Posts
      2k Views
      S

      Ah ok I understand now - brilliant this has resolved the issue I wasn’t aware that specifying the default OU would have a knock on effect.

      Thanks again for your help

    • S

      FOG PXE boot

      Watching Ignoring Scheduled Pinned Locked Moved FOG Problems
      8
      0 Votes
      8 Posts
      4k Views
      Jaymes DriverJ

      Chad is on the right track I really seem to be slacking lately, normally I am the first one to recommend the DNSMasq, I have to use it here in my novell network because we use Netware 6.5 and it has a limited number of characters that can be supplied for the boot file name. DNSMasq allows me to circumvent the system and provide the correct boot file.

      You can use this guide here [url]http://fogproject.org/wiki/index.php/Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server#DNSMASQ_settings_for_iPXE[/url]

      It will aid you in setting up DNSMasq, and of course if you have problems just come back and let us know.

    • S

      Certain machines not PXE booting after upgrade

      Watching Ignoring Scheduled Pinned Locked Moved FOG Problems
      7
      0 Votes
      7 Posts
      4k Views
      Jaymes DriverJ

      [quote=“scottmcmullan8, post: 33863, member: 24964”]Another update - it appears when the machines that aren’t working are trying to PXE boot they are using Intel Boot Agent Version 1.3.24 however the machines that are working are using a Intel PXE boot agent?[/quote]

      Look for Bios Updates/Firmware updates for the machines and see if that has any affect.

    • S

      Progress Bar - Fog 1.1.2 - Storage Nodes

      Watching Ignoring Scheduled Pinned Locked Moved FOG Problems
      1
      0 Votes
      1 Posts
      716 Views
      No one has replied
    • S

      Help - Invalid Mac Address

      Watching Ignoring Scheduled Pinned Locked Moved FOG Problems
      18
      0 Votes
      18 Posts
      7k Views
      C

      Working great now after moving to the Trunk. I was pleasantly surprised with how well the upgrade process worked. All I had to do after the update was reconfigure some of my settings for dnsmasq and then I was up and running.

      Thank you for your help @Wayne-Workman !

    • S

      Help changing from pxelinux.0 to undionly.kpxe (Boot Menu)

      Watching Ignoring Scheduled Pinned Locked Moved Linux Problems
      7
      0 Votes
      7 Posts
      7k Views
      Tom ElliottT

      I’ve now added the ability to add “individual” password login settings to menu items
      My current menu that is tested and working, although very minimal, is:
      [code]isset ${userID} && goto do_me || goto MENU
      :do_me
      kernel bzImage root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=10.10.10.1 web=10.10.10.118/fog/ consoleblank=0 loglevel=4 type=down img=win7actsysprep ftp=10.10.10.118 imgType=n osid=7 storage=10.10.10.118:/images capone=1 imgFormat=0
      imgfetch init.xz && boot || goto MENU
      :MENU
      menu
      item --gap Please Select one of the images below
      item fog.local Boot from hard disk
      item d101_64 D101 Base Image (64 bit load)
      item return Return to main menu
      choose --default fog.local target && goto ${target}
      :fog.local
      sanboot --no-describe --drive 0x80 || goto MENU
      :d101_64
      chain -ar ${boot-url}/service/ipxe/advanced.php?login=1 || goto MENU
      :return
      chain http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac} || goto MENU
      autoboot[/code]

      Notice the :d101_64 how it has the [B]chain -ar ${boot-url}/service/ipxe/advanced.php?login=1 || goto MENU[/B] ?That’s all that’s needed to have a “login” for your menu item. Notice the top where it says :do_me? This is important to note that it’s ABOVE the menu generation part of the advanced menu setup.

      As I stated, this is very basic, but a method to :sort: the different functions could be:
      [code]isset ${userID} && iseq ${bootnum} 1 && goto do_me ||
      isset ${userID} && iseq ${butnum} 2 && goto do_me2 ||
      goto MENU
      :do_me
      kernel bzImage root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=10.10.10.1 web=10.10.10.118/fog/ consoleblank=0 loglevel=4 type=down img=win7actsysprep ftp=10.10.10.118 imgType=n osid=7 storage=10.10.10.118:/images capone=1 imgFormat=0
      imgfetch init.xz && boot || goto MENU
      :do_me2
      kernel bzImage root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=10.10.10.1 web=10.10.10.118/fog/ consoleblank=0 loglevel=4 type=down img=blahblah ftp=10.10.10.118 imgType=n osid=7 storage=10.10.10.118:/images capone=1 imgFormat=0
      imgfetch init.xz && boot || goto MENU
      :MENU
      menu
      item --gap Please Select one of the images below
      item fog.local Boot from hard disk
      item d101_64 D101 Base Image (64 bit load)
      item return Return to main menu
      choose --default fog.local target && goto ${target}
      :fog.local
      sanboot --no-describe --drive 0x80 || goto MENU
      :d101_64
      set bootnum 1
      chain -ar ${boot-url}/service/ipxe/advanced.php?login=1 || goto MENU
      :d102_64
      set bootnum 2
      chain -ar ${boot-url}/service/ipxe/advanced.php?login=1 || goto MENU
      :return
      chain http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac} || goto MENU
      autoboot[/code]

    • 1 / 1