We're running SCCM 2012 R2 and have remote DPs. I can PXE boot and load boot images fine from our main site, but when I try to PXE boot at a remote site I get error E53 no boot filename received. I've checked the smspxe.log file on the remote DP, but no errors there.

When you look at the SMSPXE.log you saw the computer request and you saw the PXE point sending the right winpe ?

Saying no error is a bit vague.

Boot images are distributed to the remote DPs? 

What smsdpprov.log said?

Here is snippet of smspxe.log:

Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
SMSPXE 8/28/2015 11:07:35 AM 3032 (0x0BD8)
00:21:70:C6:88:2B, 4C4C4544-005A-3110-8035-C4C04F524831: device is not in the database. SMSPXE 8/28/2015 11:07:35 AM 3032 (0x0BD8)
Getting boot action for unknown machine: item key: 2046820352 SMSPXE 8/28/2015 11:07:35 AM 3032 (0x0BD8)
Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
SMSPXE 8/28/2015 11:07:37 AM 3036 (0x0BDC)
00:21:70:C6:88:2B, 4C4C4544-005A-3110-8035-C4C04F524831: device is not in the database. SMSPXE 8/28/2015 11:07:37 AM 3036 (0x0BDC)
Getting boot action for unknown machine: item key: 2046820352 SMSPXE 8/28/2015 11:07:37 AM 3036 (0x0BDC)
Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
SMSPXE 8/28/2015 11:07:41 AM 3028 (0x0BD4)
00:21:70:C6:88:2B, 4C4C4544-005A-3110-8035-C4C04F524831: device is not in the database. SMSPXE 8/28/2015 11:07:41 AM 3028 (0x0BD4)
Getting boot action for unknown machine: item key: 2046820352 SMSPXE 8/28/2015 11:07:41 AM 3028 (0x0BD4)
Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
SMSPXE 8/28/2015 11:07:49 AM 3040 (0x0BE0)
00:21:70:C6:88:2B, 4C4C4544-005A-3110-8035-C4C04F524831: device is not in the database. SMSPXE 8/28/2015 11:07:49 AM 3040 (0x0BE0)
Getting boot action for unknown machine: item key: 2046820352 SMSPXE 8/28/2015 11:07:49 AM 3040 (0x0BE0)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName=""><Machine><ClientID>2f5ddd6a-9a99-4c13-824d-78f3bddc8db2</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="CM12001C" OfferIDTime="6/25/2015 10:07:00 AM" PkgID="CM10009B" PackageVersion="" PackagePath="http://sccm-houston.Advocacyinc.org/SMS_DP_SMSPKG$/CM10009D" BootImageID="CM10009D" Mandatory="0"/></ClientIDReply>
SMSPXE 8/28/2015 11:08:17 AM 3032 (0x0BD8)
00:21:70:C6:88:2B, 4C4C4544-005A-3110-8035-C4C04F524831: found optional advertisement CM12001C SMSPXE 8/28/2015 11:08:17 AM 3032 (0x0BD8)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName=""><Machine><ClientID>2f5ddd6a-9a99-4c13-824d-78f3bddc8db2</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="CM12001C" OfferIDTime="6/25/2015 10:07:00 AM" PkgID="CM10009B" PackageVersion="" PackagePath="http://sccm-houston.Advocacyinc.org/SMS_DP_SMSPKG$/CM10009D" BootImageID="CM10009D" Mandatory="0"/></ClientIDReply>
SMSPXE 8/28/2015 11:08:19 AM 3036 (0x0BDC)
00:21:70:C6:88:2B, 4C4C4544-005A-3110-8035-C4C04F524831: found optional advertisement CM12001C SMSPXE 8/28/2015 11:08:19 AM 3036 (0x0BDC)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName=""><Machine><ClientID>2f5ddd6a-9a99-4c13-824d-78f3bddc8db2</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="CM12001C" OfferIDTime="6/25/2015 10:07:00 AM" PkgID="CM10009B" PackageVersion="" PackagePath="http://sccm-houston.Advocacyinc.org/SMS_DP_SMSPKG$/CM10009D" BootImageID="CM10009D" Mandatory="0"/></ClientIDReply>
SMSPXE 8/28/2015 11:08:23 AM 3028 (0x0BD4)
00:21:70:C6:88:2B, 4C4C4544-005A-3110-8035-C4C04F524831: found optional advertisement CM12001C SMSPXE 8/28/2015 11:08:23 AM 3028 (0x0BD4)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName=""><Machine><ClientID>2f5ddd6a-9a99-4c13-824d-78f3bddc8db2</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="CM12001C" OfferIDTime="6/25/2015 10:07:00 AM" PkgID="CM10009B" PackageVersion="" PackagePath="http://sccm-houston.Advocacyinc.org/SMS_DP_SMSPKG$/CM10009D" BootImageID="CM10009D" Mandatory="0"/></ClientIDReply>
SMSPXE 8/28/2015 11:08:31 AM 3040 (0x0BE0)
00:21:70:C6:88:2B, 4C4C4544-005A-3110-8035-C4C04F524831: found optional advertisement CM12001C SMSPXE 8/28/2015 11:08:31 AM 3040 (0x0BE0)

yes, boot images have been distributed and redistributed.

Sandy,

Here are the errors from smsdpprov.log:

