I have an application with a 32bit MSI and a 64bit MSI.
We've deployed it to about 30 or 40 workstations with a notification that software is available to install. It installs with a /forcerestart which forces a prompt to restart.
Even after a restart, two users (one on Windows 7 32bit and one on Windows 7 64 bit) keep getting the notification that they should install the software. In Software Center, they see the application as "past due." When I monitor the
deployment, they both show as Pending "In Progress" a day later.
In their AppEnforce.log files, I see this:
+++ Starting Install enforcement for App DT "x86 Pulse Secure - Windows Installer (*.msi file)" ApplicationDeliveryType - ScopeId_AF3727D5-F64B-47C4-9158-7783F5F51D9A/DeploymentType_ed1cd639-3724-4315-ace4-31b21d4a9c7f, Revision - 2,
ContentPath - C:\windows\ccmcache\vl, Execution Context - SystemAppEnforce2/5/2016 2:02:18 PM4956 (0x135C)
A user is logged on to the system.
AppEnforce2/5/2016 2:02:18 PM4956 (0x135C)
Performing detection of app deployment type x86 Pulse Secure - Windows Installer (*.msi file)(ScopeId_AF3727D5-F64B-47C4-9158-7783F5F51D9A/DeploymentType_ed1cd639-3724-4315-ace4-31b21d4a9c7f, revision 2) for system.AppEnforce2/5/2016 2:02:18 PM4956 (0x135C)
+++ Application not discovered. [AppDT Id: ScopeId_AF3727D5-F64B-47C4-9158-7783F5F51D9A/DeploymentType_ed1cd639-3724-4315-ace4-31b21d4a9c7f, Revision: 2]AppEnforce2/5/2016 2:02:18 PM4956 (0x135C)
App enforcement environment:
Context: Machine
Command line: msiexec /i "JunosPulse.x86.msi" /qb+ /forcerestart
Allow user interaction: Yes
UI mode: 1
User token: null
Session Id: 4294967295
Content path: C:\windows\ccmcache\vl
Working directory: AppEnforce2/5/2016 2:02:18 PM4956 (0x135C)
Prepared working directory: C:\windows\ccmcache\vlAppEnforce2/5/2016 2:02:18 PM4956 (0x135C)
Found executable file msiexec with complete path C:\windows\system32\msiexec.exeAppEnforce2/5/2016 2:02:18 PM4956 (0x135C)
Prepared command line: "C:\windows\system32\msiexec.exe" /i "JunosPulse.x86.msi" /qb+ /forcerestartAppEnforce2/5/2016 2:02:18 PM4956 (0x135C)
Valid MSI Package path = C:\windows\ccmcache\vl\JunosPulse.x86.msiAppEnforce2/5/2016 2:02:18 PM4956 (0x135C)
Advertising MSI package [C:\windows\ccmcache\vl\JunosPulse.x86.msi] to the system.AppEnforce2/5/2016 2:02:18 PM4956 (0x135C)
Executing Command line: "C:\windows\system32\msiexec.exe" /i "JunosPulse.x86.msi" /qb+ /forcerestart with user contextAppEnforce2/5/2016 2:02:21 PM4956 (0x135C)
Working directory C:\windows\ccmcache\vlAppEnforce2/5/2016 2:02:21 PM4956 (0x135C)
Post install behavior is BasedOnExitCodeAppEnforce2/5/2016 2:02:21 PM4956 (0x135C)
Waiting for process 6012 to finish. Timeout = 20 minutes.AppEnforce2/5/2016 2:02:21 PM4956 (0x135C)
Process 6012 terminated with exitcode: 3010AppEnforce2/5/2016 2:02:58 PM4956 (0x135C)
Looking for exit code 3010 in exit codes table...AppEnforce2/5/2016 2:02:58 PM4956 (0x135C)
Matched exit code 3010 to a PendingSoftReboot entry in exit codes table.AppEnforce2/5/2016 2:02:58 PM4956 (0x135C)
++++++ App enforcement completed (39 seconds) for App DT "x86 Pulse Secure - Windows Installer (*.msi file)" [ScopeId_AF3727D5-F64B-47C4-9158-7783F5F51D9A/DeploymentType_ed1cd639-3724-4315-ace4-31b21d4a9c7f], Revision: 2, User
SID: ] ++++++AppEnforce2/5/2016 2:02:58 PM4956 (0x135C)
In their AppDiscovery.log files, I see this:
+++ Discovered application [AppDT Id: ScopeId_AF3727D5-F64B-47C4-9158-7783F5F51D9A/DeploymentType_ca53d815-e9cc-42d9-bf8a-1c7b92abcc9a, Revision: 4]AppDiscovery2/5/2016 2:01:46 PM2996 (0x0BB4)
+++ Evaluating expression to discover application. [AppDT Id: ScopeId_AF3727D5-F64B-47C4-9158-7783F5F51D9A/DeploymentType_4ed84a1b-daaa-426f-9cf5-98272f054c51, Revision: 5]AppDiscovery2/5/2016 2:01:46 PM2996 (0x0BB4)
+++ Application not discovered. [AppDT Id: ScopeId_AF3727D5-F64B-47C4-9158-7783F5F51D9A/DeploymentType_4ed84a1b-daaa-426f-9cf5-98272f054c51, Revision: 5]AppDiscovery2/5/2016 2:01:46 PM2996 (0x0BB4)
+++ Evaluating expression to discover application. [AppDT Id: ScopeId_AF3727D5-F64B-47C4-9158-7783F5F51D9A/DeploymentType_ef378df2-cfdf-4f35-9898-1692694a511f, Revision: 4]AppDiscovery2/5/2016 2:01:46 PM2996 (0x0BB4)
+++ Application not discovered. [AppDT Id: ScopeId_AF3727D5-F64B-47C4-9158-7783F5F51D9A/DeploymentType_ef378df2-cfdf-4f35-9898-1692694a511f, Revision: 4]AppDiscovery2/5/2016 2:01:46 PM2996 (0x0BB4)
+++ Evaluating expression to discover application. [AppDT Id: ScopeId_AF3727D5-F64B-47C4-9158-7783F5F51D9A/DeploymentType_5fa7608b-8258-4e56-9471-40f4ac673c57, Revision: 2]AppDiscovery2/5/2016 2:01:46 PM2996 (0x0BB4)
+++ Application not discovered. [AppDT Id: ScopeId_AF3727D5-F64B-47C4-9158-7783F5F51D9A/DeploymentType_5fa7608b-8258-4e56-9471-40f4ac673c57, Revision: 2]AppDiscovery2/5/2016 2:01:46 PM2996 (0x0BB4)
+++ Evaluating expression to discover application. [AppDT Id: ScopeId_AF3727D5-F64B-47C4-9158-7783F5F51D9A/DeploymentType_09f4e5d8-9f74-45d2-bb15-ffd7168c28a0, Revision: 2]AppDiscovery2/5/2016 2:01:46 PM2996 (0x0BB4)
+++ Application not discovered. [AppDT Id: ScopeId_AF3727D5-F64B-47C4-9158-7783F5F51D9A/DeploymentType_09f4e5d8-9f74-45d2-bb15-ffd7168c28a0, Revision: 2]AppDiscovery2/5/2016 2:01:46 PM2996 (0x0BB4)
+++ Evaluating expression to discover application. [AppDT Id: ScopeId_AF3727D5-F64B-47C4-9158-7783F5F51D9A/DeploymentType_0ab98991-f1d7-46b7-a736-a449ed89e84e, Revision: 13]AppDiscovery2/5/2016 2:01:46 PM2996 (0x0BB4)
+++ Application not discovered. [AppDT Id: ScopeId_AF3727D5-F64B-47C4-9158-7783F5F51D9A/DeploymentType_0ab98991-f1d7-46b7-a736-a449ed89e84e, Revision: 13]AppDiscovery2/5/2016 2:01:46 PM2996 (0x0BB4)
+++ Evaluating expression to discover application. [AppDT Id: ScopeId_AF3727D5-F64B-47C4-9158-7783F5F51D9A/DeploymentType_2e49fddd-2572-4a95-abe9-abf34bea5102, Revision: 2]AppDiscovery2/5/2016 2:01:46 PM2996 (0x0BB4)
+++ Discovered application [AppDT Id: ScopeId_AF3727D5-F64B-47C4-9158-7783F5F51D9A/DeploymentType_2e49fddd-2572-4a95-abe9-abf34bea5102, Revision: 2]AppDiscovery2/5/2016 2:01:46 PM2996 (0x0BB4)
+++ Evaluating expression to discover application. [AppDT Id: ScopeId_AF3727D5-F64B-47C4-9158-7783F5F51D9A/DeploymentType_ed1cd639-3724-4315-ace4-31b21d4a9c7f, Revision: 2]AppDiscovery2/5/2016 2:01:46 PM2996 (0x0BB4)
+++ Application not discovered. [AppDT Id: ScopeId_AF3727D5-F64B-47C4-9158-7783F5F51D9A/DeploymentType_ed1cd639-3724-4315-ace4-31b21d4a9c7f, Revision: 2]AppDiscovery2/5/2016 2:01:46 PM2996 (0x0BB4)
+++ Evaluating expression to discover application. [AppDT Id: ScopeId_AF3727D5-F64B-47C4-9158-7783F5F51D9A/DeploymentType_e1b8f539-ba74-46c3-92ec-09c8476f30e2, Revision: 7]AppDiscovery2/5/2016 2:01:46 PM2996 (0x0BB4)
+++ Application not discovered. [AppDT Id: ScopeId_AF3727D5-F64B-47C4-9158-7783F5F51D9A/DeploymentType_e1b8f539-ba74-46c3-92ec-09c8476f30e2, Revision: 7]AppDiscovery2/5/2016 2:01:46 PM2996 (0x0BB4)
+++ Local Handler found 9 applications, encountered 0 failures. (Elasped time = 0 seconds), Handler CLSID = {8B1B4B43-7CDE-4113-BDF5-3A02EAEA9B16}AppDiscovery2/5/2016 2:01:46 PM2996 (0x0BB4)
+++ Enumerating all App-V 5X applications.AppVHandler2/5/2016 2:01:46 PM2996 (0x0BB4)
A supported App-V 5X client is not installed. Will not discover any App-V 5X deployment typesAppVHandler2/5/2016 2:01:46 PM2996 (0x0BB4)
+++ AppV5X Handler found 0 applications, encountered 0 failures. (Elasped time = 0 seconds), Handler CLSID = {5B9C3324-906F-49EF-8318-41F9A07299A3}AppDiscovery2/5/2016 2:01:46 PM2996 (0x0BB4)
+++++++ Full application discovery completed (0 seconds) ++++++AppDiscovery2/5/2016 2:01:46 PM2996 (0x0BB4)
ActionType - Install will use Content Id: Content_6319f940-ab10-47e0-b824-0bc423c10075 + Content Version: 1 for AppDT "x86 Pulse Secure - Windows Installer (*.msi file)" [ScopeId_AF3727D5-F64B-47C4-9158-7783F5F51D9A/DeploymentType_ed1cd639-3724-4315-ace4-31b21d4a9c7f],
Revision - 2AppDiscovery2/5/2016 2:02:14 PM2996 (0x0BB4)
Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_AF3727D5-F64B-47C4-9158-7783F5F51D9A/DeploymentType_7301b6b0-6124-4b60-b503-37a9e7239b30" AND Revision = 2)"AppDiscovery2/5/2016 2:10:00 PM3040 (0x0BE0)
Performing detection of app deployment type x64 Pulse Secure - Windows Installer (*.msi file)(ScopeId_AF3727D5-F64B-47C4-9158-7783F5F51D9A/DeploymentType_7301b6b0-6124-4b60-b503-37a9e7239b30, revision 2) for system.AppDiscovery2/5/2016 2:10:00 PM3040 (0x0BE0)
+++ Application not discovered. [AppDT Id: ScopeId_AF3727D5-F64B-47C4-9158-7783F5F51D9A/DeploymentType_7301b6b0-6124-4b60-b503-37a9e7239b30, Revision: 2]AppDiscovery2/5/2016 2:10:00 PM3040 (0x0BE0)
+++ Did not detect app deployment type x64 Pulse Secure - Windows Installer (*.msi file)(ScopeId_AF3727D5-F64B-47C4-9158-7783F5F51D9A/DeploymentType_7301b6b0-6124-4b60-b503-37a9e7239b30, revision 2) for system.AppDiscovery2/5/2016 2:10:00 PM3040 (0x0BE0)
Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_AF3727D5-F64B-47C4-9158-7783F5F51D9A/DeploymentType_ed1cd639-3724-4315-ace4-31b21d4a9c7f" AND Revision = 2)"AppDiscovery2/5/2016 2:10:00 PM3040 (0x0BE0)
Performing detection of app deployment type x86 Pulse Secure - Windows Installer (*.msi file)(ScopeId_AF3727D5-F64B-47C4-9158-7783F5F51D9A/DeploymentType_ed1cd639-3724-4315-ace4-31b21d4a9c7f, revision 2) for system.AppDiscovery2/5/2016 2:10:00 PM3040 (0x0BE0)
+++ Application not discovered. [AppDT Id: ScopeId_AF3727D5-F64B-47C4-9158-7783F5F51D9A/DeploymentType_ed1cd639-3724-4315-ace4-31b21d4a9c7f, Revision: 2]AppDiscovery2/5/2016 2:10:00 PM3040 (0x0BE0)
+++ Did not detect app deployment type x86 Pulse Secure - Windows Installer (*.msi file)(ScopeId_AF3727D5-F64B-47C4-9158-7783F5F51D9A/DeploymentType_ed1cd639-3724-4315-ace4-31b21d4a9c7f, revision 2) for system.AppDiscovery2/5/2016 2:10:00 PM3040 (0x0BE0)
However, they've restarted and are using the updated software. It also shows up as the updated version in Resource Explorer and in Software 02D "Installed Software on a specific computer."
I requested that one user let me know what whether he has the MSI Product Code in the appropriate place in his registry and to give me a screen shot of his installed products list from Control Panel.
Anything else that I should be checking? What could cause the detection to fail? Presumably, the MSI Product Code detection that the MSI provided is correct. The other 40something users didn't have any troubles like this.
Thanks!