ConfigMgr : Erratic Task Sequence Application Deployment Failure

I’ve seen this issue with Windows 7, Windows 8 and Windows 8.1 deployments via SCCM 2012 SP1 and SP1 CU3 – almost at random an OSD Task Sequence will fail with a “0x80004005” error, deploying an application that I know:

  • Works outside of a Task Sequence
  • Exists on the required Distribution Point used during OSD
  • Worked on the last X builds, using the exact same Task Sequence

Interestingly, in my case at least, it was always the same application that caused the problem.

Tracing the error reveals an interesting “feature” in SCCM 2012 SP1 and SP1 CU3; the AppDiscovery.log shows the client is missing the application in question, and that the installation is launched:

{code lang:text showtitle:false lines:false hidden:false}ActionType – Install will use Content Id: Content_2956d9e2-e279-4868-a70c-4ea95cb55004 + Content Version: 1 for AppDT “Microsoft Office ProfessionalPlus 2013 X86 EN – SCRIPT” [ScopeId_43347163-BC72-4CCA-A9E9-DBCC13F55603/DeploymentType_9ebdc693-4a51-46c2-afe3-1fb24eab15ea], Revision – 10{/code}

What is interesting here is that the Revision Number is not the “current” revision, i.e. the the T/S is looking for revision 10, whereas revision 11 is the current revision.

As a workaround, until there is a real fix for this issue, perform the following tasks:

  1. Remove the application from the Task Sequence
  2. Disable the Install Applictaion step
  3. Save the Task Sequence
  4. Close and Open TS editor
  5. Re-add the application and re-enable the Install Application step
  6. Save the Task Sequence

Alternatively, as described from the link below, you can put the offending application into is own Install Application step (instead of having multiple applications in one step).

The same errors is reported here (in much more detail) with more details on this workaround: