
Tftp Smsboot X64 Pxeboot.com
This happened in a SCCM 2012 R2 SP1 CU3 environment:
Hi Reddit Folks! So i'm looking at some ADR's and looking for Windows 10 flavors with updates classified as: Critical Updates. Security Updates. Looking at the 'Product' section, there's a number of different Windows 10 products to choose from.
When Deploying an OSD task sequence via PXE, at the PXE boot screen the client was stuck on PXE – TFTP Download: smsbootx64pxeboot.n12 ……….
First thing I checked was the smspxe.log on the distribution point. I could see it was in a loop with the line “Looking for bootImage XXX00AA1”

In the ConfigMgr console, I checked MonitoringDistribution StatusContent Status and verified that the boot image was successfully distributed to the distribution point. It was, but obviously there is an issue.
I went to AdministrationOverviewDistribution Points and selected the distribution point having the issue, clicked on Content tab, typed in the boot image name or package ID and clicked Redistribute. Once the boot image had redistributed successfully, I cleared the PXE flag and PXE booted the client again.
Usb camera software. It was able to successfully boot and run the Task Sequence.
This happened in a SCCM 2012 R2 SP1 CU3 environment:
When Deploying an OSD task sequence via PXE, at the PXE boot screen the client was stuck on PXE – TFTP Download: smsbootx64pxeboot.n12 ……….
First thing I checked was the smspxe.log on the distribution point. I could see it was in a loop with the line “Looking for bootImage XXX00AA1”
In the ConfigMgr console, I checked MonitoringDistribution StatusContent Status and verified that the boot image was successfully distributed to the distribution point. It was, but obviously there is an issue.
I went to AdministrationOverviewDistribution Points and selected the distribution point having the issue, clicked on Content tab, typed in the boot image name or package ID and clicked Redistribute. Once the boot image had redistributed successfully, I cleared the PXE flag and PXE booted the client again.
It was able to successfully boot and run the Task Sequence.