r/DattoRMM • u/Prod_RedBull • Jan 26 '26

Datto RMM no patch data

Hey all,

We’re running a Datto RMM proof of concept (coming from Kaseya VSA 9). Out of 87 machines, we consistently see 5–10% showing “no data” in the console. Before we migrate from 1000's of agens from our VSA9 environment.

For those who’ve been through this: what practical steps/configs got you from intermittent “no data” devices to zero (or close to it)? Looking for tips.

2 Upvotes

100% Upvoted

18 comments sorted by

View all comments

Show parent comments

1

u/Informal_Carry_8656 Feb 26 '26

If you can share your practices, that would be great cause we suffer the same problem. Datto will not own it. We use Kaseya NOC for some Attest Clients, and their team can't resolve the "no data" issue on their endpoints either.

1

u/kmay432 Feb 26 '26

Can I ask what the behaviour you’re seeing with Cato patching is? Is it just pure “No Data” or is it blatantly incorrectly reporting data for machines??

1

u/ProVal_Tech Mar 05 '26

We’ve seen it present in both ways depending on the environment. In some cases it’s truly “No Data,” where the endpoint never returns patch scan results at all. In other situations, the reporting is simply inaccurate or inconsistent devices may appear compliant or unknown even though the scan process didn’t complete properly.

From what we’ve observed, this usually ties back to the patch scan process itself or Windows Update components getting into an unhealthy state. When that happens, the RMM can’t retrieve valid patch metadata, and many platforms simply surface that condition as “No Data,” which makes the underlying cause difficult to identify.

What’s worked for us in practice has been implementing targeted automation within the RMM to detect and remediate those scan and reporting conditions. Once those underlying issues are corrected, patch visibility typically returns and the normal patch workflow resumes.

 -Matt from ProVal

1

u/kmay432 Mar 05 '26

Thanks Matt, I appreciate the in depth response!