Client Agent in the Console : Fake Status (Application / Baseline / Software Updates)

Question

question

Vid3al-7669 asked Mar 14, '22 saldana-msft edited 3 days ago

Client Agent in the Console : Fake Status (Application / Baseline / Software Updates)

We are using MECM version 2107

1. When deploying an application to a device collection, looking at the deployment status the device remains in the “Unknown” status (Client check passed/Active).

-----Looking at the device status, everything seems to be ok, client check result is passed – policy request and hardware / software scan are recent.

-----Forcing an evaluation of application deployments, both from the console or from the client itself, and looking at the AppDiscovery log, the log is not moving / updating or it is updating listing only a small part of the applications that actually the device has in Software Center.

-----The only way to fix this situation is to push an agent reinstallation from the console.

2. Another scenario is with a client that has a Configuration Baseline deployed to it but, after evaluation, it is shown as in Error in the deployment status.

-----The specific error is “rule is in conflict with other rules”.
In this case, the logs are moving and checking them we can see that the rule contained in the baseline (only one deployed) is in conflict with … itself (?) .

-----Also in this case, looking at the device status, everything seems to be ok, client check result is passed – policy request and hardware / software scan are recent and also in this case the only way to fix this situation is to push an agent reinstallation from the console.

-----In fact, after the agent reinstallation, at next baseline evaluation, client will result Compliant without doing / touching anything else.

3. Another situation we faced is with a client having updates deployed to it that are also shown as needed in the reports. In Software Center nothing is shown and in ccmcache nothing is received.

-----From the Support Center Remote Client Tool we can see that this client should have deployment targeted.

-----Also in this third case, looking at the device status, everything seems to be ok, client check result is passed – policy request and hardware / software scan are recent and also in this case the only way to fix this situation is to push an agent reinstallation from the console.

these three anomalies to date, are not always present simultaneously on the same computer. a computer could have even one of these anomalies.

Why are these situations happening even if the devices seems to be healthy from the console?

Is there a way to identify all devices that are in this status? Is the agent reinstallation the only way to fix this?

Is there someone else who is facing these kind of issues?

Thank you for your support.

Regards

mem-cm-updates mem-cm-application

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Answer 1 · 2022-03-15T07:40:07.99Z

Amandayou-MSFT answered Mar 15, '22 Vid3al-7669 commented Apr 15, '22

Hi,

Thanks for your posting in the Q&A.

The online status of client on the sccm console may not be correct, actually, the status is from the SQL, and SQL information is from the MP, so we should check the MP is normal before we uninstall the client.

About checking, we could refer to CcmMessaging.log, it records activities related to communication between the client and management points.

If the answer is the right solution, 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.

· 3

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Amandayou-MSFT · Mar 21 at 07:52 AM

Hi,

May we know the current status of the question? If there is any other assistance we can provide, please feel free to let us know, we will do our best to help you.

Thanks and regards,
Amanda

0 ·

Amandayou-MSFT Amandayou-MSFT · Mar 30 at 06:46 AM

Hi,

Just checking in to see if there is any update. May we know the current status of the question? If there is any other assistance we can provide, please feel free to let us know, we will do our best to help you.

Thanks and regards,
Amanda

0 ·

Vid3al-7669 Amandayou-MSFT · Apr 15 at 12:49 PM

Thank you for your answers.

Specifically, for anomaly number 1, also go and see this thread. the problem is bigger.

https://docs.microsoft.com/en-us/answers/questions/651032/anomaly-monitoring-application-status-error-not-re.html

For each point mentioned, I expect that if the "Client Check Result" returns the result as passed, there is no agent problem on the client computer. Why instead there is a real problem and in the console there is no information that makes it understood?
Also go and see this other thread :

https://docs.microsoft.com/en-us/answers/questions/768675/34last-status34-in-the-console-grid.html

We cannot accept that the status in the console may be incorrect. I expect that a console to centralize services, if it reports the status of an agent as good, is really good and not discover after months or years that is actually not true.
In 8000 client computers, we assume there are at least 800 client computers with these abnormal states, so I don't think there can be a problem in the Management Point.

In any case, I will also monitor the "CcmMessaging.log" of one of these Client Computers.

I will also take a look at the LOGs of the Management Point.

The anomalies are still there even after MECM update to the latest version.

Thank you for your support, ideas or anything else that may be useful.

0 ·

question