Anomaly Monitoring Application Status Error not reported

Question

We are detecting, for many applications, the anomaly described in the following article:

https://techcommunity.microsoft.com/t5/configuration-manager-archive/troubleshooting-in-console-monitoring-for-deployments-in-system/ba-p/273015

We started noting this after Upgrade all Build 2107 of MECM. A month ago.

We also noticed, taking into consideration some Applications, that before the upgrade, the TAB "Error" correctly displayed all the devices in error.
The application, deploy and collection of deploy, have not been changed. They have not been touched for more than 4 months.

Devices have already updated the Agent to version 2107 (5.00.9058.1047).

Gli agenti dei device, non mostrano anomalie evidenti.
Client Check Result = Passed.
Client Check Detail ---> All Evaluation Rules = Evaluation Succeeded

Bearing in mind that, in the case of a deploy of an application of type available, a possible error will never be reported in monitoring until the user performs the installation from the software center, I expect that whatever the error returned above a device, this will be reported in monitoring by displaying the devices in error.

Regardless, the anomaly occurs in both modes of deployment, available and required.

If the anomaly depends on the corrupted agent, is it possible that the only solution is to reinstall all the Agents on the Devices?
If the agent is somehow corrupted, why is it not shown in the console? How do I track down all the devices that have this anomaly?
Is the problem the agent or something is not working in the console?

The Report "Application infrastructure errors", not only shows the devices with this anomaly, but also shows those that are visible in the TAB error.

Thank you for your support.

Answer 1

Hi, @Vid3al
Thank you for posting in Microsoft Q&A forum.

It looks like a product design issue, you may send a frown about this issue.
In the upper-right corner of the Configuration Manager console, select the feedback icon. Choose Send a frown.
https://learn.microsoft.com/en-us/mem/configmgr/core/understand/product-feedback#send-a-frown

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

---

Answer 2

The problem is still present, despite the upgrade to the latest version of MECM.
The problem also occurs with newly created applications.
We will ask Microsoft for support.
Thank you for your support.

Answer 3

We are trying the following W/A :

Rename "CcmStore.sdf" in "CcmStoreOLD.sdf"
File Path C:\Windows\CCM\

We are monitoring the outcomes and it seems to be resolved.
We should have a method that allows us to understand if the problem returns to the same systems remedied.
NOTE: The file size we have already found that it is not a valid indicator.

However, we do not know in detail what is the cause that generated the anomaly.
We started to notice the anomaly only after Upgrading the Infrastructure to version 2107, and today we are version 2111, but the anomaly persists.

An additional thing to watch out for is described in the following article:

https://learn.microsoft.com/en-us/troubleshoot/mem/configmgr/recommended-antivirus-exclusions#folder-exclusions-for-clients