NinjaOne: Patch management update FAILED to complete. ERROR: Patch management update FAILED to complete. Error:[-1001 NinjaWPM execution timeout.]

Is there a common cause/condition for this or do I need to contact support?

Posted May 22, 2023, 12:21 PM UTC

114
cwilliamsNinjaOneNinjaOne•

What is the patch duration set to in your schedule? I've seen this error if a patch duration is set too short and the install can't complete in time.

If that's not the issue, then I recommend reaching out to Support. They'll figure it out.

3
Technical-Message615OP•

1 hour. Machines are on fast storage and fast LAN+WAN. I've contacted support.

1
CptUnderpants-•

Contact support, they're very responsive in my experience. I've not seen this error before.

2
larvlarv1•

Maybe a device that came online and Ninja did not have time to finish the task before said device went offline?

1
Ognius•

This is why we didn’t end up going with Ninja when we were shopping around for RMMs. Patching was too unreliable and policies were too shallow.

-1
sfreemMSP•

So when are you migrating away from kaseya?

2
Ognius•

I don’t know dawg. I don’t make those decisions. I think we have a year and a half left on our contract

1
CptUnderpants-•

I agree with the shallow options, but patching has been reliable for us. Are you talking about OS patching, software patching, or both?

2
docNNST•

Get a better RMM

-4

Suggestion?

1
bbqwatermelon•

No experience but I have a list going of ones I would like to try however need to work elsewhere before I get to experience them:

  • Automox
  • Intune/Azure Update Management
  • Scalefusion
  • Heimdall
  • Level.io
3
docNNST•

It was a bad joke. All RMMs have problems. Patch management has always been a struggle.

I got out of the MSP game a few years ago, now an IT director at a software company with a laptop population of Macs and PCs. We use JAMF + Intune with some scripts we wrote that get the data we care about into azure logic app into a cosmos DB. We wrote queries that generate tickets for errant conditions.

This was more work but enabled us to be more resilient\secure.

When I worked at a MSP we were a manage\labtech\automate shop. I know your pain.

1
[deleted]•

[removed]

1
CptUnderpants-•

All RMMs have problems. Patch management has always been a struggle.

On the whole, Ninja has been very good on patching for me. Only issue I've had is at one point the software (but not OS) patching started using its own trusted list of root CAs which broke some of the patching due to our SSL inspection. IIRC it only affected Zoom and VSCode patching for us.

Ninja also has a good patching status dashboard.

1