@george1421 Yes I can. Here is the code that I use to boot from SCCM
DEFAULT menu.c32
MENU TITLE SCCM PXE Server
LABEL wds
MENU DEFAULT
MENU LABEL SCCM
KERNEL pxeboot.0
LABEL linuxpxe
MENU LABEL FOG Image Capture
KERNEL pxechain.com
APPEND 10.0.1.203::undionly.kpxe
LABEL abort
MENU LABEL Exit PXE
Kernel abortpxe.0
I successfully booted into the FOG server both by the natively installed undionly.kpxe as well as the version @george1421 had me download. But in order to do so I had to turn off PXE on the SCCM server. If it is easier to create a menu item to point to the sccm server from FOG I am open to this idea as well. I am booting from a Dell Latitude E5470.
@george1421 said in Edited undionly.kpxe now receive params: command not found:
@jlober1981 No I don’t feel that its a fog server issue just yet (You could test by changing /temp/ your dhcp option 66 and 67 to the fog server IP and undionly.kpxe and see if you can boot).
Please tell me a bit more about what you are trying to pxe boot, that system is hanging with the ipxe kernel.
Bear with me as I am quite new to FOG, but I am trying to setup FOG to be able to capture images of new and used Dell Laptops. The ONLY configurations that I have changed on the FOG server is the undionly.kpxe file based on suggestions shown here. If you need more detailed information please specify and I can gladly provide whatever you are looking for to help get this running. Thanks!
Yes I downloaded your file and received the same error message. Is it perhaps a misconfiguration on my FOG server?
@george1421 said in Edited undionly.kpxe now receive params: command not found:
@jlober1981 Ok the test worked correctly in our test lab.
Some of the settings have changed on the rom-o-matic since that first tutorial was written. Its mostly the same but a few extra options have been added.
Please test this file: 0_1483986244383_gundionly.kpxe and let me know how it works, be aware that I changed the name to gundionly.kpxe to not conflict with the official undionly.kpxe file.
When I tested, I just dropped that file on our test syslinux pxe boot server and then changed the dhcp option 67 to load that file instead of pxelinux.0. It worked right out of the box and loaded the fog pxe menu. I do have to admit I did not try anything past there, but if you can get into the ipxe fog menu that was more than you had before.
If it works correctly in your environment I’ll post the instructions on how to recreate it.
Thanks! But I am receiving the same error as shown in the picture.
@george1421 said in Edited undionly.kpxe now receive params: command not found:
@jlober1981 Just to confirm that 10.0.1.203 is the IP address of your fog server?
I’m back in the office today after traveling last week, so I should be able to create a mock up of this over the lunch hour today. Let me see if I can make it work like I think it should in the test lab.
Yes 10.0.1.203 is the correct address of the FOG server
I followed: https://forums.fogproject.org/topic/6400/usb-boot-uefi-client-into-fog-menu-harder-way to the letter, changing only step 3 (output format) to PXE bootstrap Loader keep (.kpxe) and step 4 (NIC type) to undionly. This leads to a large ipxe.kpxe (338KB) download from https://rom-o-matic.eu which I rename to undionly.kpxe and then upload to my tftpboot folder. Once FOG runs it gives me a Installation Failed notice and no other errors, error codes, or options. I’m really unsure what I’m doing wrong. I need to get this to work on the current infrastructure as changing the network scheme is not an option.
I need to host a Fog and SCCM server on the same network subnet. To achieve this I went through the steps to add a PXE Boot Menu allowing a PXE chain to the FOG server. I used https://rom-o-matic.eu/ to edit the undionly.kpxe to set the fog server address using this script:
#!ipxe
set fogserver x.x.x.x
isset ${net0/mac} && dhcp net0 || goto dhcpnet1
echo Received DHCP answer on interface net0 && goto netboot
:dhcpnet1
isset ${net1/mac} && dhcp net1 || goto dhcperror
echo Received DHCP answer on interface net1 && goto netboot
:dhcperror
prompt --key s --timeout 10000 DHCP Failed, hit ‘s’ for the iPXE shell; reboot in 10 seconds && shell || reboot
:netboot
cpuid --ext 29 && set arch x86_64 || set arch i386
params
param mac0 ${net0/mac}
param arch ${arch}
param platform ${platform}
param product ${product}
param ipxever ${version}
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
:bootme
chain http://${fogserver}/fog/service/ipxe/boot.php##params
The script was kindly provided for me by @george1421
After a few smaller errors (Read: user error) I was able to boot a client into the FOG server only to receive the error: params: command not found.
I checked to ensure that #define PARAM_CMD /* Form parameter commands */ was defined in git/fogproject/src/ipxe/src/config/general.h as shown by this post, and it is. Rebooted server to make sure none of my changed required that. Still receiving the error Command not Found. I’m not sure what the next step might be…
