Hello,

In my task sequence, any application that i add fails to install with Error Code 0x87d00215. Outside of the task sequence the applications install with no problems. 

 

 

A couple things that i have verified already

DP is set to allow clients to connect anonymously

Network Access Account is set and verified

Setting on the application for Allow this application to be installed from the Install Application task sequence action instead of deploying it manually is set

Boundaries are set correctly as software installs correctly outside of the TS 

 

 

Logs that do not show errors

IIS logs - Check out just fine

Location Services - Does not show any errors and finds the AD Forest/Site and MP successfully 

CAS Log - Does not show any errors with the correct date

Data Transfer Log - Does not show any error with the correct date

 

 

Any ideas would be greatly appreciated.

Thanks 

Ok, I figured this out; the application that I was deploying in the task sequence had two deployment types, one for 32bit and one for 64. After removing the 64bit deployment type the task sequence now installs the application. So with that being said, does anyone know how the task sequence evaluates the deployment types?

Thanks 

After continuing on after i thought i had this figured out, I can still not deploy applications during the TS. Applications all deploy successfully while in the OS but not during the TS. Every application that tries to install gets this in the log

Policy evaluation initiated

Policy Evaluation failed, hr=0x87d00215

Application failed to evaluate

No application state information is available

Exhausted retry attempts. Giving up

Install application action failed: (Application Name) Error Code 0x80004005

Any Ideas?

Also noticed these in the logs if it helps

 

SMSTS.Log

CAppMgmtSDK::GetEvaluationState ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/RequiredApplication_e4048d56-cfa1-43e0-b4df-f30b6a834828

Passed in version 6 for ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/RequiredApplication_e4048d56-cfa1-43e0-b4df-f30b6a834828

spCIStateStore->GetCIState( pszAppPolicyId, csPolicyRevision, (sUserSID.length()>0) ? sUserSID.c_str() : 0, &spPolicyState), HRESULT=87d00215 (e:\nts_sccm_release\sms\dcm\sdk\cisdkclass.cpp,1965)

CAppMgmtSDK::GetEvaluationState - ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/RequiredApplication_e4048d56-cfa1-43e0-b4df-f30b6a834828.6 Not found in CI state store. Marking CIs state as EvaluationFailed

NotifyProgress received: 16 (Application failed to evaluate )

 

 

CIStore.log

CCIStore::Notify - Targeting Change: __InstanceCreationEvent for CI with Model Name ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/RequiredApplication_e4048d56-cfa1-43e0-b4df-f30b6a834828, Version 6

CCIStore::Notify - CI Model Name ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/RequiredApplication_e4048d56-cfa1-43e0-b4df-f30b6a834828, Version 6 is now targeted for user .

CCIStore::ProcessCITargetEvent - CI ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/RequiredApplication_e4048d56-cfa1-43e0-b4df-f30b6a834828:6 will be targeted for SYSTEM

CCIStoreTargetedCIDownloader::AddCI - CI Modelname:ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/RequiredApplication_e4048d56-cfa1-43e0-b4df-f30b6a834828 Version:6 has been added for download

 

 

CIStateStore.log

CCIStateStore::CacheCIState - CI ModelName ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/RequiredApplication_e4048d56-cfa1-43e0-b4df-f30b6a834828, Revision 6 will be cached for SYSTEM

CCIStateStore::CacheCIState - CI ModelName ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/RequiredApplication_e4048d56-cfa1-43e0-b4df-f30b6a834828, Revision 6 already cached for SYSTEM

CIStateStore 5/24/2012 11:53:16 AM

2556 (0x09FC)

CCIStateTransition::ExtractStateDetails - CI ModelName ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/RequiredApplication_e4048d56-cfa1-43e0-b4df-f30b6a834828, version 6 not found in store.

Do you have a Network Access Account defined in SCCM/ConfigMgr?

http://www.jamesbannanit.com/2011/04/configure-the-network-access-account-in-sccm-2012/

Henk, 

I do have the network access account defined and verified. I just switched it to another domain account just to be sure and tested again. Applications still do not install during the TS, same errors

Did you get this working? I have same problem.

Is there anything useful in AppDiscovery.log, AppEnforce.log and AppIntentEval.log?

