Understanding low compliance numbers for an application deployment

Question

We created a deployment of a driver package to a group of known machines that need the update. After 3 weeks, the required deployment is sitting at only 40.7% compliance. Many of the machines may be on intermittently, so we are not surprised the number is
not 100%, but it does seem rather low. However, the real issue is the summarization of the deployment.
The deployment information in the Monitoring workspace seems to be incomplete. The pie chart shows a big red swatch of over 50% in error, but when looking at the error tab, only 9 machines have information. As a matter of fact, in the breakdown only 131
of the 275 machines in the collection are accounted for. When looking at the collection, 14 machines show as inactive, so that does not account for the large gap.
EDIT: I ran the report Application deployment type compliance, and it says success is 228 machines, in stark contrast to what I see in deployment monitoring.
How can I find out what is really going on with this deployment?

Answer 1

you should look at the logs on the client for unknown machines what are they doing like reeving policies or what went wrong.without logs,would be difficult to predict what went wrong.
Eswar Koneti | Configmgr blog:
www.eskonr.com | Linkedin: Eswar Koneti
| Twitter: Eskonr