[144][Fri 08/28/2015 10:35:46]:MsiEnumRelatedProducts failed
[144][Fri 08/28/2015 10:35:46]:FindProduct failed; 0x80070103
[144][Fri 08/28/2015 10:35:46]:MsiEnumRelatedProducts failed
[144][Fri 08/28/2015 10:35:46]:FindProduct failed; 0x80070103
[144][Fri 08/28/2015 10:35:46]:Found C:\Windows\system32\wimgapi.dll
[144][Fri 08/28/2015 10:35:46]:SetNamedSecurityInfo() failed.
[144][Fri 08/28/2015 10:35:46]:SetObjectOwner() failed. 0x80070002.
[144][Fri 08/28/2015 10:35:46]:SetFileSecurity() failed.

doesn't smsdpgrov.log metion about cannot find ADK? Did you install ADK in your DP?

I don't have ADK installed on the remote DPs. I thought that was only required for the main site. 

Any special instructions for installing ADK 8.1 on SCCM 2102 R2 remote DP?

I don't have ADK installed on the remote DPs. I thought that was only required for the main site. 

Any special instructions for installing ADK 8.1 on SCCM 2102 R2 remote DP?

You don't need to have the Windows ADK on your DP, only on site servers (CAS, Primary Site)

https://technet.microsoft.com/en-us/library/gg682187.aspx

The following features of the Windows ADK must be installed on site server of the top-level site of the hierarchy, and on the site server of each primary site in the hierarchy:

• User State Migration Tool (USMT)

• Windows Deployment Tools

• Windows Preinstallation Environment (Windows PE)

Note
You must manually install the Windows ADK on each computer that will host a central administration site or primary site server before you install the Configuration Manager site.

Can you please check to see if the RemoteInstall\SMSImages folder on the PXE DP has the two (32-bit and 64-bit) boot WIM packages?

Also, please check if the boot files are expanded under RemoteInstall\SMSBoot\x64 and RemoteInstall\SMSBoot\x86.

Can you please check to see if the RemoteInstall\SMSImages folder on the PXE DP has the two (32-bit and 64-bit) boot WIM packages?

Also, please check if the boot files are expanded under RemoteInstall\SMSBoot\x64 and RemoteInstall\SMSBoot\x86.

Yes, you need to distribute boot image (x86) content to your DPs, and enable "Deploy this boot image...."

Kerwin,

Yes, I see all four wim boot packages in d:\RemoteInstall\SMSImages

I see seven files under D:\RemoteInstall\SMSBoot\x64 and \x86 equaling about 3.5mb.

Also, in smspxe.log on remote DP it shows "found optional advertisement CM12001C", but I don't have a boot image package by that name.

• Edited by Carltonw1 17 hours 55 minutes ago

Yes, this has been done. I've also redistributed them. ("Deploy this boot image..." already checked)

FYI - PXE boot works fine from site server. I'm only having this problem on the remote DPs.

Kerwin,

Yes, I see all four wim boot packages in d:\RemoteInstall\SMSImages

I see seven files under D:\RemoteInstall\SMSBoot\x64 and \x86 equaling about 3.5mb.

Also, in smspxe.log on remote DP it shows "found optional advertisement CM12001C", but I don't have a boot image package by that name.

• Edited by Carltonw1 Monday, August 31, 2015 1:56 PM

Kerwin,

Yes, I see all four wim boot packages in d:\RemoteInstall\SMSImages

I see seven files under D:\RemoteInstall\SMSBoot\x64 and \x86 equaling about 3.5mb.

Also, in smspxe.log on remote DP it shows "found optional advertisement CM12001C", but I don't have a boot image package by that name.

• Edited by Carltonw1 Monday, August 31, 2015 1:56 PM

Can you please post the full SMSTS.log file (say, in SkyDrive) and let us know what is the MAC address of the client that is trying to boot?

Kerwin,

It doesn't get to the point where it generates a smsts.log. When I try to PXE boot it won't even show the IP address info from the DHCP server. 

I know the DHCP server works fine because it grabs an IP for Windows 7 clients. 

My apologies. I meant the SMSPXE.log file.

Kerwin,

Thanks for your help. smspxe.log is here:

https://drive.google.com/file/d/0B8VgHS4Ba27ZdW5VcGVZWDAyajQ/view?usp=sharing

MAC is 00:21:70:C6:88:2B

I can think of two possible issues:

1. There is another PXE server on the network. That other one is responding to the client instead of the SCCM PXE server. You can use network trace to verify this.

2. TFTP traffic from the client is not getting to the WDS server. Please check your network configuration (routers, switches, etc) and make sure that you allow TFTP traffic to go through between the clients and the WDS server, in both directions. Also, please check that the firewall on the WDS server allows for TFTP.

If this client is in a different subnet - you may need to configure an IP Helper table on the Router level.

• Proposed as answer by v-2Harsh 1 hour 20 minutes ago

If this client is in a different subnet - you may need to configure an IP Helper table on the Router level.

• Proposed as answer by v-2Harsh Wednesday, September 02, 2015 6:30 AM

If this client is in a different subnet - you may need to configure an IP Helper table on the Router level.

• Proposed as answer by v-2Harsh Wednesday, September 02, 2015 6:30 AM

Client and remote DP are on same subnet and same switch.

I suggest that you run a network trace (like netmon) on your network.

The TFTP packets are not reaching the WDS server. Its stopping somewhere (perhaps in your router, or the firewall).

Hi ,

In distribution point page of deployment task sequence , select " When no local distribution point is available , use remote DP" . Please check if this works.