@george1421 I got it working. My issue was that I erased some lines of code in the “vi src/config.h” portion of the when trying to edit in vim (I wasn’t sure how to edit the file in vim). Once I unpackaged the tarball again, I was able to get it compiled.

Thanks for responding.

@Tom-Elliott @george1421 @Wayne-Workman @Scott-Adams

First, I can assure you its a Surface Pro 3. Unfortunately, its the only one I have at the moment so I cannot verify whether multiple SP3 share the same vendor class. (although I am guessing they may)

PXEClient:Arch:00007:UNDI:003016

The other question in regards to changing to snponly.efi, it could have been I wasn’t pointing the BC_EFI entry.

Correct entry

pxe-service=BC_EFI, "Boot UEFI PXE-BC", ipxe7156.efi

Wrong architecture entry

pxe-service=X86-64_EFI, "Boot Surface UEFI" snponly.efi

Tom, to answer your question, yes I believe you can mark this as solved.

Thanks for all your help.

@Tom-Elliott Thanks!

Server

• FOG Version: 1.3.0-RC-23
• OS: Ubuntu 16.04.1 LTS

Client

• Service Version: 6017
• OS: Windows 10

Description

When navigating to the following page http://x.x.x.x/fog/management/fog/management/index.php?node=service

And attempting to click on Hostname changer, the page appears as follows.

All,

I’ve modified my itsp.conf to the following based upon ProxyDHCP_with_dnsmasq:Adding (a bit more complex) UEFI support to the basic script

port=0
log-dhcp
tftp-root=/tftpboot
dhcp-no-override

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-boot=net:UEFI32,i386-efi/ipxe.efi,,x.x.x.x
dhcp-boot=net:UEFI,ipxe7156.efi,,x.x.x.x
dhcp-boot=net:UEFI64,ipxe.efi,,x.x.x.x
dhcp-boot=undionly.kpxe,,x.x.x.x
pxe-prompt="Booting FOG Client", 20

dhcp-range=x.x.x.x,proxy

The key to getting the Surface Pro 3 to PXE boot into the FOG Menu, and successfully start a Full Registration was modifying the following values.

dhcp-boot=net:UEFI,ipxe.efi,,x.x.x.x

To This

dhcp-boot=net:UEFI,ipxe7156.efi,,x.x.x.x

I am currently 12% of the way through capturing an image, although my VM will probably fill up.

@george1421

Now that I figured out how to take it out of my Ubuntu server, here is the file.
0_1479321004153_output.pcap

0_1479320050891_test.pcap

@george1421

here’s a wireshark capture I did of any traffic going into FOG

@Wayne-Workman I’m using

Running Version 1.3.0-RC-23
SVN Revision: 6017

@Scott-Adams
Here are the contents of my itsp.conf

port=0
log-dhcp
tftp-root=/tftpboot
dhcp-no-override
dhcp-boot=undionly.kpxe,,x.x.x.x
pxe-prompt="Booting FOG Client", 20
pxe-service=X86PC, "Boot BIOS PXE", undionly.kpxe
pxe-service=BC_EFI, "Boot UEFI PXE-BC", ipxe.efi
pxe-service=X86-64_EFI, "Boot UEFI PXE-64" ipxe.efi
pxe-service=X86-64_EFI, "Boot Surface UEFI" snponly.efi
dhcp-range=x.x.x.x,proxy

When I PXE boot and select my snponly.efi entry the screen flashes, then goes back to the “Surface” logo.

@Wayne-Workman let me restate that lol. I have it, just not in my itsp.conf file. I didn’t specify that as an option.

Thanks Wayne and George.

I am using the updated 2.76 version of dnsmasq, however I do not have the boot kernel ipxe7156.efi I’ll have to try that and report back my findings.

@george1421 I got it working. My issue was that I erased some lines of code in the “vi src/config.h” portion of the when trying to edit in vim (I wasn’t sure how to edit the file in vim). Once I unpackaged the tarball again, I was able to get it compiled.

Thanks for responding.