@george1421 Thanks for the response. Before I added PXEClient:Arch:00007:UNDI:003016 to the conf the laptop showed the
Boot to FOG UEFI PXE-BC
on the screen
but iPXE would never start as if it was not finding the file.
The screen goes away too fast to see if there are any other messages

You are correct 7156 was removed, I pulled it from an old build to try different options.

Thanks

@p4cm4n I have the same problem you had. When i look in the dnsmasq log it shows the vendorclass as PXEClient:Arch:00007:UNDI:003016
so i created dhcp-vendorclass=UEFIBC,PXEClient:Arch:00007:UNDI:003016
iwith that in the ltsp.conf i get the Boot to FOG UEFI PXE-BC prompt but it never boots the efi
here is my conf file.
If anyone could help it would be appreciated.

# Don't function as a DNS server:
port=0

# Log lots of extra information about DHCP transactions.
log-dhcp

log-queries

# Set the root directory for files available via FTP.
tftp-root=/tftpboot

# The boot filename, Server name, Server Ip Address
dhcp-boot=undionly.kpxe,,10.5.0.240

# Disable re-use of the DHCP servername and filename fields as extra
# option space. That's to avoid confusing some old or broken DHCP clients.
dhcp-no-override

# inspect the vendor class string and match the text to set the tag
dhcp-vendorclass=BIOS,PXEClient:Arch:00000
dhcp-vendorclass=UEFI32,PXEClient:Arch:00006
dhcp-vendorclass=UEFI,PXEClient:Arch:00007
dhcp-vendorclass=UEFI64,PXEClient:Arch:00009
dhcp-vendorclass=UEFIBC,PXEClient:Arch:00007:UNDI:003016



# Set the boot file name based on the matching tag from the vendor class (above)
dhcp-boot=tag:UEFI32,i386-efi/ipxe.efi,,10.5.0.240
dhcp-boot=tag:UEFI,ipxe.efi,,10.5.0.240
dhcp-boot=tag:UEFI64,ipxe.efi,,10.5.0.240
dhcp-boot=tag:UEFIBC,ipxe7156.efi,,10.5.0.240


# PXE menu.  The first part is the text displayed to the user.  The second is the timeout, in seconds.
pxe-prompt="Booting FOG Client", 3

# The known types are x86PC, PC98, IA64_EFI, Alpha, Arc_x86,
# Intel_Lean_Client, IA32_EFI, BC_EFI, Xscale_EFI and X86-64_EFI
# This option is first and will be the default if there is no input from the user.
pxe-service=X86PC, "Boot to FOG", undionly.kpxe
pxe-service=X86-64_EFI, "Boot to FOG UEFI", ipxe.efi
pxe-service=BC_EFI, "Boot to FOG UEFI PXE-BC", ipxe.efi #ipxe7156.efi

dhcp-range=10.5.0.240,proxy,255.255.0.0```

Hi.
I upgraded to 1.5.6 because when trying to do any fog related tasks through an esxi 6.5 vm the client hangs after the text init.xz… ok
I tried updating the kennel to the latest but no luck. The memtest is able to run but nothing else. Had anyone else experienced this?

Multiple Partition Image - Single Disk (Not Resizable)
Partclone Compressed

Server

• FOG Version: 1.4.4
• OS: Deb 8

Client

• Service Version:
• OS: Win7 64

Description

I created a new image using the EFI settings in vmware esxi and sysprepped the image using the generalize switch. When the deployed image boots, i now get this…

@george1421 Thanks everyone.

@tom-elliott Thanks for the clarification Tom. I want all of our new machines to be in UEFI mode. So I guess i need an image for the “old” legacy BIOS machines and an image for the UEFI machines, right?

@fractal13 Yes it was created on a VM with legacy boot. It is windows 7 and was sysprepped.

Hi, Yes. The issue has something to do with the UEFI mode. In the past we always had the systems set in bios mode and images were created in bios mode. If i change the system to use BIOS mode it will boot from the hard drive, but crashes before windows starts. When rEFInd is used it just gtoes to the rEFInd about page.
Thanks for the prompt reply

Server

• FOG Version: 1.4.4
• OS: Debian 8

Client

• Service Version: NA
• OS: Windows 7 Ent

Description

I am trying to restore an image onto an Optiplex 5050. It looks like fog copies the image to the pc without issue, but after it reboots it never boots from the hard drive. I tried SANBOOT, EXIT and all the other options without any luck. Secure boot is disabled and the system is using UEFI.
I am not sure what else to try.