Here's my environment:

SCCM 2012 SP1 installed on Server 2008 R2 in a Hyper-V environment

Brand new boot images created after SP1 upgrade using Windows ADK

The virtual is using 1 network adapter (the legacy network adapter has been disabled, as a trobleshooting step)

PXE and WDS have been removed and recreated numerous times

This has never worked since implementation of SCCM 2012 (7/2012)

Attempted on multiple physical clients and a virtual client

The boot images work fine when setup as USB boot media

The network boot always finds the SCCM server as this screen shows:

Then it proceeds to loading the \SMSboot\boot.sdi. Some times it fails right here other times it proceeds to \SMSImages\MFC0008D\BootImagex86.MFC0008D.wim. Either way it gets a bit into the progress bar but always fails to this screen:

The smspxe.log shows the following:

Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777391" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
 SMSPXE 4/10/2013 8:21:12 AM 844 (0x034C)
00:15:5D:0A:6C:0D, BB01BB09-CF61-4611-8820-73941512B432: device is in the database. SMSPXE 4/10/2013 8:21:12 AM 844 (0x034C)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777391" ServerName="" ServerRemoteName=""><Machine><ClientID>GUID:0ba9fb20-f317-475e-8a24-bead025b5e31</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="MFC200EE" OfferIDTime="4/2/2013 11:21:00 AM" PkgID="MFC00007" PackageVersion="" PackagePath="http://(siteserver)/SMS_DP_SMSPKG$/MFC0008D" BootImageID="MFC0008D" Mandatory="0"/></ClientIDReply>
 SMSPXE 4/10/2013 8:21:12 AM 844 (0x034C)
00:15:5D:0A:6C:0D, BB01BB09-CF61-4611-8820-73941512B432: found optional advertisement MFC200EE SMSPXE 4/10/2013 8:21:12 AM 844 (0x034C)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777391" ServerName="" ServerRemoteName=""><Machine><ClientID>GUID:0ba9fb20-f317-475e-8a24-bead025b5e31</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="MFC200EE" OfferIDTime="4/2/2013 11:21:00 AM" PkgID="MFC00007" PackageVersion="" PackagePath="http://(siteserver)/SMS_DP_SMSPKG$/MFC0008D" BootImageID="MFC0008D" Mandatory="0"/></ClientIDReply>
 SMSPXE 4/10/2013 8:21:16 AM 844 (0x034C)
00:15:5D:0A:6C:0D, BB01BB09-CF61-4611-8820-73941512B432: found optional advertisement MFC200EE SMSPXE 4/10/2013 8:21:16 AM 844 (0x034C)
Looking for bootImage MFC0008D SMSPXE 4/10/2013 8:21:16 AM 844 (0x034C)

________________________________________________________________________________________________________________________

It also shows this occasionally after "Looking for bootImage"

BootImage MFC0008D needs to be updated (new packageID=MFC0008D) VersionUpdate=true SMSPXE 4/2/2013 11:25:41 AM 4020 (0x0FB4)

________________________________________________________________________________________________________________________

The only errors I've found have been in the distmgr.log when I've updated the boot images: (notice errors related to wimgapi.dll and errors related to set attribute, remove file, and remove directory failures)

STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=(siteserver) SITE=MFC PID=2676 TID=6104 GMTDATE=Tue Apr 02 20:18:43.917 2013 ISTR0="BootImagex86" ISTR1="MFC0008D" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="MFC0008D" SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:43 PM 6104 (0x17D8)
Start updating the package MFC0008D... SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:43 PM 6104 (0x17D8)
Package storage format has changed for MFC0008D. Updating the distribution points SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:43 PM 6104 (0x17D8)
Enabling package MFC0008D for SMB access on MSWNET:["SMS_SITE=MFC"]\\(siteserver)\SMSPKGC$\MFC0008D\ SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:44 PM 6104 (0x17D8)
Attempting to add or update a package on a distribution point. SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:44 PM 6104 (0x17D8)
The distribution point is on the siteserver and the package is a content type package. There is nothing to be copied over. SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:44 PM 6104 (0x17D8)
STATMSG: ID=2342 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=(siteserver) SITE=MFC PID=2676 TID=6104 GMTDATE=Tue Apr 02 20:18:44.683 2013 ISTR0="BootImagex86" ISTR1="["Display=\\(siteserver)\"]MSWNET:["SMS_SITE=MFC"]\\(siteserver)\" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="MFC0008D" AID1=404 AVAL1="["Display=\\(siteserver)\"]MSWNET:["SMS_SITE=MFC"]\\(siteserver)\" SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:44 PM 6104 (0x17D8)
The current user context will be used for connecting to ["Display=\\(siteserver)\"]MSWNET:["SMS_SITE=MFC"]\\(siteserver)\. SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:45 PM 6104 (0x17D8)
No network connection is needed to ["Display=\\(siteserver)\"]MSWNET:["SMS_SITE=MFC"]\\(siteserver)\ as this is the local machine. SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:45 PM 6104 (0x17D8)
CreateSignatureShare, connecting to DP SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:45 PM 6104 (0x17D8)
Signature share exists on distribution point path \\(siteserver)\SMSSIG$ SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:45 PM 6104 (0x17D8)
Set share security on share \\(siteserver)\SMSSIG$ SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:45 PM 6104 (0x17D8)
Share SMSPKGC$ exists on distribution point \\(siteserver)\SMSPKGC$ SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:45 PM 6104 (0x17D8)
Set share security on share \\(siteserver)\SMSPKGC$ SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:45 PM 6104 (0x17D8)
Set share security on share \\(siteserver)\SCCMContentLib$ SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:45 PM 6104 (0x17D8)
Successfully created directory \\(siteserver)\SMSPKGC$\MFC0008D for package MFC0008D SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:46 PM 6104 (0x17D8)
Copying package MFC0008D to the package share location \\(siteserver)\SMSPKGC$\MFC0008D on the server ["Display=\\(siteserver)\"]MSWNET:["SMS_SITE=MFC"]\\(siteserver)\ SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:46 PM 6104 (0x17D8)
SMSDP_ExpandPXEImage: MFC0008D, 1174406304 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:47 PM 6104 (0x17D8)
Library path mismatch: \\?\C:\SCCMContentLib, C:\SCCMContentLib SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:47 PM 6104 (0x17D8)
Expanding C:\SCCMContentLib\FileLib\DE79\DE7975B36C7DCA08953E8404A1FC115DC9A250828456A8E34C5C158C1907EE14 from package MFC0008D SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:47 PM 6104 (0x17D8)
Finding Wimgapi.Dll SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:47 PM 6104 (0x17D8)
MsiEnumRelatedProducts failed SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:47 PM 6104 (0x17D8)
FindProduct failed; 0x80070103 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:47 PM 6104 (0x17D8)
MsiEnumRelatedProducts failed SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:47 PM 6104 (0x17D8)
FindProduct failed; 0x80070103 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:47 PM 6104 (0x17D8)
Found C:\Windows\system32\wimgapi.dll SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:47 PM 6104 (0x17D8)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 4216 (0x1078)
SetFileAttributesW failed for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\EFI\bootmgfw.efi SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveDirectoryW failed (0x80070091) for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\EFI SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
SetFileAttributesW failed for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\Fonts\segmono_boot.ttf SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
SetFileAttributesW failed for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\Fonts\segoen_slboot.ttf SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
SetFileAttributesW failed for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\Fonts\segoe_slboot.ttf SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
SetFileAttributesW failed for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\Fonts\wgl4_boot.ttf SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveDirectoryW failed (0x80070091) for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\Fonts SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
SetFileAttributesW failed for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\PXE\abortpxe.com SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
SetFileAttributesW failed for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\PXE\bootmgr.exe SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
SetFileAttributesW failed for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\PXE\pxeboot.com SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
SetFileAttributesW failed for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\PXE\pxeboot.n12 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
SetFileAttributesW failed for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\PXE\wdsmgfw.efi SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
SetFileAttributesW failed for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\PXE\wdsnbp.com SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveDirectoryW failed (0x80070091) for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\PXE SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveDirectoryW failed (0x80070091) for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveDirectoryW failed (0x80070091) for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveDirectoryW failed (0x80070091) for C:\RemoteInstall\SMSTempBootFiles\MFC0008D SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
Expanding MFC0008D to C:\RemoteInstall\SMSImages SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
Used 1 out of 3 allowed processing threads. SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 1872 (0x0750)
Sleep 3600 seconds... SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 1872 (0x0750)
STATMSG: ID=2330 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=(siteserver) SITE=MFC PID=2676 TID=6104 GMTDATE=Tue Apr 02 20:18:49.796 2013 ISTR0="MFC0008D" ISTR1="["Display=\\(siteserver)\"]MSWNET:["SMS_SITE=MFC"]\\(siteserver)\" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="MFC0008D" AID1=404 AVAL1="["Display=\\(siteserver)\"]MSWNET:["SMS_SITE=MFC"]\\(siteserver)\" SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:49 PM 6104 (0x17D8)
Successfully created/updated the package server in the data source SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:49 PM 6104 (0x17D8)
Performing cleanup prior to returning. SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:49 PM 6104 (0x17D8)
The Package Action is 1, the Update Mask is 266240 and UpdateMaskEx is 1064960. SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:49 PM 6104 (0x17D8)
Successfully created/updated the package MFC0008D SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:49 PM 6104 (0x17D8)
STATMSG: ID=2311 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=(siteserver) SITE=MFC PID=2676 TID=6104 GMTDATE=Tue Apr 02 20:18:49.943 2013 ISTR0="MFC0008D" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="MFC0008D" SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:49 PM 6104 (0x17D8)
Set share security on share \\(siteserver)\SCCMContentLib$ SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:49 PM 6104 (0x17D8)
Set share security on share \\(siteserver)\SCCMContentLib$ SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:49 PM 6104 (0x17D8)
Created policy provider trigger for ID MFC0008D SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:51 PM 6104 (0x17D8)
Package MFC0008D does not have a preferred sender. SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:51 PM 6104 (0x17D8)
Package MFC0008D is new or has changed, replicating to all applicable sites. SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:51 PM 6104 (0x17D8)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=MFC0008D, Version=2, Status=2301 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:51 PM 6104 (0x17D8)
StoredPkgVersion (2) of package MFC0008D. StoredPkgVersion in database is 2. SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:51 PM 6104 (0x17D8)
SourceVersion (2) of package MFC0008D. SourceVersion in database is 2. SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:51 PM 6104 (0x17D8)
STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=(siteserver) SITE=MFC PID=2676 TID=6104 GMTDATE=Tue Apr 02 20:18:51.876 2013 ISTR0="BootImagex86" ISTR1="MFC0008D" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="MFC0008D" SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:51 PM 6104 (0x17D8)
Exiting package processing thread. SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:51 PM 6104 (0x17D8)
Used 0 out of 3 allowed processing threads. SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:57 PM 1872 (0x0750)
The last source update time for pkg MFC0008D is 4/2/2013 10:56:53 AM Pacific Daylight Time SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:57 PM 1872 (0x0750)
The next start time for pkg MFC0008D is 4/2/2013 1:18:57 PM Pacific Daylight Time SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:57 PM 1872 (0x0750)

___________________________________________________________________________________________________________________________

At this point I'm out of ideas. I've searched all the forums tried just about everything I can think of except for settings DHCP options or IP Helpers. I've declined to do that because it appears to find the server just fine. Also the client, DHCP, and the SCCMPXE Point are all on the same subnet.

Help me Obi-(technet)-wan you're my only hope!

• Edited by McFarland Cascade Wednesday, April 10, 2013 3:52 PM formatting

It almost looks as though you don't have all the required drivers in your WinPE image.  As you said it was a new boot image, is there a chance that you missed a driver?

Well that's what I thought also but when I make a TS Boot Media ISO using the x86 and x64 boot images, and xfer those to a USB stick that loads fine. Even a brand new boot image made from ADK without any additional drivers can boot my virtual client if I turn it into a TS Boot Media ISO and boot it from the virtual CD Drive. I haven't tried to load any drivers through WDS because everyone says to leave that alone.

You're getting the response from the WDS service on the PXE Service Point, so I don't think it's DHCP issue.  

Do you ever fully download the boot.wim?  Is it the exact same boot.wim on your PXE Service Point as the ISO that you boot from?  That is, have you re-distributed to the PXE distribution point? 

I also see a lot of access denied errors in your distmgr.log, you might want to double check your admin rights for site servers. 

It's all the same. The Primary Site Server is also our only DP. When I update it is when I get those weird errors in the distmgr.log. I also get that error in the smspxe.log that the image needs to be updated, but that's like right after I update it. I've tried unchecking the PXE option on the DP, waited while it removes WDS, and deleted the remote install folder. Then check the option for PXE and watch it all come back and update the distribution of the images I get those same errors in the distmgr.log. It's like it's some weird rights error with the Remote Install folder but I can't seem to get past it.

You should have a directory: C:\RemoteInstall\SMSImages\MFC0008D  and in that directory you should have a file named WinPE.MFC0008D.wim 

Also, the RemoteInstall folder should have Admins/System Full right down the tree.  If that's not working, you could try going with Everyone Full.  

Do you have UAC disabled? It might be messing with things if it isn't. 

• Edited by EricS108 Wednesday, April 10, 2013 9:56 PM

That directory exists, however my file is called BootImagex86.MFC0008D.wim because that's the name of my boot image series (x86 and x64).

I disabled UAC and added everyone with full control at the NTFS level on the remoteinstall folder. To do that I had to take ownership because TrustedInstaller was owner for some reason on some of the subfolders (SMSTemp and SMSTempBootFiles).

After doing that and cleaning out the SMSTemp and SMSTempBootFiles and redistributing the x86 and x64 boot images and verifying the drivers were injected, I still made no progress failing at the same point.

Are you using only x86 boot image?

have you distributed x64 boot image?

do you have task sequence available with both x86 and x64?

what have you written in option 67?

I am using the x86 and x64 boot images. Both up to date and loaded with drivers.

There is a task sequence for unknown computers and I've specifically added some test machines to the task sequences.

We don't have option 67 setup in DHCP. We've never needed it because it always seems to find the server and load boot.sdi and sometimes the wim but always fails at that point, not before. This has led us to believe it's not a DHCP issue.

The SMSPXE.log never seems to get past "looking for bootimage (bootimage name)"

Here are the logs after I removed and reinstalled the PXE role on the DP (notice the errors relating to not being able to find wimgapi.dll, and Failed to copy the needed boot binaries from the boot image) To fix the wimgapi.dll error I've tried running the wimgapi.msi file in the Config Manager folder in program files, no change. The second error I've tried to fix by manually mounting the wim, no change.

SMSPXE.LOG

================= PXE Provider loaded. ===================== SMSPXE 4/11/2013 10:02:11 AM 6128 (0x17F0)
Machine is running Windows Longhorn. (NTVersion=0X601, ServicePack=1) SMSPXE 4/11/2013 10:02:11 AM 6128 (0x17F0)
Cannot read the registry value of MACIgnoreListFile (00000000) SMSPXE 4/11/2013 10:02:11 AM 6128 (0x17F0)
MAC Ignore List Filename in registry is empty SMSPXE 4/11/2013 10:02:11 AM 6128 (0x17F0)
Begin validation of Certificate [Thumbprint 64C881149146DD93DB1D6092ACA4D6BC85F98C30] issued to '{0B126787-AE51-4288-89FD-5BEBF0F64FA5}' SMSPXE 4/11/2013 10:02:11 AM 6128 (0x17F0)
Completed validation of Certificate [Thumbprint 64C881149146DD93DB1D6092ACA4D6BC85F98C30] issued to '{0B126787-AE51-4288-89FD-5BEBF0F64FA5}' SMSPXE 4/11/2013 10:02:11 AM 6128 (0x17F0)
Initializing PXEPerfObject. SMSPXE 4/11/2013 10:02:11 AM 6128 (0x17F0)
Could not load logging configuration for component ccmperf. Using default values. SMSPXE 4/11/2013 10:02:11 AM 6128 (0x17F0)
Client is set to use HTTPS when available. The current state is 224. SMSPXE 4/11/2013 10:02:12 AM 6128 (0x17F0)
Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
 SMSPXE 4/11/2013 10:02:12 AM 6128 (0x17F0)
PXE::CBootImageInfo::CBootImageInfo: key= SMSPXE 4/11/2013 10:02:12 AM 6128 (0x17F0)
PXE::CBootImageInfo::CBootImageInfo: key= SMSPXE 4/11/2013 10:02:12 AM 6128 (0x17F0)
Adding MFC0008B.21 SMSPXE 4/11/2013 10:02:13 AM 6128 (0x17F0)
Adding MFC0008D.20 SMSPXE 4/11/2013 10:02:20 AM 6128 (0x17F0)
Found new image MFC0008B SMSPXE 4/11/2013 10:02:24 AM 6128 (0x17F0)
Opening image file C:\RemoteInstall\SMSImages\MFC0008B\BootImagex64.MFC0008B.wim SMSPXE 4/11/2013 10:02:24 AM 6128 (0x17F0)
Found Image file: C:\RemoteInstall\SMSImages\MFC0008B\BootImagex64.MFC0008B.wim
 PackageID: MFC0008B
 ProductName: Microsoft Windows Operating System
 Architecture: 9
 Description: Microsoft Windows PE (x64)
 Version: 
 Creator:
 SystemDir: WINDOWS
 SMSPXE 4/11/2013 10:02:24 AM 6128 (0x17F0)
Closing image file C:\RemoteInstall\SMSImages\MFC0008B\BootImagex64.MFC0008B.wim SMSPXE 4/11/2013 10:02:24 AM 6128 (0x17F0)
InstallBootFilesForImage failed. 0x80004005 SMSPXE 4/11/2013 10:02:26 AM 6128 (0x17F0)
Warning: Failed to copy the needed boot binaries from the boot image C:\RemoteInstall\SMSImages\MFC0008B\BootImagex64.MFC0008B.wim.
The operation completed successfully. (Error: 00000000; Source: Windows) SMSPXE 4/11/2013 10:02:26 AM 6128 (0x17F0)
Failed adding image C:\RemoteInstall\SMSImages\MFC0008B\BootImagex64.MFC0008B.wim. Will Retry..
Unspecified error (Error: 80004005; Source: Windows) SMSPXE 4/11/2013 10:02:26 AM 6128 (0x17F0)
File C:\RemoteInstall\SMSTemp\2013.04.11.10.02.24.01.{815BF406-40BF-4198-BEBC-F660FB134A62}.boot.bcd deleted. SMSPXE 4/11/2013 10:02:26 AM 6128 (0x17F0)
File C:\RemoteInstall\SMSTemp\2013.04.11.10.02.24.01.{815BF406-40BF-4198-BEBC-F660FB134A62}.boot.bcd.log deleted. SMSPXE 4/11/2013 10:02:26 AM 6128 (0x17F0)
Found new image MFC0008D SMSPXE 4/11/2013 10:02:26 AM 6128 (0x17F0)
Opening image file C:\RemoteInstall\SMSImages\MFC0008D\BootImagex86.MFC0008D.wim SMSPXE 4/11/2013 10:02:26 AM 6128 (0x17F0)
Found Image file: C:\RemoteInstall\SMSImages\MFC0008D\BootImagex86.MFC0008D.wim
 PackageID: MFC0008D
 ProductName: Microsoft Windows Operating System
 Architecture: 0
 Description: Microsoft Windows PE (x86)
 Version: 
 Creator:
 SystemDir: WINDOWS
 SMSPXE 4/11/2013 10:02:26 AM 6128 (0x17F0)
Closing image file C:\RemoteInstall\SMSImages\MFC0008D\BootImagex86.MFC0008D.wim SMSPXE 4/11/2013 10:02:26 AM 6128 (0x17F0)
InstallBootFilesForImage failed. 0x80004005 SMSPXE 4/11/2013 10:02:27 AM 6128 (0x17F0)
Warning: Failed to copy the needed boot binaries from the boot image C:\RemoteInstall\SMSImages\MFC0008D\BootImagex86.MFC0008D.wim.
The operation completed successfully. (Error: 00000000; Source: Windows) SMSPXE 4/11/2013 10:02:27 AM 6128 (0x17F0)
Failed adding image C:\RemoteInstall\SMSImages\MFC0008D\BootImagex86.MFC0008D.wim. Will Retry..
Unspecified error (Error: 80004005; Source: Windows) SMSPXE 4/11/2013 10:02:27 AM 6128 (0x17F0)
File C:\RemoteInstall\SMSTemp\2013.04.11.10.02.26.02.{D1D513E6-47C7-46F9-B50A-6E93E400D65B}.boot.bcd deleted. SMSPXE 4/11/2013 10:02:27 AM 6128 (0x17F0)
File C:\RemoteInstall\SMSTemp\2013.04.11.10.02.26.02.{D1D513E6-47C7-46F9-B50A-6E93E400D65B}.boot.bcd.log deleted. SMSPXE 4/11/2013 10:02:27 AM 6128 (0x17F0)
Begin validation of Certificate [Thumbprint 64C881149146DD93DB1D6092ACA4D6BC85F98C30] issued to '{0B126787-AE51-4288-89FD-5BEBF0F64FA5}' SMSPXE 4/11/2013 10:02:27 AM 6128 (0x17F0)
Completed validation of Certificate [Thumbprint 64C881149146DD93DB1D6092ACA4D6BC85F98C30] issued to '{0B126787-AE51-4288-89FD-5BEBF0F64FA5}' SMSPXE 4/11/2013 10:02:27 AM 6128 (0x17F0)
PXE Provider finished loading. SMSPXE 4/11/2013 10:02:27 AM 6128 (0x17F0)
Found new image MFC0008B SMSPXE 4/11/2013 10:02:27 AM 6104 (0x17D8)
Opening image file C:\RemoteInstall\SMSImages\MFC0008B\BootImagex64.MFC0008B.wim SMSPXE 4/11/2013 10:02:27 AM 6104 (0x17D8)
Found Image file: C:\RemoteInstall\SMSImages\MFC0008B\BootImagex64.MFC0008B.wim
 PackageID: MFC0008B
 ProductName: Microsoft Windows Operating System
 Architecture: 9
 Description: Microsoft Windows PE (x64)
 Version: 
 Creator:
 SystemDir: WINDOWS
 SMSPXE 4/11/2013 10:02:27 AM 6104 (0x17D8)
Closing image file C:\RemoteInstall\SMSImages\MFC0008B\BootImagex64.MFC0008B.wim SMSPXE 4/11/2013 10:02:27 AM 6104 (0x17D8)
InstallBootFilesForImage failed. 0x80004005 SMSPXE 4/11/2013 10:02:28 AM 6104 (0x17D8)
Warning: Failed to copy the needed boot binaries from the boot image C:\RemoteInstall\SMSImages\MFC0008B\BootImagex64.MFC0008B.wim.
The operation completed successfully. (Error: 00000000; Source: Windows) SMSPXE 4/11/2013 10:02:28 AM 6104 (0x17D8)
Failed adding image C:\RemoteInstall\SMSImages\MFC0008B\BootImagex64.MFC0008B.wim. Will Retry..
Unspecified error (Error: 80004005; Source: Windows) SMSPXE 4/11/2013 10:02:28 AM 6104 (0x17D8)
File C:\RemoteInstall\SMSTemp\2013.04.11.10.02.27.03.{CC4A1AFE-988E-4D35-A790-1A45C3006F21}.boot.bcd deleted. SMSPXE 4/11/2013 10:02:28 AM 6104 (0x17D8)
File C:\RemoteInstall\SMSTemp\2013.04.11.10.02.27.03.{CC4A1AFE-988E-4D35-A790-1A45C3006F21}.boot.bcd.log deleted. SMSPXE 4/11/2013 10:02:28 AM 6104 (0x17D8)
Found new image MFC0008D SMSPXE 4/11/2013 10:02:28 AM 6104 (0x17D8)
Opening image file C:\RemoteInstall\SMSImages\MFC0008D\BootImagex86.MFC0008D.wim SMSPXE 4/11/2013 10:02:28 AM 6104 (0x17D8)
Found Image file: C:\RemoteInstall\SMSImages\MFC0008D\BootImagex86.MFC0008D.wim
 PackageID: MFC0008D
 ProductName: Microsoft Windows Operating System
 Architecture: 0
 Description: Microsoft Windows PE (x86)
 Version: 
 Creator:
 SystemDir: WINDOWS
 SMSPXE 4/11/2013 10:02:28 AM 6104 (0x17D8)
Closing image file C:\RemoteInstall\SMSImages\MFC0008D\BootImagex86.MFC0008D.wim SMSPXE 4/11/2013 10:02:28 AM 6104 (0x17D8)
Cannot read the registry value of MACIgnoreListFile (800703e5) SMSPXE 4/11/2013 10:02:31 AM 1508 (0x05E4)
MAC Ignore List Filename in registry is empty SMSPXE 4/11/2013 10:02:31 AM 1508 (0x05E4)
Found new image MFC0008B SMSPXE 4/11/2013 10:02:33 AM 6104 (0x17D8)
Opening image file C:\RemoteInstall\SMSImages\MFC0008B\BootImagex64.MFC0008B.wim SMSPXE 4/11/2013 10:02:33 AM 6104 (0x17D8)
Found Image file: C:\RemoteInstall\SMSImages\MFC0008B\BootImagex64.MFC0008B.wim
 PackageID: MFC0008B
 ProductName: Microsoft Windows Operating System
 Architecture: 9
 Description: Microsoft Windows PE (x64)
 Version: 
 Creator:
 SystemDir: WINDOWS
 SMSPXE 4/11/2013 10:02:33 AM 6104 (0x17D8)
Closing image file C:\RemoteInstall\SMSImages\MFC0008B\BootImagex64.MFC0008B.wim SMSPXE 4/11/2013 10:02:33 AM 6104 (0x17D8)
Cannot read the registry value of MACIgnoreListFile (800703e5) SMSPXE 4/11/2013 10:02:45 AM 6104 (0x17D8)
MAC Ignore List Filename in registry is empty SMSPXE 4/11/2013 10:02:45 AM 6104 (0x17D8)

DISTMGR.LOG

ConfigurePXE SMS_DISTRIBUTION_MANAGER 4/11/2013 10:01:50 AM 4308 (0x10D4)
CcmInstallPXE SMS_DISTRIBUTION_MANAGER 4/11/2013 10:01:50 AM 4308 (0x10D4)
Running: C:\Program Files\Microsoft Configuration Manager\bin\x64\vcredist_x64.exe /q /l C:\Program Files\Microsoft Configuration Manager\bin\x64\vcredist.log SMS_DISTRIBUTION_MANAGER 4/11/2013 10:01:50 AM 4308 (0x10D4)
Waiting for the completion of: C:\Program Files\Microsoft Configuration Manager\bin\x64\vcredist_x64.exe /q /l C:\Program Files\Microsoft Configuration Manager\bin\x64\vcredist.log SMS_DISTRIBUTION_MANAGER 4/11/2013 10:01:50 AM 4308 (0x10D4)
Run completed for: C:\Program Files\Microsoft Configuration Manager\bin\x64\vcredist_x64.exe /q /l C:\Program Files\Microsoft Configuration Manager\bin\x64\vcredist.log SMS_DISTRIBUTION_MANAGER 4/11/2013 10:01:55 AM 4308 (0x10D4)
Created the DP mutex key for WDS. SMS_DISTRIBUTION_MANAGER 4/11/2013 10:01:55 AM 4308 (0x10D4)
Finding Wimgapi.Dll SMS_DISTRIBUTION_MANAGER 4/11/2013 10:01:55 AM 4308 (0x10D4)
MsiEnumRelatedProducts failed SMS_DISTRIBUTION_MANAGER 4/11/2013 10:01:55 AM 4308 (0x10D4)
FindProduct failed; 0x80070103 SMS_DISTRIBUTION_MANAGER 4/11/2013 10:01:55 AM 4308 (0x10D4)
MsiEnumRelatedProducts failed SMS_DISTRIBUTION_MANAGER 4/11/2013 10:01:55 AM 4308 (0x10D4)
FindProduct failed; 0x80070103 SMS_DISTRIBUTION_MANAGER 4/11/2013 10:01:55 AM 4308 (0x10D4)
Found C:\Windows\system32\wimgapi.dll SMS_DISTRIBUTION_MANAGER 4/11/2013 10:01:55 AM 4308 (0x10D4)
Wimgapi.dll is already installed. SMS_DISTRIBUTION_MANAGER 4/11/2013 10:01:55 AM 4308 (0x10D4)
Path to smsdp.dll is 'C:\Program Files\Microsoft Configuration Manager\bin\x64\SMSDP.DLL' SMS_DISTRIBUTION_MANAGER 4/11/2013 10:01:55 AM 4308 (0x10D4)
PXE performance counters have been initialized SMS_DISTRIBUTION_MANAGER 4/11/2013 10:01:55 AM 4308 (0x10D4)
Failed to open WDS service. SMS_DISTRIBUTION_MANAGER 4/11/2013 10:01:55 AM 4308 (0x10D4)
WDS is NOT INSTALLED SMS_DISTRIBUTION_MANAGER 4/11/2013 10:01:55 AM 4308 (0x10D4)
Installing WDS. SMS_DISTRIBUTION_MANAGER 4/11/2013 10:01:55 AM 4308 (0x10D4)
Running: ServerManagerCmd.exe -i WDS -a SMS_DISTRIBUTION_MANAGER 4/11/2013 10:01:55 AM 4308 (0x10D4)
Waiting for the completion of: ServerManagerCmd.exe -i WDS -a SMS_DISTRIBUTION_MANAGER 4/11/2013 10:01:55 AM 4308 (0x10D4)
Run completed for: ServerManagerCmd.exe -i WDS -a SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:04 AM 4308 (0x10D4)
Successfully installed WDS. SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:04 AM 4308 (0x10D4)
Machine is running Windows Server. (NTVersion=0X601, ServicePack=1) SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:04 AM 4308 (0x10D4)
WDS is INSTALLED SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:04 AM 4308 (0x10D4)
Machine is running Windows Server. (NTVersion=0X601, ServicePack=1) SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:04 AM 4308 (0x10D4)
Setting TFTP config key as: System\CurrentControlSet\Services\WDSSERVER\Providers\WDSTFTP SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:04 AM 4308 (0x10D4)
Configuring TFTP read filters SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:04 AM 4308 (0x10D4)
SetupComplete is set to 0 SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:04 AM 4308 (0x10D4)
RegQueryValueExW failed for Software\Microsoft\Windows\CurrentVersion\Setup, REMINST SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:04 AM 4308 (0x10D4)
RegReadDWord failed; 0x80070002 SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:04 AM 4308 (0x10D4)
REMINST not set in WDS SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:04 AM 4308 (0x10D4)
WDS is NOT Configured SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:04 AM 4308 (0x10D4)
Share (REMINST) does not exist. (NetNameNotFound) (0x00000906) SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:04 AM 4308 (0x10D4)
GetFileSharePath failed; 0x80070906 SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:04 AM 4308 (0x10D4)
REMINST share does not exist. Need to create it. SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:04 AM 4308 (0x10D4)
Enumerating drives A through Z for the NTFS drive with the most free space. SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:04 AM 4308 (0x10D4)

Checking Drive: C:\ SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:05 AM 4308 (0x10D4)

Drive 'C:\' is the best drive for the SMS installation directory. SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:05 AM 4308 (0x10D4)
Creating REMINST share to point to: C:\RemoteInstall SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:05 AM 4308 (0x10D4)
Succesfully created share REMINST SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:06 AM 4308 (0x10D4)
Removing existing PXE related directories SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:06 AM 4308 (0x10D4)
Registering WDS provider: SourceDir: C:\Program Files\Microsoft Configuration Manager\bin\x64 SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:06 AM 4308 (0x10D4)
Registering WDS provider: ProviderPath: C:\Program Files\Microsoft Configuration Manager\bin\x64\smspxe.dll SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:06 AM 4308 (0x10D4)
DoPxeProviderRegister SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:06 AM 4308 (0x10D4)
PxeLoadWdsPxe SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:06 AM 4308 (0x10D4)
Loading wdspxe.dll from C:\Windows\system32\wdspxe.dll SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:06 AM 4308 (0x10D4)
wdspxe.dll is loaded SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:06 AM 4308 (0x10D4)
PxeProviderRegister has suceeded (0x00000000) SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:06 AM 4308 (0x10D4)
Disabling WDS/RIS functionality SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:06 AM 4308 (0x10D4)
PxeProviderUnRegister SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:06 AM 4308 (0x10D4)
SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:06 AM 4308 (0x10D4)
Found privilege otifyPrivilege on service WDSServer SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:06 AM 4308 (0x10D4)
Found privilege SeRestorePrivilege on service WDSServer SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:06 AM 4308 (0x10D4)
Found privilege SeBackupPrivilege on service WDSServer SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:06 AM 4308 (0x10D4)
Found privilege SeSecurityPrivilege on service WDSServer SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:06 AM 4308 (0x10D4)
Privilege SeTakeOwnershipPrivilege NOT found service WDSServer SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:06 AM 4308 (0x10D4)
ChangeServiceConfig2 succeeded for WDSServer. Added privilege SeTakeOwnershipPrivilege SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:06 AM 4308 (0x10D4)
ChangeServiceConfig succeeded for WDSServer. StartType: 0x2 SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:06 AM 4308 (0x10D4)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:13 AM 4872 (0x1308)
Created policy provider trigger for ID 16777217 SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:15 AM 4864 (0x1300)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:18 AM 4872 (0x1308)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:23 AM 4872 (0x1308)
WDSServer status is 4 SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:27 AM 4308 (0x10D4)
WDSServer is STARTED SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:27 AM 4308 (0x10D4)
Running: WDSUTIL.exe /Initialize-Server /REMINST:"C:\RemoteInstall" SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:27 AM 4308 (0x10D4)
Waiting for the completion of: WDSUTIL.exe /Initialize-Server /REMINST:"C:\RemoteInstall" SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:27 AM 4308 (0x10D4)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:28 AM 4872 (0x1308)
Run completed for: WDSUTIL.exe /Initialize-Server /REMINST:"C:\RemoteInstall" SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:29 AM 4308 (0x10D4)
Machine is running Windows Server. (NTVersion=0X601, ServicePack=1) SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:29 AM 4308 (0x10D4)
No need to configure the firewall SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:29 AM 4308 (0x10D4)
Processing MFC0008B SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:29 AM 4308 (0x10D4)
Library path mismatch: \\?\C:\SCCMContentLib, C:\SCCMContentLib SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:29 AM 4308 (0x10D4)
Expanding C:\SCCMContentLib\FileLib\FDB6\FDB6C3EAB458C526E27E5C08432CF9B5506BC082F9A2F7AFE419696E4C6F5ED0 from package MFC0008B SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:29 AM 4308 (0x10D4)
Finding Wimgapi.Dll SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:29 AM 4308 (0x10D4)
MsiEnumRelatedProducts failed SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:29 AM 4308 (0x10D4)
FindProduct failed; 0x80070103 SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:29 AM 4308 (0x10D4)
MsiEnumRelatedProducts failed SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:29 AM 4308 (0x10D4)
FindProduct failed; 0x80070103 SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:29 AM 4308 (0x10D4)
Found C:\Windows\system32\wimgapi.dll SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:29 AM 4308 (0x10D4)
Expanding MFC0008B to C:\RemoteInstall\SMSImages SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:30 AM 4308 (0x10D4)
Processing MFC0008D SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:30 AM 4308 (0x10D4)
Library path mismatch: \\?\C:\SCCMContentLib, C:\SCCMContentLib SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:30 AM 4308 (0x10D4)
Expanding C:\SCCMContentLib\FileLib\8CE4\8CE4C1F4C1ECC3920C451199CB69F3C7584DCFCE05E31F997AE10C244861248B from package MFC0008D SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:30 AM 4308 (0x10D4)
Finding Wimgapi.Dll SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:30 AM 4308 (0x10D4)
MsiEnumRelatedProducts failed SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:30 AM 4308 (0x10D4)
FindProduct failed; 0x80070103 SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:30 AM 4308 (0x10D4)
MsiEnumRelatedProducts failed SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:30 AM 4308 (0x10D4)
FindProduct failed; 0x80070103 SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:30 AM 4308 (0x10D4)
Found C:\Windows\system32\wimgapi.dll SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:30 AM 4308 (0x10D4)
Expanding MFC0008D to C:\RemoteInstall\SMSImages SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:31 AM 4308 (0x10D4)
CcmInstallPXE: Deleting the DP mutex key for WDS. SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:31 AM 4308 (0x10D4)
DP monitoring task is disabed on server (site server) SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:32 AM 4308 (0x10D4)
No need to initialize monitoring task on (site server) SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:32 AM 4308 (0x10D4)
DP settings have been updated to (site server). SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:32 AM 4308 (0x10D4)
Sleep 858 seconds... SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:32 AM 4308 (0x10D4)
Found notification for package 'MFC00002' SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:42 AM 4308 (0x10D4)
Found notification for package 'MFC00003' SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:42 AM 4308 (0x10D4)
Package Thread Limit: 3 SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:42 AM 4308 (0x10D4)
Retry interval: 30 SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:42 AM 4308 (0x10D4)
DP upgrade thread Limit: 5 SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:42 AM 4308 (0x10D4)
DP upgrade retry interval: 20 SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:42 AM 4308 (0x10D4)
STATMSG: ID=2375 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=(site server) SITE=MFC PID=2572 TID=4308 GMTDATE=Thu Apr 11 17:02:42.346 2013 ISTR0="["Display=\\(site server)\"]MSWNET:["SMS_SITE=MFC"]\\(site server)\" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=404 AVAL0="["Display=\\(site server)\"]MSWNET:["SMS_SITE=MFC"]\\(site server)\" SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:42 AM 4308 (0x10D4)
Setting HTTPUrl to http://(site server)/SMS_DP_SMSPKG$/MFC00003 for package MFC00003 on DP \\(site server)\SCCMContentLib$ SMS_DISTRIBUTION_MANAGER 4/11/2013 10:02:42 AM 4308 (0x10D4)
STATMSG: ID=2375 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=(site server) SITE=MFC PID=2572 TID=4308 GMTDATE=Thu Apr 11 17:02:42.868 2013 ISTR0="["Display=\\(site server)\"]MSWNET:["SMS_SITE=MFC"]\\(site server)\" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" I

How much memory on the computer you are booting?

There was a similar issue reported here: http://social.technet.microsoft.com/Forums/en-US/configmanagerosd/thread/cea3eedf-1a36-43d4-ad8f-96134aa9386a

Perhaps it's the network card selection you have on your VM? 

My issue also :)

Just imported the LAN Driver of the laptop in question, added it  to my Boot Image and and all works great :) 

There was a similar issue reported here: http://social.technet.microsoft.com/Forums/en-US/configmanagerosd/thread/cea3eedf-1a36-43d4-ad8f-96134aa9386a

Perhaps it's the network card selection you have on your VM? 

Agreed, I would check here. Had the same problem recently with vmxnet3 not playing well with PXE.

Definitely not a driver issue as drivers do not come into play until the boot wim has been completely downloaded, mounted and booted into WinPE.

Hi All,

Firstly, apologies for dragging this up again after so long but we are also experiencing this issue.  In our SCCM 2012 R2 environment it occurs when we try to increase the TFTP block size for PXE booting.  We are trying this because our boot.wim (approx 400mb) takes 10+ minutes to download when using the default TFTP block size setting.

To increase the TFTP block size we are adding the "RamDiskTFTPBlockSize" registry subkey to HKLM\Software\Microsoft\SMS\DP on our DP/PXE server.  We have tried multiple values of 16384, 8192 and 4096 for this subkey but all entries result in the issue detailed in the original post on this thread.  The details of this registry subkey are taken from http://support.microsoft.com/kb/968718/en-us.  Although this KB is specifically for SCCM 2007, it has been confirmed as still being valid for SCCM 2012, including in our testlab.

Our gut feeling is that this problem is related to the MTU in ESXi where SCCM is hosted, however it also appears the client NIC could be a contributing factor.

Has anyone else experienced this when altering the TFTP block size?  Would greatly appreciate any info...

• Edited by Deenos Wednesday, April 09, 2014 11:25 AM

Hi All,

Firstly, apologies for dragging this up again after so long but we are also experiencing this issue.  In our SCCM 2012 R2 environment it occurs when we try to increase the TFTP block size for PXE booting.  We are trying this because our boot.wim (approx 400mb) takes 10+ minutes to download when using the default TFTP block size setting.

To increase the TFTP block size we are adding the "RamDiskTFTPBlockSize" registry subkey to HKLM\Software\Microsoft\SMS\DP on our DP/PXE server.  We have tried multiple values of 16384, 8192 and 4096 for this subkey but all entries result in the issue detailed in the original post on this thread.  The details of this registry subkey are taken from http://support.microsoft.com/kb/968718/en-us.  Although this KB is specifically for SCCM 2007, it has been confirmed as still being valid for SCCM 2012, including in our testlab.

Our gut feeling is that this problem is related to the MTU in ESXi where SCCM is hosted, however it also appears the client NIC could be a contributing factor.

Has anyone else experienced this when altering the TFTP block size?  Would greatly appreciate any info...

We have the same issue no matter what size we use. Did you ever find a fix for this?

Hi all!

I was also experiencing similar problems with my PXE on SCCM 2012. I realize that this behavior, only happend on Network speed at 100 Mbps. Not on Gigabits segments. We have IP phones where all PC are connected at 100 Mbps, quite a drawback. So I deleted the  "RamDiskTFTPBlockSize" entry from the registry and restarted the WDS service on the server. It worked right away. But the download speed was slow, just before I added the  "RamDiskTFTPBlockSize" value to 16384. What I di, I try the  "RamDiskTFTPBlockSize" key again, but this time with a value to 8192. This fixed my problem. TFTP download is fast on 100 Mbps. Bether then before. Don't forget to restart the WDS service, each time you change the values or delete the entry.

Hope this help you!

Hi all

In my case the problem was easy

NAC was implemented on the network blocked TFTP

added exlusion and bam it worked

Have you enabled that the boot image should be deployed from a PXE Enabled Distribution Point?

http://www.danielclasson.com/dont-forget-this-step-when-you-want-clients-to-pxe-boot-using-configuration-manager-2012/

Is the boot image in the RemoteInstall folder on the server hosting the DP role?

Try to remove boot image from DP and add it again. Restart WDS server after that.

Hello

I have the same problem. I try resolve removing all packages with errors in the DP, delete and re crate boot image and add necesary drivers. finally re crate task sequence but the problem continue.after I'm reviewing the network segmentation, because I found out that my sccm VLAN is different from the client. I change the network port and EUREKA.

I know this is an older post but the problem seems to come back on us from time to time.

I had a the same problem in my PXE environment.  Server 2012 R2 and Server 2008 R2 running SCCM 2012 R2.  This issue came up where we could not image a certain model of Dell laptop.  The issue was initially handed to our network guys although it was dropped when we found that we were able to get it working from a different switch port.  (FYI all the ports were configured the same.) We let the issue go for a while and used that port with an unman-aged switch attached to get multiple images going at the same time.

Since then, the network crew has changed leaving the issue to come back at me to investigate deeper.

I started playing with the TFTP settings as suggested by others in this thread.  Changed from 16384 to 8192 to 4096 rebooting my PXE server in between.  The last setting of 4096 got it working again.  The strangest part is that it seemed to only be affecting this one model of Laptop.

Thanks Big Air - reducing RamDiskTFTPBlockSize fixed this problem when we were imaging some older laptops. Cheers!

Same issue here, running sccm2012 R2 CU3, cannot boot into PXE in a VM on VMware plateform.  Unless TFTP block size is tempered with in registry of SCCM 2012 R2 CU3.  What is the solution?