Nope. There's only information about first application and its dependencies. Smsts.log referred to another log files with job numbers. There wasn't either nothing more information about application installation than "Application 1 has dependecies "A" and "B"" and then it looks forward those packages. It seems that it cannot access files in DP (from smsts.log: Execution status received: 24 (Application download failed )). All applications are distributed to Distribution Point and Network Access Account has access to DP.

I don't know about applications (don't know the way) but packages are accessible from client machine with browser http://cm12server/SMS_DP_SMSPKG$/<PACKAGE_ID>.

I have machines in same network. Operating system and packages will be installed normally during task sequence. Only application mode installation fails.

The AppEnforce log is empty and below are some bits from the AppDiscovery log and the AppIntentEval log which I did not see anything unusual.

 

 

AppDiscovery.log

    Performing detection of app deployment type VMware Tools x32(ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_9fbcb77f-c553-45d8-9d5b-b4a6c2c0d4a1, revision 2) for system.
+++ Application not discovered. [AppDT Id: ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_9fbcb77f-c553-45d8-9d5b-b4a6c2c0d4a1, Revision: 2]
+++ Did not detect app deployment type VMware Tools x32(ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_9fbcb77f-c553-45d8-9d5b-b4a6c2c0d4a1, revision 2) for system.
Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_955d0646-14a5-47d6-8146-be5811818c8f" AND Revision = 2)"
    Performing detection of app deployment type Adobe AIR - Windows Installer (Native)(ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_955d0646-14a5-47d6-8146-be5811818c8f, revision 2) for system. 
+++ Application not discovered. [AppDT Id: ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_955d0646-14a5-47d6-8146-be5811818c8f, Revision: 2]
+++ Did not detect app deployment type Adobe AIR - Windows Installer (Native)(ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_955d0646-14a5-47d6-8146-be5811818c8f, revision 2) for system.
Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_fb1b4e3f-0600-4682-a865-37ec2bdf3255" AND Revision = 1)"
    Performing detection of app deployment type Adobe Reader X MUI - Windows Installer (Native)(ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_fb1b4e3f-0600-4682-a865-37ec2bdf3255, revision 1) for system.
+++ MSI application not discovered [MSI Product Code: {AC76BA86-7AD7-FFFF-7B44-AA0000000001}, MSI Product version: ]
+++ Did not detect app deployment type Adobe Reader X MUI - Windows Installer (Native)(ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_fb1b4e3f-0600-4682-a865-37ec2bdf3255, revision 1) for system.
Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_7b131081-c490-4a74-9595-c97a03b54bf2" AND Revision = 2)"
    Performing detection of app deployment type Adobe Shockwave Player 11.6 - Windows Installer (Native)(ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_7b131081-c490-4a74-9595-c97a03b54bf2, revision 2) for system.
+++ Application not discovered. [AppDT Id: ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_7b131081-c490-4a74-9595-c97a03b54bf2, Revision: 2]
+++ Did not detect app deployment type Adobe Shockwave Player 11.6 - Windows Installer (Native)(ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_7b131081-c490-4a74-9595-c97a03b54bf2, revision 2) for system.
Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_dc3e58ae-3e78-4ba5-8e13-8b4e565899c4" AND Revision = 6)"
    Performing detection of app deployment type Flash(ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_dc3e58ae-3e78-4ba5-8e13-8b4e565899c4, revision 6) for system.
+++ Application not discovered. [AppDT Id: ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_dc3e58ae-3e78-4ba5-8e13-8b4e565899c4, Revision: 6]
+++ Did not detect app deployment type Flash(ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_dc3e58ae-3e78-4ba5-8e13-8b4e565899c4, revision 6) for system.
Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_f5c8beed-13f7-4c10-82f6-640c7c314038" AND Revision = 2)" AppDiscovery 5/23/2012 3:10:56 PM 3520 (0x0DC0)
    Performing detection of app deployment type VMware Tools x64(ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_f5c8beed-13f7-4c10-82f6-640c7c314038, revision 2) for system
+++ Application not discovered. [AppDT Id: ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_f5c8beed-13f7-4c10-82f6-640c7c314038, Revision: 2]
+++ Did not detect app deployment type VMware Tools x64(ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_f5c8beed-13f7-4c10-82f6-640c7c314038, revision 2) for system.

