failed to run task sequence due to missing content - show package ID not GUID
When you start a task sequence and it starts off by validating content. If it can't find a given package/application, it used to just say something like "content for package ID ABC000123 could not be found on any distribution points". That was super easy to find in the console and either update distribution points or whatever needed to be done.
With the 1702 update, it appears package ID has been replaced with ScopeID(longnastyGUID)/Application(Anotherlongnasty_GUID). When this happened to me last week, I couldn't find the ScopeID or Application GUID anywhere in the console, and had no idea which of the 5 billion logs to look in to find it. Eventually I figured it out by trial and error based on which apps were in TSes that worked versus apps that were in TSes that didn't work... Huge waste of several hours!
PLEASE bring back the simple Package ID instead of this GUID nonsense!
No response back, closing for 1802
The message you’re seeing is for Applications – Applications use CI’s rather than the ABC00001 you see for SWD Packages, Boot Images, Task Sequences etc.
In the Software Library, Applications – add CI Unique ID to the columns view. Type in the first few characters of the CI and any apps that match that are shown. You don’t need the column – I’m just suggesting that to help illustrate.
In the Task Sequence view, the References tab shows all referenced content and distribution status. Right-click on any item and you’ll be shown which Distribution Points have that item. Also, the Object ID will show the CI/GUID or Package Id depending on the item type.
Another option is selecting the Task Sequence and selecting Distribute Content – the wizard will show any referenced content that is not yet distributed.
Lastly, within the Admin Console there’s a powerful Search function which can traverse all objects, sub-folders etc. that can also identify the item for remediation.
Hope this helps you out somewhat, let me know.
Topaz Paul commented
Try the sccm task sequence deployment orchestrator. It checks content availability before the task sequence starts. www.sccmtspsi.com
Jeremy Cooper commented
This doesn't work for task sequences that are deployed to the local config manager client. From Software Center it does not provide the GUID.