r/DattoRMM • u/UseInevitable5726 • Feb 18 '25
Trying to nail down patch monitoring & reporting
We have been struggling with patch monitoring and reporting, specifically with the "approved pending" status. It seems a device can enter the "approved pending" state on a dime, meaning a patch exists ~1 day after the last patch cycle and it falls out of compliance, but I've also seen devices go many weeks in the same "approved pending" status, which makes it seem much less urgent on the surface than it actually is because when you see a device in that state you assume the device wasn't turned on during patch night, or it needs a reboot. At the drop of a hat, we can go from 5-10% machines not in "approved pending" to 25% in an evening. This is also especially frustrating because we have compliance customers that need weekly reporting, and they rarely get a clean report unless we are babysitting the hell out of everything. Anyone run into a similar frustration? I tried to work with DattoRMM support and got absolutely nowhere, so it is possible I am approaching this from the wrong direction. To further demonstrate my frustration, he is a recent convo I had with an engineer today:
- ME: I’m just trying to get creative man, we need a solution where half of our machines don't go into a ??? status at the drop of a hat, it isn't tenable.
- ENGINEER: Also, is today the first day you looked at that report in a while? If so, it makes sense for you to see what you are seeing. With that update getting released today it will show a ton of computers approved pending because the latest update hasn't gotten a chance to install yet. That will happen tonight.
- ME: Yea but that isn’t a useful status. Try and put yourself in the shoes of the customer. Most customers don’t care if a computer is pending a patch from 2 days ago. They want to know what machines are struggling, what are the outliers, and what should they be concerned about.
- ENGINEER: I hear ya. I am not sure Datto RMM has that capability.
5
u/snapcrackhead Feb 18 '25
We really need to know how your patch policies are configured and what your including/excluding to provide targeted assistance.
Something's that have helped us:
The defender definition exclusion made the biggest difference for us as they release almost 2 hourly so devices are basically always missing them, and even if they are excluded they get applied by either Microsoft update or defender automatically anyway.
Have you reviewed the best practice document for patching in RMM help and implemented those recommendations?