My OSD task sequence just failed again, and without posting the irrelevant stuff, I have 100% reason to believe the following excerpt from the smsts.log is the cause of my OSD TS woes (read: the OSD TS won't complete):

Setting wizard error: This task sequence cannot be run because the program files for ScopeId_8838E705-367A-45DD-8757-ADE20FDB9163/ Application_038b6b36-c13f-4489-a64f-ff6ea2877382 cannot be located on a distribution point. For more information, contact your system administrator or helpdesk operator.

I know for certain this is a DP-related issue. On that note, most of the OSD TS errors that are DP-related usually have a package ID (e.g - A0000123) instead of a directory of "ScopeId_8838E705-367A-45DD-8757-ADE20FDB9163/ Application_038b6b36-c13f-4489-a64f-ff6ea2877382" (like I am encountering).

On that note, does anyone have a way of hunting down this content? Yes I tried doing a search on "ScopeId_8838E705-367A-45DD-8757-ADE20FDB9163" or "Application_038b6b36-c13f-4489-a64f-ff6ea2877382" on the DPs.

Any help would be appreciated.. thanks!

Since it is in WinPE downloading the .wim I think smsts.log is your only option for logging. If it doesnt list the package ID there you may have to enable debug logging to get more info.

Personally, when I get content issue like this I just check the References of the task sequence and check for two things.

1. All content shows 100%

2. All content that should be more than 0 MB is actually.

If you have a suspect package, just update distribution points so the package revision increases, then try to run the task sequence again.

You can try having a look at the DB tables.  There are 2 for standard packages.  If you have the TS configured to run from DP, also make sure that all packages are set to copy to a package share.  If not, you need to just update the package on your distribution points.  You may have a version issue.

"Run from DP" won't help if the client is not able to find the content on the DP at all. So it does not matter if it tries to download or run from DP.

Just add the GUID column in the console (Applications) so that you can see which application belongs to the GUID.

If he configured Run from DP, and distributed the packages to the distribution point, it would fail unless he also had Copy to Package Share enabled.  The message is identical whether Run from DP without the share or Download and Run without the package being distributed. 

In the DB, look for two tables, dbo.smspackages_G and dbo.smspackages_L  Use a query to target the GUID from your log.