AppIntectEval.log

ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_01c75763-a985-4a58-99fc-35e5b5380106/2 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = Project 2010 Pro - Silent AppIntentEval 5/23/2012 3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_4680375d-efcf-411b-8901-233d7a9694aa/1 :- Current State = NotInstalled, Applicability = NotApplicable, ResolvedState = None, Title = Autodesk 2012 64bit AppIntentEval 5/23/2012 3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_5f72c7c1-b695-4f8d-b754-f8f6d1aa4046/9 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = Autodesk 2012 32bit AppIntentEval 5/23/2012 3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_7b131081-c490-4a74-9595-c97a03b54bf2/2 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = Adobe Shockwave Player 11.6 - Windows Installer (Native) AppIntentEval 5/23/2012 3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_9365b2e3-d0a3-4486-88bb-a7071d9b047b/4 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = LogMeIn - Windows Installer (Native) AppIntentEval 5/23/2012 3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_955d0646-14a5-47d6-8146-be5811818c8f/2 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = Adobe AIR - Windows Installer (Native) AppIntentEval 5/23/2012 3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_9fbcb77f-c553-45d8-9d5b-b4a6c2c0d4a1/2 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = VMware Tools x32 AppIntentEval 5/23/2012 3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_dc3e58ae-3e78-4ba5-8e13-8b4e565899c4/6 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = Flash AppIntentEval 5/23/2012 3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_f5c8beed-13f7-4c10-82f6-640c7c314038/2 :- Current State = NotInstalled, Applicability = NotApplicable, ResolvedState = None, Title = VMware Tools x64 AppIntentEval 5/23/2012 3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_f8a1de4d-ffa9-4ba6-b51b-7e9a6810cfda/3 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = Silent Install AppIntentEval 5/23/2012 3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_fb1b4e3f-0600-4682-a865-37ec2bdf3255/1 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = Adobe Reader X MUI - Windows Installer (Native) AppIntentEval 5/23/2012 3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/Application_07eed4d3-7acf-4717-93f9-74f717a191b4/5 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = LogMeIn Client AppIntentEval 5/23/2012 3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/Application_0bce5378-1b95-45ea-b210-e72cb65b2b37/3 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = Project 2010 Pro AppIntentEval 5/23/2012 3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/Application_808fe5d5-5b90-48aa-83cb-f5497d534691/6 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = VMware Tools AppIntentEval 5/23/2012 3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/Application_b1a04314-2a3a-47e2-98a0-ff09fc8e3948/3 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = Adobe AIR AppIntentEval 5/23/2012 3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/Application_b614de9b-5133-4788-a013-71c7de98a233/11 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = AutoCAD 2012 AppIntentEval 5/23/2012 3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/Application_c4ccbd68-7c0f-4b79-9437-eba3cb46e90c/5 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = Shockwave Player 11.6 AppIntentEval 5/23/2012 3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/Application_dec4acbc-b968-41d9-82e6-3f7767467c8e/2 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = Reader X AppIntentEval 5/23/2012 3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/Application_e4048d56-cfa1-43e0-b4df-f30b6a834828/3 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = Application Virtualization Client with SP1 and HF4 AppIntentEval 5/23/2012 3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/Application_ee3b1dcf-e401-44fe-8283-a6e5721dac11/10 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = Adobe Flash Player AppIntentEval 5/23/2012 3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/RequiredApplication_07eed4d3-7acf-4717-93f9-74f717a191b4/5 :- Current State = NonCompliant, Applicability = Applicable, ResolvedState = Compliant, Title = ApplicationIntentPolicy AppIntentEval 5/23/2012 3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/RequiredApplication_0bce5378-1b95-45ea-b210-e72cb65b2b37/3 :- Current State = NonCompliant, Applicability = Applicable, ResolvedState = Compliant, Title = ApplicationIntentPolicy AppIntentEval 5/23/2012 3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/RequiredApplication_808fe5d5-5b90-48aa-83cb-f5497d534691/6 :- Current State = NonCompliant, Applicability = Applicable, ResolvedState = Compliant, Title = ApplicationIntentPolicy AppIntentEval 5/23/2012 3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/RequiredApplication_b1a04314-2a3a-47e2-98a0-ff09fc8e3948/3 :- Current State = NonCompliant, Applicability = Applicable, ResolvedState = Compliant, Title = ApplicationIntentPolicy AppIntentEval 5/23/2012 3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/RequiredApplication_b614de9b-5133-4788-a013-71c7de98a233/11 :- Current State = NonCompliant, Applicability = Applicable, ResolvedState = Compliant, Title = ApplicationIntentPolicy AppIntentEval 5/23/2012 3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/RequiredApplication_c4ccbd68-7c0f-4b79-9437-eba3cb46e90c/5 :- Current State = NonCompliant, Applicability = Applicable, ResolvedState = Compliant, Title = ApplicationIntentPolicy AppIntentEval 5/23/2012 3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/RequiredApplication_dec4acbc-b968-41d9-82e6-3f7767467c8e/2 :- Current State = NonCompliant, Applicability = Applicable, ResolvedState = Compliant, Title = ApplicationIntentPolicy AppIntentEval 5/23/2012 3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/RequiredApplication_e4048d56-cfa1-43e0-b4df-f30b6a834828/3 :- Current State = NonCompliant, Applicability = Applicable, ResolvedState = Compliant, Title = ApplicationIntentPolicy AppIntentEval 5/23/2012 3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/RequiredApplication_ee3b1dcf-e401-44fe-8283-a6e5721dac11/10 :- Current State = NonCompliant, Applicability = Applicable, ResolvedState = Compliant, Title = ApplicationIntentPolicy AppIntentEval 5/23/2012 3:10:56 PM 1912 (0x0778)

