Forum Discussion
SCCM is not detecting installed applications
We use the product code for detection: {E57F8E37-C7DB-3CF8-82E4-98423E05EF63} . Check yours that you want to deploy.
This is plain and simple. Maybe you add the printscreen of the detection rule you use so we can help?
Good luck!
danielkaliel If you're enabling the "This file or folder is associated with a 32-bit application on 64-bit systems" option for the Detection Rule, then you should use the "%ProgramFiles%" environment variable in the path. Enabling that option will cause the ConfigMgr client to use the actual "%ProgramFiles%" variable on 64-bit systems, and the "%ProgramFiles(x86)%" variable on 32-bit systems.
It doesn't matter if the application is deployed as Available or Required. In both cases, the Detection Method is used to determine if the application is installed or not. If the application is not detected after the installation command line is completed successfully (based on the return code), that will result in an error along the lines of "Application not detected after enforcement". This is an indication that the Detection Method is incorrect.
I was expecting the section of the AppDiscovery.log. Please provide a link or past it in the message. Have you try the MSI product code like in my example?
Bigair-Mifi Well.. i feel dumb. But I'll ask this question, does SCCM only check the detected if installed rule if the Application Deployment is set to "Required"? I realized in looking at the AppDiscovery log, as my screenshot shows, that it could not find Chrome within it. So my thought then was, maybe it's not checking for it because it is not required. I changed the deployment to required and ran the steps again and it is now discovered as installed.
- Did you use a User Collection for the deployment?
I am also facing those issues right now after changing to User Based Assignments;
Somehow it seems to be "as designed", that detection is not really working without pressing the Install-button within User Collections.
Bigair-Mifi I may have figured it out. I'll let you know shortly
Bigair-Mifi detecting the MSI code was how we had originally deployed but when that wasn't working I switched to file/version and then just file. So I ran Machine Policy and Evaluation waited about 10 minutes and then checked the AppDiscovery.log. The timestamp from the AppDiscovery.log was for about 3 minutes after I ran the task. Unfortunately this is what I get when searching Up or Down.
