App Deployment not discovered

Question

This is a new one for me. I have 5 computers that are failing all app deployments even though they are successfully installed. Its not the detection rule as hundreds of others are successful. Its not just one app either. These 5 are "failing" every app. Appenforce.log shows same message for all of them... +++ Application not discovered. I could understand if this was consistent for all but only these 5 laptops are failing. We are on MEM 2002, win 10 1809 for all of them. Below is a small sample of the appenforce.log. Its much longer with the same messages for all apps. Any ideas

++++++ App enforcement completed (0 seconds) for App DT "C++ 2015" [ScopeId_1A23F36E-C097-4536-8462-8EA9F925E71B/DeploymentType_093085b6-4286-45d3-8aa2-e9dcc14aa64d], Revision: 1, User SID: ] ++++++ AppEnforce 9/23/2020 8:37:13 PM 14620 (0x391C)
+++ Starting Install enforcement for App DT "Cisco Jabber - Windows Installer (.msi file)" ApplicationDeliveryType - ScopeId_1A23F36E-C097-4536-8462-8EA9F925E71B/DeploymentType_c6b82c4e-f19e-43f9-b9b7-1c41311809a0, Revision - 7, ContentPath - C:\WINDOWS\ccmcache\i6, Execution Context - System AppEnforce 9/23/2020 8:37:13 PM 14620 (0x391C)
Performing detection of app deployment type Cisco Jabber - Windows Installer (.msi file)(ScopeId_1A23F36E-C097-4536-8462-8EA9F925E71B/DeploymentType_c6b82c4e-f19e-43f9-b9b7-1c41311809a0, revision 7) for system. AppEnforce 9/23/2020 8:37:13 PM 14620 (0x391C)
+++ Application not discovered. [AppDT Id: ScopeId_1A23F36E-C097-4536-8462-8EA9F925E71B/DeploymentType_c6b82c4e-f19e-43f9-b9b7-1c41311809a0, Revision: 7] AppEnforce 9/23/2020 8:37:13 PM 14620 (0x391C)
App enforcement environment:
Context: Machine
Command line: msiexec /i "CiscoJabberSetup.msi" /q
Allow user interaction: No
UI mode: 0
User token: null
Session Id: 4294967295
Content path: C:\WINDOWS\ccmcache\i6
Working directory: AppEnforce 9/23/2020 8:37:13 PM 14620 (0x391C)
Prepared working directory: C:\WINDOWS\ccmcache\i6 AppEnforce 9/23/2020 8:37:13 PM 14620 (0x391C)
Found executable file msiexec with complete path C:\WINDOWS\system32\msiexec.exe AppEnforce 9/23/2020 8:37:13 PM 14620 (0x391C)
Prepared command line: "C:\WINDOWS\system32\msiexec.exe" /i "CiscoJabberSetup.msi" /q /qn AppEnforce 9/23/2020 8:37:13 PM 14620 (0x391C)
Valid MSI Package path = C:\WINDOWS\ccmcache\i6\CiscoJabberSetup.msi AppEnforce 9/23/2020 8:37:13 PM 14620 (0x391C)
Advertising MSI package [C:\WINDOWS\ccmcache\i6\CiscoJabberSetup.msi] to the system. AppEnforce 9/23/2020 8:37:13 PM 14620 (0x391C)
Executing Command line: "C:\WINDOWS\system32\msiexec.exe" /i "CiscoJabberSetup.msi" /q /qn with system context AppEnforce 9/23/2020 8:37:14 PM 14620 (0x391C)
Working directory C:\WINDOWS\ccmcache\i6 AppEnforce 9/23/2020 8:37:14 PM 14620 (0x391C)
Post install behavior is BasedOnExitCode AppEnforce 9/23/2020 8:37:14 PM 14620 (0x391C)
Waiting for process 4048 to finish. Timeout = 120 minutes. AppEnforce 9/23/2020 8:37:14 PM 14620 (0x391C)
Process 4048 terminated with exitcode: 0 AppEnforce 9/23/2020 8:37:20 PM 14620 (0x391C)
Looking for exit code 0 in exit codes table... AppEnforce 9/23/2020 8:37:20 PM 14620 (0x391C)
Matched exit code 0 to a Success entry in exit codes table. AppEnforce 9/23/2020 8:37:20 PM 14620 (0x391C)
Performing detection of app deployment type Cisco Jabber - Windows Installer (.msi file)(ScopeId_1A23F36E-C097-4536-8462-8EA9F925E71B/DeploymentType_c6b82c4e-f19e-43f9-b9b7-1c41311809a0, revision 7) for system. AppEnforce 9/23/2020 8:37:20 PM 14620 (0x391C)
+++ Application not discovered. [AppDT Id: ScopeId_1A23F36E-C097-4536-8462-8EA9F925E71B/DeploymentType_c6b82c4e-f19e-43f9-b9b7-1c41311809a0, Revision: 7] AppEnforce 9/23/2020 8:37:20 PM 14620 (0x391C)
++++++ App enforcement completed (6 seconds) for App DT "Cisco Jabber - Windows Installer (.msi file)" [ScopeId_1A23F36E-C097-4536-8462-8EA9F925E71B/DeploymentType_c6b82c4e-f19e-43f9-b9b7-1c41311809a0], Revision: 7, User SID: ] ++++++ AppEnforce 9/23/2020 8:37:20 PM 14620 (0x391C)
+++ Starting Install enforcement for App DT "C++ 2005" ApplicationDeliveryType - ScopeId_1A23F36E-C097-4536-8462-8EA9F925E71B/DeploymentType_5aa14414-bab8-47e7-99ba-aef4f6ae36a9, Revision - 3, ContentPath - C:\WINDOWS\ccmcache\ih, Execution Context - System AppEnforce 9/23/2020 8:37:20 PM 14620 (0x391C)
Performing detection of app deployment type C++ 2005(ScopeId_1A23F36E-C097-4536-8462-8EA9F925E71B/DeploymentType_5aa14414-bab8-47e7-99ba-aef4f6ae36a9, revision 3) for system. AppEnforce 9/23/2020 8:37:20 PM 14620 (0x391C)
+++ Application not discovered. [AppDT Id: ScopeId_1A23F36E-C097-4536-8462-8EA9F925E71B/DeploymentType_5aa14414-bab8-47e7-99ba-aef4f6ae36a9, Revision: 3] AppEnforce 9/23/2020 8:37:20 PM 14620 (0x391C)
App enforcement environment:
Context: Machine
Command line: "vcredist_x86-2005.EXE" /Q
Allow user interaction: No
UI mode: 0
User token: null
Session Id: 4294967295
Content path: C:\WINDOWS\ccmcache\ih
Working directory: AppEnforce 9/23/2020 8:37:20 PM 14620 (0x391C)
Prepared working directory: C:\WINDOWS\ccmcache\ih AppEnforce 9/23/2020 8:37:20 PM 14620 (0x391C)
Prepared command line: "C:\WINDOWS\ccmcache\ih\vcredist_x86-2005.EXE" /Q AppEnforce 9/23/2020 8:37:20 PM 14620 (0x391C)
Post install behavior is BasedOnExitCode AppEnforce 9/23/2020 8:37:21 PM 14620 (0x391C)
Waiting for process 11336 to finish. Timeout = 120 minutes. AppEnforce 9/23/2020 8:37:21 PM 14620 (0x391C)
Process 11336 terminated with exitcode: 0 AppEnforce 9/23/2020 8:37:22 PM 14620 (0x391C)
Looking for exit code 0 in exit codes table... AppEnforce 9/23/2020 8:37:22 PM 14620 (0x391C)
Matched exit code 0 to a Success entry in exit codes table. AppEnforce 9/23/2020 8:37:22 PM 14620 (0x391C)
Performing detection of app deployment type C++ 2005(ScopeId_1A23F36E-C097-4536-8462-8EA9F925E71B/DeploymentType_5aa14414-bab8-47e7-99ba-aef4f6ae36a9, revision 3) for system. AppEnforce 9/23/2020 8:37:22 PM 14620 (0x391C)
+++ Application not discovered. [AppDT Id: ScopeId_1A23F36E-C097-4536-8462-8EA9F925E71B/DeploymentType_5aa14414-bab8-47e7-99ba-aef4f6ae36a9, Revision: 3] AppEnforce 9/23/2020 8:37:22 PM 14620 (0x391C)
++++++ App enforcement completed (1 seconds) for App DT "C++ 2005" [ScopeId_1A23F36E-C097-4536-8462-8EA9F925E71B/DeploymentType_5aa14414-bab8-47e7-99ba-aef4f6ae36a9], Revision: 3, User SID: ] ++++++ AppEnforce 9/23/2020 8:37:22 PM 14620 (0x391C)
+++ Starting Install enforcement for App DT "Visual Studio Runtime 2010" ApplicationDeliveryType - ScopeId_1A23F36E-C097-4536-8462-8EA9F925E71B/DeploymentType_f7c1782c-cdad-45e7-9704-fec9abf04c67, Revision - 5, ContentPath - C:\WINDOWS\ccmcache\if, Execution Context - System AppEnforce 9/24/2020 9:27:00 AM 17420 (0x440C)
Performing detection of app deployment type Visual Studio Runtime 2010(ScopeId_1A23F36E-C097-4536-8462-8EA9F925E71B/DeploymentType_f7c1782c-cdad-45e7-9704-fec9abf04c67, revision 5) for system. AppEnforce 9/24/2020 9:27:00 AM 17420 (0x440C)
+++ Application not discovered. [AppDT Id: ScopeId_1A23F36E-C097-4536-8462-8EA9F925E71B/DeploymentType_f7c1782c-cdad-45e7-9704-fec9abf04c67, Revision: 5] AppEnforce 9/24/2020 9:27:00 AM 17420 (0x440C)
App enforcement environment:
Context: Machine
Command line: "vstor_redist.exe" /q /norestart
Allow user interaction: No
UI mode: 0
User token: null
Session Id: 4294967295
Content path: C:\WINDOWS\ccmcache\if
Working directory: AppEnforce 9/24/2020 9:27:00 AM 17420 (0x440C)
Prepared working directory: C:\WINDOWS\ccmcache\if AppEnforce 9/24/2020 9:27:00 AM 17420 (0x440C)
Prepared command line: "C:\WINDOWS\ccmcache\if\vstor_redist.exe" /q /norestart AppEnforce 9/24/2020 9:27:00 AM 17420 (0x440C)
Executing Command line: "C:\WINDOWS\ccmcache\if\vstor_redist.exe" /q /norestart with system context AppEnforce 9/24/2020 9:27:00 AM 17420 (0x440C)
Working directory C:\WINDOWS\ccmcache\if AppEnforce 9/24/2020 9:27:00 AM 17420 (0x440C)
Post install behavior is BasedOnExitCode AppEnforce 9/24/2020 9:27:00 AM 17420 (0x440C)
Waiting for process 10288 to finish. Timeout = 120 minutes. AppEnforce 9/24/2020 9:27:00 AM 17420 (0x440C)
Process 10288 terminated with exitcode: 0 AppEnforce 9/24/2020 9:27:06 AM 17420 (0x440C)
Looking for exit code 0 in exit codes table... AppEnforce 9/24/2020 9:27:06 AM 17420 (0x440C)
Matched exit code 0 to a Success entry in exit codes table. AppEnforce 9/24/2020 9:27:06 AM 17420 (0x440C)
Performing detection of app deployment type Visual Studio Runtime 2010(ScopeId_1A23F36E-C097-4536-8462-8EA9F925E71B/DeploymentType_f7c1782c-cdad-45e7-9704-fec9abf04c67, revision 5) for system. AppEnforce 9/24/2020 9:27:06 AM 17420 (0x440C)
+++ Application not discovered. [AppDT Id: ScopeId_1A23F36E-C097-4536-8462-8EA9F925E71B/DeploymentType_f7c1782c-cdad-45e7-9704-fec9abf04c67, Revision: 5] AppEnforce 9/24/2020 9:27:06 AM 17420 (0x440C)
++++++ App enforcement completed (6 seconds) for App DT "Visual Studio Runtime 2010" [ScopeId_1A23F36E-C097-4536-8462-8EA9F925E71B/DeploymentType_f7c1782c-cdad-45e7-9704-fec9abf04c67], Revision: 5, User SID: ] ++++++ AppEnforce 9/24/2020 9:27:06 AM 17420 (0x440C)