Nope. There's only information about first application and its dependencies. Smsts.log referred to another log files with job numbers. There wasn't either nothing more information about application installation than "Application 1 has dependecies "A" and "B"" and then it looks forward those packages. It seems that it cannot access files in DP (from smsts.log: Execution status received: 24 (Application download failed )). All applications are distributed to Distribution Point and Network Access Account has access to DP.

I don't know about applications (don't know the way) but packages are accessible from client machine with browser http://cm12server/SMS_DP_SMSPKG$/<PACKAGE_ID>.

I have machines in same network. Operating system and packages will be installed normally during task sequence. Only application mode installation fails.

I was able to install now Applications. I created only Distribution Point Group and added my only Distribution Point to it and enabled content location and site assigment in that Distribution Point Group.

- Markus

Are you building a reference image at the moment or deploying a captured image?  If it is the former, try adding SMSMP=yourmp.domain.com to the "Setup Windows and ConfigMgr" TS Step options.

Exactly where do You specify this "deployment rule" ? Do you mean "requirement" in the deployment type for the application?

Hello All,

I have exactly the same problem: impossible to install applications during task sequences (rule for 32 and rule for 64). seems to be an access denied somewhere, but where ? also error 24 status received: 24 (Application download failed ).

When i check the distribution point at smspkgd$, the content is not there; maybe it's normal as this one is present in the SCCMContenLib folder. I don't understand why this folder exisit and what's the content location. Should i add access rights to this SCCMContenlib folder, or in IIS (note: only HTTP is enabled)

Thanks in advance

I'm hoping this will help someone on the forums...

I was having this exact same problem. Packages would install fine during my OSD task sequence, but Applications failed. Looking through logs, I saw various errors: 24(Application download failed), error code 0x87D00607, etc. 

I tried everything I could think of, updated content on distribution points, deleted and re-created applications, etc. Even confirmed I had boundary groups set up correctly.

Finally, it dawned on me that I had recently set up the migration piece between our old SCCM 2007 hierarchy and had enabled distribution point sharing. This step created boundary groups so SCCM 2012 clients could connect to SCCM 2007 DPs. In these new groups, there was one that contained AD sites that were in my new SCCM 2012 boundary groups. This created duplicate boundaries and my clients didn't know where to go for their content. Once I deleted the boundary group created from sharing DPs, applications installed correctly.

Hello,

I encountered the same problem during the build of my TS deployment. No applications was deployed during this process

Error message 0x800004005 and Execution status received: 24 (Application download failed).

Finally, i found a solution which solve my problem. Go through your Application definition and Deployment Type tab. Edit your(s) deployment type and select content tab. In the scroll menu called Deployment options ... select "download content from distribution point and run locally"

I don't know why, because this setting is normally used for slow link (and this is not my case) but it solved my problem.

Hope it help you.

Hello to all,

