• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Idea: Two "next-servers" coexisting on the same vlan

Scheduled Pinned Locked Moved
General
3
23
4.5k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • D
    DBCountMan @george1421
    last edited by Apr 14, 2022, 6:10 PM

    @george1421 Would it be easier to re-run the FOG setup script and just change the FOG IP and disable DHCP? I could also define our existng DHCP server during the setup.

    1 Reply Last reply Reply Quote 0
    • S
      Sebastian Roth Moderator
      last edited by Apr 15, 2022, 6:23 PM

      @brakcounty said in Idea: Two "next-servers" coexisting on the same vlan:

      Would it be easier to re-run the FOG setup script and just change the FOG IP and disable DHCP? I could also define our existng DHCP server during the setup.

      Probably good idea to check out the docs on changing a FOG server’s IP: https://docs.fogproject.org/en/latest/reference/change_fog_server_ip_address.html

      Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

      Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

      D 2 Replies Last reply Apr 16, 2022, 5:03 PM Reply Quote 0
      • D
        DBCountMan @Sebastian Roth
        last edited by DBCountMan Apr 16, 2022, 11:18 AM Apr 16, 2022, 5:03 PM

        @george1421
        Just tested it with my USB boot method to load ipxe in a vm, the menu item was present but when I tried to boot it, I got this error:
        Screenshot from 2022-04-16 13-01-21.png

        These are the parameters I have set as per the your post:
        set next-server our SCCM server

        iseq ${platform} efi && goto is_wds_efi || goto is_wds_bios

        :is_wds_efi
        set wds-bootfile \boot\x64\wdsmgfw.efi
        goto wds_boot

        :is_wds_bios
        set wds-bootfile \boot\x64\wdsnbp.com

        :wds_boot
        set filename ${wds-bootfile}
        set net0.dhcp/filename ${wds-bootfile}
        set proxydhcp/filename ${wds-bootfile}
        chain tftp://${next-server}${wds-bootfile} || goto Menu

        After looking at the folder structure, I see a folder that our sysadmin setup that has a folder called Boot, but no file called “wdsmgfw.efi” exists.

        D G 2 Replies Last reply Apr 16, 2022, 5:24 PM Reply Quote 0
        • D
          DBCountMan @DBCountMan
          last edited by Apr 16, 2022, 5:24 PM

          Actually found the files but it keeps saying the same error message. I corrected the path in the script. We disabled the PXE service on the SCCM server, so I am wondering if that also disabled TFTP which is why the files can’t be found.

          G 1 Reply Last reply Apr 16, 2022, 8:03 PM Reply Quote 0
          • G
            george1421 Moderator @DBCountMan
            last edited by Apr 16, 2022, 6:55 PM

            @brakcounty said in Idea: Two "next-servers" coexisting on the same vlan:

            but no file called “wdsmgfw.efi” exists.

            So if you search that path what files end in .efi? Is there something like bootmgr.efi ?? I don’t have SCCM so I can’t reverse engineer the answer.

            Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

            1 Reply Last reply Reply Quote 0
            • G
              george1421 Moderator @DBCountMan
              last edited by Apr 16, 2022, 8:03 PM

              @brakcounty said in Idea: Two "next-servers" coexisting on the same vlan:

              Actually found the files but it keeps saying the same error message.

              From a windows computer install the tftp client feature and then temporarily drop the windows firewall (or do this from the fog server) use tftp get command to see if you can pull the file from the wds/sccm server. That will tell you if the needed service is running.

              Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

              D 1 Reply Last reply Apr 18, 2022, 1:13 PM Reply Quote 0
              • D
                DBCountMan @george1421
                last edited by Apr 18, 2022, 1:13 PM

                @george1421 We just re-enabled PXE on the SCCM server so it takes a minute to reinstall the features. I was going to run Wireshark to see what is being requested from where. I did that testing ipxe in my lab and found out that ipxe requests autoexec.ipxe if you don’t embed or specify a menu file. Learn something new everyday.

                D 1 Reply Last reply Apr 18, 2022, 6:40 PM Reply Quote 1
                • D
                  DBCountMan @DBCountMan
                  last edited by Apr 18, 2022, 6:40 PM

                  I think when we disabled PXE on the WDS it also removed everything else that made it work. I think that includes the proxyDHCP service. Our prod DHCP server had our WDS server’s IP listed as DHCP Relay. But I don’t think we still need PXE if we chain from FOG.

                  1 Reply Last reply Reply Quote 0
                  • D
                    DBCountMan
                    last edited by DBCountMan Apr 18, 2022, 1:28 PM Apr 18, 2022, 7:28 PM

                    So while the script @george1421 made in that post didn’t work right and threw errors, I have FOG scripted to allow to drop to shell if an error occurs. Once I got into the shell, i just typed “autoboot” and hit enter. I then got prompted to press Enter to boot WDS. Then it stopped here. I think I still have to define a boot.wim on the WDS Properties. But I feel like I am getting closer. I could just throw in the “autoboot” command under the FOG’s ipxe item setting parameters.
                    VirtualBox_Test64_18_04_2022_15_27_17.png

                    G 1 Reply Last reply Apr 18, 2022, 7:46 PM Reply Quote 0
                    • G
                      george1421 Moderator @DBCountMan
                      last edited by Apr 18, 2022, 7:46 PM

                      @brakcounty OK As I mentioned before SCCM has a service that I thought was called netboot or something like that, if you stop that service it will turn off the proxydhcp service (udp port 4011) on the server. That functions much like the dnsmasq service does to provide pxe boot infomation only leaving the rest of the settings to come from your dhcp server. Yes you would add the proxydhcp server as the last server in the dhcp-helper/relay service on your IP router.

                      So having the proxydhcp option in one method, the other method is using dhcp options 66 and 67. To use this option with SCCM you need to set dhcp option 66 to the IP address of the SCCM server and dhcp option 67 to the boot file to use. Once we can get this method to work (without FOG in the picture) then we can introduce FOG into the chain. So IMO you need to find the name of the boot file that ends in .efi That file should be on the SCCM server, I think in the boot directory, but I can’t remember from that long ago when I last touched SCCM.

                      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                      D 1 Reply Last reply Apr 18, 2022, 8:03 PM Reply Quote 0
                      • D
                        DBCountMan @george1421
                        last edited by DBCountMan Apr 18, 2022, 2:10 PM Apr 18, 2022, 8:03 PM

                        @george1421 Actually since I added a standard boot.wim file from a Windows install disc, pxe booting works as it did before we disabled PXE on the WDS server. Now its just a matter of finding the original custom boot.wim we had in place. Then we can move on to modifying the os.WDS-Boot parameters to make it work from FOG. If I remember correctly, FOG also works with the autoboot command. I remember I saw this when I was experimenting at the ipxe shell from a remote location when I loaded ipxe from USB. I typed autoboot and since the next-server was predefined as my FOG IP, it loaded FOG.

                        As far as finding the efi file, I did find it. I see this error now followed by two No such file or directory errors when attempting to load from the FOG menu:
                        tftp://wds ip/SMSBoot/x64/wdsmgfw.efi…Error 0x3d126083

                        Followed the link and it is “Error: Inappropriate I/O control operation”.

                        D 1 Reply Last reply Apr 19, 2022, 5:06 PM Reply Quote 0
                        • D
                          DBCountMan @DBCountMan
                          last edited by DBCountMan Apr 19, 2022, 11:07 AM Apr 19, 2022, 5:06 PM

                          This post is deleted!
                          1 Reply Last reply Reply Quote 0
                          • D
                            DBCountMan @Sebastian Roth
                            last edited by Apr 19, 2022, 7:33 PM

                            @sebastian-roth Where do I “use –recreate-CA and –recreate-keys keys” switches? Like this?
                            .\installfog.sh --recreate-CA --recreate-keys?

                            1 Reply Last reply Reply Quote 0
                            • 1
                            • 2
                            • 1 / 2
                            1 / 2
                            • First post
                              20/23
                              Last post

                            171

                            Online

                            12.1k

                            Users

                            17.3k

                            Topics

                            155.3k

                            Posts
                            Copyright © 2012-2024 FOG Project