0x80004005 error when using Applications in a Task Sequence

This is a second post in a matter of days and although I like the new App model I must admit I am far from impressed on its current stabilitly and apparent frailty when compared to regular packages.

Aside from the dependancy in and around Build & Captures, at present the revision history seems to play potential havoc inside of Task Sequences in certain instances as outlined below:

When building a machine from a Task Sequence, an application (or multiple) will fail and produce what is apparently an access denied message (0x80004005) however the NA Account is configured correctly and all boundaries are in place.

The source of the issue can be traced to the revision history in the Task Sequence being referenced to an incorrect version causing the install to fail.

This explanation is detailed in this excellent post
Although I like the new App model I feel it has some way to go before moving away from Packages all together.

Leave a Reply

Your email address will not be published. Required fields are marked *