Hi,

We recently renamed applications within SCCM. However, the monitoring of deployments shows still (errors) on the old deployment name.

Is there a way to reset monitoring info for an application within SCCM?
Btw I find it very confusing, this monitoring, specifcally on terminal servers (to which 100 users are logged on). I get "an error occured while querying the app-v WMI provider ONLY for a few users: is this historical data -we had issues but they are solved-, is it recent ...?).

Pls advise.

The information is shown about the deployment of the application, not about the application (name) itself. That information will be refreshed everything the Application Deployment Evaluation Cycle runs on a client. Also, that node shows the deployment status and not the installation status of an application. That means that sometimes something can go wrong with the evaluation of the deployment that's not related to the installation of the application.

For example, after the installation of the application the deployment is re-evaluated and this time the client failed to detect the application due to a WMI error on the client. In this case the deployment status will show an error even though the application is successfully installed.

Ok, thanks. So if for some reason the sccm client has issues, the result(s) will be wrong.

Extra "issue" we have is that terminal server users don't work on the same servers all the time. So an app-v application published to a user can have as well a good as a bad result (server1: install ok, server2: install went wrong).

No, it's not that the results will be wrong, it's that it shows the status of the deployment and not of the installation. The status is accurate, just not what you expected.

About the extra "issue", yes that's normal behavior. If the application is deployed to users it will show a deployment status for every device that the user logs on to. As designed,

Thanks.

I'm not sure if I fully get it what you mean by "deployment can be fine but installation not or vice versa".
Errors in monitoring point to what the sccm client sees and if the sccm client has issues, those results could be influenced by that. Is it that what you mean?

In packages, we have built in a logging-file which is written to a central location. Via Powershell we can read all files and look for "succesfull". This way we're directly and 100 procent sure everything went fine or did not.
I guess there is no way to do this for App-V pac

What I mean is that the deployment node shows the status of the deployment and the deployment status is not the same as the installation status. The deployment does more then just installing the installing the application. It also checks things like detections and dependencies. So if the deployment shows a failure it doesn't mean that the installation failed. It just means that something in the deployment failed.

The App-V packages in ConfigMgr are required in a specific form and that doesn't allow custom scripting.