Application Deployment Failure

Question

_{Friday, July 14, 2017 4:58 PM}

Hi,

help to troubleshoot application deployment 

1. If a application is deployed to a workstation and it not received to the machine. (means application is not seen in AppEnforceog

For example, refer the below AppEnforce.log. I do understand why application is failed

rforming detection of app deployment type InterVideo (ScopeId_7C39EE49-F1CA-4C54-93A4-9497D1354672/DeploymentType_fae91010-6ff3-4eb0-9a3e-cc8e31459d81, revision 5) for system
+++ Application not discovered. [AppDT Id: ScopeId_7C39EE49-F1CA-4C54-93A4-9497D1354672/DeploymentType_fae91010-6ff3-4eb0-9a3e-cc8e31459d81, Revision: 5]
    App enforcement environment: 
Context: Machine
Command line: "Install.vbs"
Allow user interaction: No
UI mode: 1
User token: null
Session Id: 4294967295
Content path: 
Working directory: 
    Prepared working directory: C:\WINDOWS\system32
Invalid data file "Install.vbs" to execute using file association
PrepareCommandline failed with 0x87d01106 for cmdline "Install.vbs"
ScriptHandler::EnforceApp failed (0x87d01106).
AppProvider::EnforceApp - Failed to invoke EnforceApp on Application handler(0x87d01106)
CommenceEnforcement failed with error 0x87d01106
Method CommenceEnforcement failed with error code 87D01106
++++++ Failed to enforce app. Error 0x87d01106. ++++++

2. What are the Client Side troubleshooting steps need to be performed for an Application Deployed

3. If there are no activity seen in the AppEnforce.log

Regards, Boopathi

All replies (6)

_{Friday, July 14, 2017 7:07 PM}

For your example, did you use an MSI deployment type and now you are trying to run a .vbs?

Troubleshooting steps are always variable. First you identify where you think the problem is and dig deeper into that specific area. In ConfigMgr that often means looking in the log file, find the error, and interpreting the error.

If nothing is seen in appenforce.log, then the client probably hasn't gotten the policy and may not even be communicating with the site. You need to make sure the client is communicating successfully first and then review your application to make sure there's nothing wrong with it.

Jason | http://blog.configmgrftw.com | @jasonsandys

_{Monday, July 17, 2017 7:12 AM}

0x87d01106 = "Failed to verify the executable file is valid or to construct the associated command line."

Have you tried to manually run Install.vbs?

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Monday, July 17, 2017 2:27 PM}

0x87d01106 = "Failed to verify the executable file is valid or to construct the associated command line."

Which happens when you try to use an msiexec command line in a Windows Installer deployment type which is why I pointed that out. I don't think that was his exact question though, that was just an example.

Jason | http://blog.configmgrftw.com | @jasonsandys

_{Wednesday, August 23, 2017 11:45 AM}

Hello there,
I am having the same problem. I do not have a solution so far, but what I found is where the problem is:

* Prepared working directory: C:\WINDOWS\system32*

This is, where things go wrong, it is supposed to be C:\windows\ccmcache\some-number. I am pretty sure this is a 32bit / 64bit problem and SCCM for whatever reason ends up in a tree, where the path to the executable is no longer valid.

I am on it and will keep you posted here, if I come any further.

Bernie

_{Wednesday, August 23, 2017 4:13 PM}

Ok Bernie. 

Regards, Boopathi

_{Tuesday, October 31, 2017 11:35 PM}

Any luck with this? I have this issue on a bunch of PCs too and I can't see where it's going wrong...