"Start PXE Over IPV4"   we aren't getting this option while trying to PXE boot in order to image build.

What could be reason for it?

Hi Torsten,

On PXE enabled DP side, all Seems OK. Because, we are able to do image build ( both windows 7 and 8.1)  on the computer  Other than Surface Pro

********

Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
SMSPXE 9/8/2015 2:59:10 PM 960 (0x03C0)
F0:1F:AF:23:AC:6A, 4C4C4544-0033-5210-804E-C2C04F4C5831: device is not in the database. SMSPXE 9/8/2015 2:59:10 PM 960 (0x03C0)
Getting boot action for unknown machine: item key: 2046820353 SMSPXE 9/8/2015 2:59:11 PM 960 (0x03C0)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820353" ServerName=""><Machine><ClientID>bf57d608-1981-4d2d-8ed4-79489f35dfe5</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="000201E7" OfferIDTime="11/26/2014 3:03:00 PM" PkgID="00000078" PackageVersion="" PackagePath="http://server.domain.com/SMS_DP_SMSPKG$/00000053" BootImageID="00000053" Mandatory="0"/></ClientIDReply>
SMSPXE 9/8/2015 2:59:12 PM 960 (0x03C0)
F0:1F:AF:23:AC:6A, 4C4C4544-0033-5210-804E-C2C04F4C5831: found optional advertisement 000201E7 SMSPXE 9/8/2015 2:59:12 PM 960 (0x03C0)
Looking for bootImage 00000053 SMSPXE 9/8/2015 2:59:12 PM 960 (0x03C0)

****************

Here is the problem is Surface Pro.

Surface Pro Driver is  included boot image and respective driver available as package.

Looking for bootImage 00000053 SMSPXE 9/8/2015 2:59:12 PM 960 (0x03C0)

Also make sure the MAC-Address of your USB-Ethernet Adapter or Docking-Station is not already assigned to a previously deployed device:

http://blogs.technet.com/b/configurationmgr/archive/2015/08/27/reusing-the-same-nic-for-multiple-pxe-initiated-deployments-in-system-center-configuration-manger-osd.as

Yes Torsten !

Boot image is available 

Thanks simon!   i will consider your points

but  our problem is   very first  option "Start PXE Over IPV4" is not showing up..

Do you use the original Surface USB 3.0 Ethernet Adapter or Surface Pro 3 Docking Station to perform the PXE-Boot? Does PXE-Boot work for other de

Surface USB 3.0 Ethernet Adapter or Surface Pro 3 Docking Station

We are using Original only. Yes  PXE Boot is working for Other than Surface PRO

Please help me on this issue.

This is not global issue. issue happening at particular site.  when they are trying to do image build, they don't see this "Start PXE Over IPV4'" it'f lashed up and moved next option IPv6  

Please help me on this issue.

This is not global issue. issue happening at particular site.  when they are trying to do image build, they don't see this "Start PXE Over IPV4'" it'f lashed up and moved next option IPv6  

Does the boot discovery request make it to the SCCM PXE server?

Can you also please post the complete SMSPXE log file and let us know what is the MAC address of the client that is trying to boot?

DHCP Option and IPhelper  are in place.  

Laptops/Desktops are able to do image build via PXE on the same network

Only issue with  Surface Pro3,  Start PXE over IPv4 option does't show. it seems that bypassed Start PXE over IPv6

Firmware update required for Surface Pro 3?    Earlier it was working via PXE Boot.

Or any setting to be verified at BIOS/UEFI mode? or anything to be enabled over there?

Does this Problem occur with multiple Surface Pro 3 Devices or just with one?

Do you have the latest firmware on your Surface? If not, try to manually install Windows and Update the Firmware and then try again.

I had some PXE related issues in the past with some older firm

DHCP Option and IPhelper  are in place.  

Laptops/Desktops are able to do image build via PXE on the same network

Only issue with  Surface Pro3,  Start PXE over IPv4 option does't show. it seems that bypassed Start PXE over IPv6

Laptps/Desktops are based on BIOS

should I change boot file name?

Laptps/Desktops are based on BIOS

should I change boot file name?

Do you mean change the bootfile name in DHCP option 67?
No, don't do that. Based on my reading, you should remove the option 66/67 settings from the DHCP scope options (i.e. cease serving those options).

The recommended solution is to *only* use IP helper-addresses, and do not offer/serve option 66/67 at all. The bootp request would be forwarded to the PXE/WDS which will respond with wdsndp and then BIOS/UEFI/architecture detection will occur naturally, this allows you to service both BIOS & UEFI clients.