Answer 1

Hi,

Based on the above information, all the applications are installed successfully (exit code 0), however, based on the detection method we've configured, the applications are still regarded as "not installed", so the "+++ Application not discovered. " appears.

At such situation, we may check the detection configuration and confirm the client computer meets the requirement. For example, we set the registry as the detection method for x64 application, however, this 5 computers are x86 computers and the registry does not exist.

Hope the above information helps.

Alex Zhu

---

If the response is helpful, please click "Accept Answer" and upvote it.

Answer 2

We don't have any x86 so that's not it. Every computer is the same model, OS and architecture. I am doing the detection by MSI product code. I would change it but its detecting on 95% of the other computers. Not sure why these 5 aren't detecting on any install. Tried repairing the client and that didn't fix it.

Answer 3

Hi,

Thank you very much for your feedback. I mean we need to check (at the failed client computer) if the detection is met actually, x64 and x86 is just an example. It seems there is nothing related with the agent itself. Tring another detection is worth a shot.

Hope the above information helps.

Alex Zhu

---

If the response is helpful, please click "Accept Answer" and upvote it.

Answer 4

I am facing the same issue. 95% of systems received the application and reported successful. I have the exact same entries in the appenforce.log.

The endpoints I spot checked show the application installed and the MSI code is correct for the detection method I configured.

Does anyone suggest adding a detection method with the "or" statement or removing the existing detection method in favor of a new one?

If this doesn't pan out, I will have to spend support hours with MS to fix this, and hope it is a bug so the don't charge me.