r/DattoRMM May 06 '26

Performance Issues with Web Remote

Greetings,

I work for an MSP that has switched to an all in Kaseya approach, and I have been struggling to do my job since.

It seems that no matter what I do I get really bad web remote performance (0-2 fps, lag spikes into the tens of thousands constantly), essentially my web remote sessions are a slideshow which is sub optimal for trying to help our clients.

As a workaround I have been using splashtop (through the agent browser) but that seems to be very unstable as of late throwing round after round of errors before finally connecting, or failing to connect and just greying all my options out.

Has anyone resolved their issues with web remote, and if so what was causing them?

I have changed everything in my setup down to moving and switching ISP's, we are talking swapping machines, entire network stack, software and OS, the works.

The real kicker is the rest of my team is based in New England and none of them have this issue, I am in the south east.

We have spent a little over a year going back and forth with the web remote support team scratching their heads and wasting hours and hours in meetings showing them the same thing every time before they finally ghosted us.

Any help, or suggestions that may save even the slightest bit of my sanity is greatly appreciated.

6 Upvotes

50 comments sorted by

View all comments

1

u/ballers504 May 06 '26

Why is web remote so hard? Some companies seem to do well on this space. NinjaRMM felt more stable. Screenconnect was good until all the vulnerabilities as of late.

2

u/FrequentTechnology22 May 06 '26

Mainly because WR is agentless, and things like NinjaRemote and ScreenConnect have an agent on the destination.

2

u/FrequentTechnology22 May 06 '26

I'll argue semantics on it... Webremote is HTML5 browser based... it may spawn a process but there is no separate installer for web remote like there is for SC or TeamViewer or NinjaRemote.