Quantcast
Channel: Configuration Manager 2012 - Application Management forum
Viewing all articles
Browse latest Browse all 4762

AppDiscovery.log - some clients run "Full application discovery", some not. why?

$
0
0

Hello,

we are tracking some issues on our clients which do not show new advertisements in software center, or still show old advertisements that have been deleted long ago. we have a question about appdiscovery.log.

we noticed that on some clients, the AppDiscovery.log file contains information that a "full application discovery" is run, e.g.:

++++++ Starting full application discovery on WMI namespace: root\Microsoft\policyplatform ++++++ AppDiscovery 22.10.2014 18:19:09 5664 (0x1620)
Performing enumeration in system context. AppDiscovery 22.10.2014 18:19:09 5664 (0x1620)
+++ Enumerating all applications which use Script detection, on WMI namespace: root\CCM\CIModels AppDiscovery 22.10.2014 18:19:09 5664 (0x1620)
Have 3 detection scripts for execution. AppDiscovery 22.10.2014 18:19:09 5664 (0x1620)
+++ Executing script to discover application. [AppDT Id: ScopeId_2067D847-40C7-4547-949A-75B7A0A0B9CE/DeploymentType_ea8695d1-9789-4bcd-833f-787479f0b7d9, Revision: 11] AppDiscovery 22.10.2014 18:19:09 5664 (0x1620)
+++ Application discovered [AppDT Id: ScopeId_2067D847-40C7-4547-949A-75B7A0A0B9CE/DeploymentType_ea8695d1-9789-4bcd-833f-787479f0b7d9, Revision: 11] AppDiscovery 22.10.2014 18:19:09 5664 (0x1620)
.... and so on, until:
+++++++ Full application discovery completed (2 seconds) ++++++ AppDiscovery 22.10.2014 18:19:11 5664 (0x1620)

on most other clients however, we do not see this kind of information, only some lines for a few applications, example:

+++ Did not detect app deployment type Foxit Reader 7.0.3.916(ScopeId_2067D847-40C7-4547-949A-75B7A0A0B9CE/DeploymentType_566234a0-a650-4e0f-94d8-92417556813f, revision 1) for system. AppDiscovery 22.10.2014 19:43:03 5056 (0x13C0)
Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_2067D847-40C7-4547-949A-75B7A0A0B9CE/DeploymentType_e972decd-dda9-4279-b3c4-89891af7d74c" AND Revision = 4)" AppDiscovery 22.10.2014 19:43:03 5056 (0x13C0)
    Performing detection of app deployment type 7Zip 9.20 x86(ScopeId_2067D847-40C7-4547-949A-75B7A0A0B9CE/DeploymentType_e972decd-dda9-4279-b3c4-89891af7d74c, revision 4) for system. AppDiscovery 22.10.2014 19:43:03 5056 (0x13C0)
+++ Application not discovered. [AppDT Id: ScopeId_2067D847-40C7-4547-949A-75B7A0A0B9CE/DeploymentType_e972decd-dda9-4279-b3c4-89891af7d74c, Revision: 4] AppDiscovery 22.10.2014 19:43:03 5056 (0x13C0)
+++ Did not detect app deployment type 7Zip 9.20 x86(ScopeId_2067D847-40C7-4547-949A-75B7A0A0B9CE/DeploymentType_e972decd-dda9-4279-b3c4-89891af7d74c, revision 4) for system. AppDiscovery 22.10.2014 19:43:03 5056 (0x13C0)
Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_2067D847-40C7-4547-949A-75B7A0A0B9CE/DeploymentType_8ed5bc4d-96cd-4433-a810-4e989f474563" AND Revision = 2)" AppDiscovery 22.10.2014 19:43:03 5056 (0x13C0)
    Performing detection of app deployment type Flash Player 11.7.700.169(ScopeId_2067D847-40C7-4547-949A-75B7A0A0B9CE/DeploymentType_8ed5bc4d-96cd-4433-a810-4e989f474563, revision 2) for system. AppDiscovery 22.10.2014 19:43:03 5056 (0x13C0)
+++ Application not discovered. [AppDT Id: ScopeId_2067D847-40C7-4547-949A-75B7A0A0B9CE/DeploymentType_8ed5bc4d-96cd-4433-a810-4e989f474563, Revision: 2] AppDiscovery 22.10.2014 19:43:03 5056 (0x13C0)
+++ Did not detect app deployment type Flash Player 11.7.700.169(ScopeId_2067D847-40C7-4547-949A-75B7A0A0B9CE/DeploymentType_8ed5bc4d-96cd-4433-a810-4e989f474563, revision 2) for system. AppDiscovery 22.10.2014 19:43:03 5056 (0x13C0)

why the difference in logfile contents? what is causing sccm to run a "full application discovery" instead of only running a discovery for some applications (looks like a kind of "delta discovery")?

can the full discovery be triggered somehow manually? we tried to modify "schedule re-evaluation for deployments" in a test client policy. this seems to have no effect.

thanks to everyone who can give me some insight on this.


Viewing all articles
Browse latest Browse all 4762

Latest Images

Trending Articles



Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>