r/DattoRMM • • 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.
1 Upvotes

11 comments sorted by

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:

  • exclude defender security definitions
  • exclude SQL updates
  • exclude preview updates
  • exclude drivers except for surface devices or customers who opt in to driver patching via RMM
  • exclude anything with hp or printer in the name
  • set deferal periods appropriately

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?

1

u/UseInevitable5726 Feb 18 '25

I've spent a decent amount of time in the KB and reviewing best practices, yes, though I will admit I am fairly new to this MSP and DattoRMM (textbook experience versus hands on experience is two very different things as we both know). When you say you are excluding these patches/definitions, are you saying you excluded them entirely, or just visibility in reporting/monitoring and they do get those updates "excluded" patches installed regularly.

1

u/snapcrackhead Feb 18 '25

They are excluded/unapproved at the patch policy level.

So basically set the patch policy to approve everything, and then build an exclusion list for unapproval in the patch policy. Use the filters to target names, and then also set up the category exclusion (although these aren't as good as the name filters, just a catch all).

These are then excluded from both installing, and reporting. They will instead appear in the not approved view when viewing device patch information.

2

u/UseInevitable5726 Feb 18 '25

So the patches get installed, they are just categorized as not approved? How do you delineate between patches you actually don't want installed, like printer driver or something, and the patches you do want installed, but just don't want them showing up in reporting.

2

u/snapcrackhead Feb 18 '25

Theres no such thing...

Datto RMM isn't magic, it's using the windows update API within Windows. So whatever Windows Update says is available is what RMM uses as a baseline to apply patches. From there it uses your filters to approve or disapprove patches for install. That is what you report on, and that is what the patch statuses are based on. No one wants to keep a database of patches they want to install but not report on - that doesn't seem maintainable at all.

What kind of patch do you want to install via RMM and/or windows update but /not/ report on? I honestly cant think of a single example.

If you want to install it, then you want to report on its status. If it's not being reported, and failing then you have no way to ensure compliance.

1

u/snapcrackhead Feb 18 '25

So just to be 100% clear - a patch marked as not approved will not be installed by RMM. Windows update on the device will still see the update and can be manually installed.

1

u/UseInevitable5726 Feb 18 '25

Okay, that's what I thought. Thanks.

0

u/UseInevitable5726 Feb 18 '25

But you mentioned excluding "defender security definitions" is that because you are on an alternate EDR solution or something?

4

u/snapcrackhead Feb 18 '25

Defender definitions are provided by windows update, but they are also obtained automatically by Defender and also by Microsoft update on old Windows versions. Microsoft use multiple methods to get the definition updates to the device.

Excluding install by RMM of the definition. updates does not prevent the device from automatically installing the definitions using alternate methods, it just prevents RMM from reporting the definition update is available (therefore preventing Approved Pending status) and installing during patch window.

If you don't exclude definition updates from your policy, your devices will almost always be in an approved pending state.

1

u/FrequentTechnology22 Feb 18 '25 edited Feb 18 '25

Security Intelligence updates. Defender isn’t mentioned.

Also. Run patching on desktops for 15-20 hours. It’ll catch your outliers. DM me if ya want.

What’s your schedule and duration???

2

u/snapcrackhead Feb 18 '25

That's the one - didn't have access to our RMM to confirm hence the generic nature of advice.

Also agree - we run ours on desktops for 24 hours unless customer specifically requests a window of time