r/Nable

Is anyone else having an issue when installing an agent where it hangs after clicking Start Monitoring Now?

I’m used to it finishing in like 30 seconds, but now it doesn’t seem to want to finish at all and I have to force quit it.

oh no..

6.. 6 rows with like 2 controls each. Please stop.. Please also add the dang icons back to the left-hand menu, and allow me to show/hide items I don't need. Actually, please just contract me as a part time UI designer. Heck I'll do it for free, would make my life easier. I think most everyone would thank you for it and I will experience less mind pain.

Aside from things like this, I love N-Central. Help me help you.

This might just be a UX quirk but I've noticed the following:

When you are adding a check to monitoring template, there is no ability to assign an automated task on failure of that check. You can add an automated task, though, and set it's run parameter to "on check failure" then specify the check.

If, however, you are editing an existing check for a machine, you can check the "Assign a task after editing check", which let's you choose an automated task. This bit doesn't explicitly say "on failure", but I have to presume that is the case. You can also edit an automated task and set it's run parameter to "on check failure", just like if you were editing a template.

So, there are apparently two different ways to do this thing if you are editing an existing workstation, but only one way to do it if you are editing/creating a monitoring template.

Is this conclusion correct? Is there any difference in doing it one way or the other? Obviously, it's rare to want to make a change like this to one particular machine (rare, but not never) - it's more common that you want to make a change like this to an entire client, or your entire estate of managed computers.

Is there a way to backup those?

My only scenario is a local file share from a client.

Hi all - we recently moved clients to N-able Cove Backup to consolidate tools, but we’re seeing consistent endpoint performance issues. Users on newer machines (i7, 32GB, 1Tb SSD) are reporting stuttering, input lag, and apps freezing during the day.

Logs show repeated VSS errors (0x800423f2, shadow copy timeouts, “provider timed out holding writes”), and backups frequently finish as CompletedWithErrors or Failed. We originally had mapped drives (Google Drive / ShareFile) in scope — removed those, which helped a bit, but we’re still seeing disk contention and VSS instability during backup windows. Most endpoints are backing up ~80GB+ with large file counts.

For those running Cove at scale, how are you configuring endpoints to minimize user impact? Are you limiting to specific folders (Documents/Desktop vs full profiles), what exclusions are you using, and are you applying throttling or strict off-hours scheduling?

Feels like Cove is a bit too aggressive on active endpoints, trying to dial this in without sacrificing backup reliability. Appreciate your help!

Anyone else? Since the latest update, if I connect to a computer remotely, any input to a powershell window is ignored. Works fine if I copy and paste the commands, but other keystrokes are ignored.

Command prompt seems unaffected..