Hi Wayne,

Thanks for that. But I am a little confused, so please forgive me.

• You said “Vendor Class Identifiers. We have an article written just for this” but there is nothing in there about Cisco configuration for multiple vendor class identifiers.

• “I’d strongly advise you to upgrade to FOG Trunk” but then later “I would advise against it.”. I am not sure if I should or shouldn’t.

From what I can gather, Windows server DHCP is the most flexible way, and seems like you can inject multiple boot files (undi / ipxe / snponly etc). Perhaps I should move from Cisco DHCP to Server 2012, as its easier to manage.
Question, if I go to Windows Server DHCP, am I correct in assuming it allow multiple boot files automatically depending on device.
So if UEFI device is trying to boot, it will boot the ipxe and if we have older devices, it will boot same old undionly file?

I will go and do some research on Cisco multiple Vendor Class Identifiers and see if its possible, and will post back if successful and with steps.

First time posting technical help and thank you to FOG, as I have been using it for years now and all you guys have always helped me simy by reading other posts.

Problem:
Surface Pro 3’s I cannot get it to boot into Fog pxe environment. I hate these devices, but company needs to deploy them on large scale, so I want to support that business decision.

I am running Cisco router with “undionly.kpxe” as the file to detect.

I have a MS USB to Ethernet adaptor. Disabled secure boot, red screen and it attempts to boot off pxe (seems like uefi) but ofcourse, does not boot or want to connect with fog server.

I have created my own rom from rom o matic, using a USB hub, Ethernet adaptor and desperate USB key with my next server ip and undionly.kpxe as boot file within the rom, and a little more success there. Issue is I can see it connecting (trying too) to Fog server, message reads:
“iPXE Initialising Devices … Ok
Configuring (net0 and then my MAC address)”
It just hangs there and after a few seconds co to yes to the Uefi pxe IPv4 and IPv6

I am thinking berween my server and device, something is not handshaking. I just don’t know what and I need some guidance what to do.

I have been using it for years now on at least 30 different devices, always found workarounds with Tftp kernels from Fog Management Console to help. But this uefi is now becoming more and more mainstream and I would like to be able to boot either uefi/legacy

Thanks.