MSP Remote Monitoring & Management

Feedback for MSP Remote Monitoring & Management

MSP Remote Monitoring & Management

Submitted by (@bowesit)

Update backup products

I've only been a subscriber for about 4 months. One thing that I liked about Solarwinds MSP was that all of the backup products I use are supported. However, BackupAssist is only supported to version 8 (two major revisions behind), the MSP version of CloudBerry is not supported. A new client ran Symantec BackupExec and while it is listed as supported, it too was too recent a version (apologies, I believe it was 12.x but ...more »

MSP Remote Monitoring & Management

Submitted by (@j.sans)

Evolution of asset tracking



The idea is to add on the asset tracking dashboard the description column found on the main dashboard. Because each post can have the same name but a different description in the same company. If you synchronize the name in the dashboard with the name of the workstation. We can lose a lot of information.

MSP Remote Monitoring & Management

Submitted by (@jeremywhiteman)

debug logging enabled by default for integrated RMM backup clien

It is clear as day every time that without debug logging enabled, pulling logs for integrated RMM backup clients is next to useless because they provide no info. SInce debug logging needs to be enabled to gain any knowledge of anything, why can't it be enabled by default?

MSP Remote Monitoring & Management

Submitted by (@alessandro.martins)

Incorrect term in executive summary report

Inside the executive summary report we have a field that shows "Alerts Resolved" according to the manual it shows the total of alerts raised, closed or cleaned. The term resolved is wrong here because it counts open alerts. This term should be change to something else like "total alerts" for instance. It's causing miscomprehension with some clients and end-clients.

MSP Remote Monitoring & Management

Submitted by (@iris.santos)

Take Control API to include the technician name

When the Take Control API is at place, the user registered on the RMM side is the agent key, since there's no login at place. This makes it difficult to keep track of the techs/engineers responsible for a given remote session. The underlining idea here is that Take Control's API is largely used by some RMM users, so having the possibility to add the tech/engineer name behind the remote session would be helpful.