We are trying to image a set of netbooks using the standard x86 Boot Image but we are running into problems with the TS claiming it can't find the program files for the boot image on the DP.  The exact error from the smstslog is:

<![LOG[Setting wizard error: This task sequence cannot be run because the program files for RCA00001 cannot be located on a distribution point. For more information, contact your system administrator or helpdesk operator.]LOG]!><time="09:03:30.045+00" date="01-28-2013" component="TSPxe" context="" type="0" thread="1308" file="tsmediawizardcontrol.cpp:1547">

The boot image is present on the DP, I have gone to the content status node on the monitoring tab and it shows 100% compliance.  I have updated the distribution point numerous times and I am seeing the following in the distmgr.log file:

Library path mismatch: \\?\D:\SCCMContentLib, D:\SCCMContentLib SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 6084 (0x17C4)
Expanding D:\SCCMContentLib\FileLib\CA6E\CA6E17210FA25A0AF2B860656B521E189DA4BF533E8BD534649364F00D5D7E14 from package RCA00002 SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 6084 (0x17C4)
Finding Wimgapi.Dll SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 6084 (0x17C4)
Found WAIK upgrade code SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 6084 (0x17C4)
SetFileAttributesW failed for E:\RemoteInstall\SMSTempBootFiles\RCA00002\Windows\Boot\EFI\bootmgfw.efi SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 6084 (0x17C4)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 6084 (0x17C4)
RemoveDirectoryW failed (0x80070091) for E:\RemoteInstall\SMSTempBootFiles\RCA00002\Windows\Boot\EFI SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 6084 (0x17C4)
SetFileAttributesW failed for E:\RemoteInstall\SMSTempBootFiles\RCA00002\Windows\Boot\Fonts\segmono_boot.ttf SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 6084 (0x17C4)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 6084 (0x17C4)
SetFileAttributesW failed for E:\RemoteInstall\SMSTempBootFiles\RCA00002\Windows\Boot\Fonts\segoen_slboot.ttf SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 6084 (0x17C4)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 6084 (0x17C4)
SetFileAttributesW failed for E:\RemoteInstall\SMSTempBootFiles\RCA00002\Windows\Boot\Fonts\segoe_slboot.ttf SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 6084 (0x17C4)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 6084 (0x17C4)
SetFileAttributesW failed for E:\RemoteInstall\SMSTempBootFiles\RCA00002\Windows\Boot\Fonts\wgl4_boot.ttf SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 6084 (0x17C4)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 6084 (0x17C4)
RemoveDirectoryW failed (0x80070091) for E:\RemoteInstall\SMSTempBootFiles\RCA00002\Windows\Boot\Fonts SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 6084 (0x17C4)
SetFileAttributesW failed for E:\RemoteInstall\SMSTempBootFiles\RCA00002\Windows\Boot\PXE\abortpxe.com SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 6084 (0x17C4)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 6084 (0x17C4)
SetFileAttributesW failed for E:\RemoteInstall\SMSTempBootFiles\RCA00002\Windows\Boot\PXE\bootmgr.exe SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 6084 (0x17C4)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 6084 (0x17C4)
SetFileAttributesW failed for E:\RemoteInstall\SMSTempBootFiles\RCA00002\Windows\Boot\PXE\pxeboot.com SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 6084 (0x17C4)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 6084 (0x17C4)
SetFileAttributesW failed for E:\RemoteInstall\SMSTempBootFiles\RCA00002\Windows\Boot\PXE\pxeboot.n12 SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 6084 (0x17C4)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 6084 (0x17C4)
SetFileAttributesW failed for E:\RemoteInstall\SMSTempBootFiles\RCA00002\Windows\Boot\PXE\wdsmgfw.efi SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 6084 (0x17C4)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 6084 (0x17C4)
SetFileAttributesW failed for E:\RemoteInstall\SMSTempBootFiles\RCA00002\Windows\Boot\PXE\wdsnbp.com SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 6084 (0x17C4)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 6084 (0x17C4)
RemoveDirectoryW failed (0x80070091) for E:\RemoteInstall\SMSTempBootFiles\RCA00002\Windows\Boot\PXE SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 6084 (0x17C4)
RemoveDirectoryW failed (0x80070091) for E:\RemoteInstall\SMSTempBootFiles\RCA00002\Windows\Boot SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 6084 (0x17C4)
RemoveDirectoryW failed (0x80070091) for E:\RemoteInstall\SMSTempBootFiles\RCA00002\Windows SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 6084 (0x17C4)
RemoveDirectoryW failed (0x80070091) for E:\RemoteInstall\SMSTempBootFiles\RCA00002 SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 6084 (0x17C4)
Expanding RCA00002 to E:\RemoteInstall\SMSImages SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 6084 (0x17C4)
STATMSG: ID=2330 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=RC-CFGMGR2012.riddlesdown.local SITE=RCA PID=2836 TID=6084 GMTDATE=Mon Jan 28 09:19:47.385 2013 ISTR0="RCA00002" ISTR1="["Display=\\RC-CFGMGR2012.riddlesdown.local\"]MSWNET:["SMS_SITE=RCA"]\\RC-CFGMGR2012.riddlesdown.local\" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="RCA00002" AID1=404 AVAL1="["Display=\\RC-CFGMGR2012.riddlesdown.local\"]MSWNET:["SMS_SITE=RCA"]\\RC-CFGMGR2012.riddlesdown.local\" SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 6084 (0x17C4)
Successfully created/updated the package server in the data source SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 6084 (0x17C4)
Performing cleanup prior to returning. SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 6084 (0x17C4)
DP thread with array index 0 ended. SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 5268 (0x1494)
DP thread with thread handle 0000000000002D60 and thread ID 6084 ended. SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 5268 (0x1494)
Created policy provider trigger for ID RCA00002 SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 5268 (0x1494)
Package RCA00002 does not have a preferred sender. SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 5268 (0x1494)
Package RCA00002 is new or has changed, replicating to all applicable sites. SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 5268 (0x1494)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=RCA00002, Version=8, Status=2301 SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 5268 (0x1494)
StoredPkgVersion (8) of package RCA00002. StoredPkgVersion in database is 8. SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 5268 (0x1494)
SourceVersion (8) of package RCA00002. SourceVersion in database is 8. SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 5268 (0x1494)
STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=RC-CFGMGR2012.riddlesdown.local SITE=RCA PID=2836 TID=5268 GMTDATE=Mon Jan 28 09:19:48.037 2013 ISTR0="Boot image (x64)" ISTR1="RCA00002" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="RCA00002" SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 5268 (0x1494)
Exiting package processing thread. SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 5268 (0x1494)

I noticed that something is failing... SetFileAttribuitessW failed and RemoveDirectoryW failed

Is this likely to be contributing to the problem?

did you uninstall the WAIK before installing the ADK before upgrading to SP1 ?

"Found WAIK upgrade code SMS_DISTRIBUTION_MANAGER 01/01/1601 00:00:00 6084 (0x17C4)"

Doesn't look like it no... It's still installed by the looks of things.  Is it just a case of uninstalling it?

Have you checked the Boundary Groups for content assignment?

• Proposed as answer by McAllstar Monday, January 28, 2013 2:37 PM

I've discovered it's connected to boundary groups.  I'd added another site to AD (in preparation for bringing a new site online) and I had forgotten to add a subnet to the Default Site.  Once that was done, OSD was working again.

• Marked as answer by adamf83 Monday, January 28, 2013 2:31 PM

Could you please be more specific, how you fixed that issue. 

Hey guys old question but still, just had an issue like this which i stuffed around with for ages. anyway in our unique situation it was a wan accelerator  (cisco wave) that was relaying something incorrectly. so if you have wan acceleration you probably should turn it off to see if that is affecting anything then redistribute everything.