I had the same problem with the distribution of Client Workgroup. I solved it by providing the following properties to the Client Agent in Task Sequence:

SMSMP=sccm2012.domain.it DNSSUFFIX=domain.it

I created a DP Group and assigned the content to the group.

Vid.

Hello,

I encountered the same problem during the build of my TS deployment. No applications was deployed during this process

Error message 0x800004005 and Execution status received: 24 (Application download failed).

Finally, i found a solution which solve my problem. Go through your Application definition and Deployment Type tab. Edit your(s) deployment type and select content tab. In the scroll menu called Deployment options ... select "download content from distribution point and run locally"

I don't know why, because this setting is normally used for slow link (and this is not my case) but it solved my problem.

Hope it help you.

I only had one package in the OSD TS that would error.  Lync x64 was the only package that failed to deploy to Windows 7 Enterprise x64.  Setting the "download content from distribution point and run locally" as recommended by Fugazy resolved my issue.

Thanks,

Mike

I had an working environment, but after updating my image offline with DISM, I also got this problem.

After spending hours going through forums, reading logs and finally start using process monitor I found something really weard. I have a step with "Use MDT toolkit Package" because I need some scripts. There is a folder called Templates\GPOPacks which seemed to be applied with every software. After removing the folder GPOPacks and updating my DP, everything started working again...

/Daniel

I only had one package in the OSD TS that would error.  Lync x64 was the only package that failed to deploy to Windows 7 Enterprise x64.  Setting the "download content from distribution point and run locally" as recommended by Fugazy resolved my issue.

Thanks,

Mike

Me too!

All my applications and packages worked in my TS deployment apart from 2, both were packages.

I added a reboot in to the task sequence and this seemed to fix it. Simple, but there you go.

All my applications and packages worked in my TS deployment apart from 2, both were packages.

I added a reboot in to the task sequence and this seemed to fix it. Simple, but there you go.

This fixed it for me, but I just had to understand why packages were successful, but Applications were not.

It is because Applications have dependencies and Detection methods. Essentially, the reboot fixes it because it then boots into proper Windows (be sure to select "the currently installed default operating system" radio button in the restart computer task) and this environment is capable of detecting the dependencies and detecting a successful install. 

In my case, I have a few driver packages that reboot into Windows before installing applications, so I added the mirror opposite WMI query into my reboot task to ensure the computer isn't rebooted twice (another way would be to use a query that would detect if the machine was already in Windows Proper, but perhaps someone else will post that query).

Hello,

I ran into this issue as well. Applications would not install during OSD, but worked just fine when deploying to an existing OS.

The problem for me was in the boundary groups in the References tab -> Content location. I had only defined my primary site server as being Fast, but not my SQL which is running on another server.

Adding my SQL to the boundary group as a fast connection solved the problem.

Hope this helps.

Martin

In my case the "Application failed to evaluate" because the machine was not domain joined.

The same applications would install just fine through the Software Center/Configuration Manager client, but of course I was on the domain at that time.

I was trying to install applications as part of my Build and Capture task sequence and I didn't want to join the domain in order to keep the build clean of any unnecessary GPOs.

But the applications would only install as part of the Task sequence if I joined my domain.

Here's two possible solutions I may try.. may work for you
http://www.bpmi.nl/blog/?p=1637

There's no requirement to be joined to a domain.

The two things that need to be done are

- Add the SMSMP property to the Setup and ConfigMgr task (contrary to that blog post, this is not problematic if you have multiple MPs within a primary site, you just pick one -- who cares which one)

- And install the hotfix from KB2522623: http://blog.configmgrftw.com/?p=490

So with multiple sites and management points... this won't force the use of a specific site MP for the life of that machines install right? Just during OSD?

Will it still be able to fail over to another MP if it becomes unavailable in the future?

http://technet.microsoft.com/en-us/library/gg699356.aspx: "Specifies an initial management point for the Configuration Manager client to use. "

Don't think of an MP at a secondary site as an MP, it serves a slightly different purpose in life. In 2007 and before they were called proxy MPs. Although that's not really accurate for 2012, hence the reason they are not called that anymore, they are not full-fledged MPs either and only contain a subset of the required information and also cannot do things like register clients.

Connectivity to the MP at the primary site is always required and is explicitly needed during initial client setup.