Kaseya VSA Review

Efficient patching and good alert system, but the interface needs updating and technical support needs improvement

What is our primary use case?

We primarily use Kaseya for managing all of the inventory, accessing the nodes remotely, and patching them. This includes the operating system and third-party applications. We also use it for the monitoring of services, such as vendor services.

What is most valuable?

The most valuable feature is remote access to the machine.

The patching is very efficient and we can rely on the alerts that we receive.

What needs improvement?

The GUI is not user-friendly. You have to search and dig deep into the options to find things. The overall look of the solution is dull and boring.

Technical support needs to be improved because the process is too long.

The reporting is not well organized. The predefined reports are not up to the mark and you have to do a lot of customization. Along with that, the process of customization is not very user-friendly. You cannot just put things into the GUI and get what you are looking for.

For how long have I used the solution?

We have been using Kaseya VSA for between three and four years.

What do I think about the stability of the solution?

This solution is quite stable. As it is on a public cloud, you just need a good internet connection to access all of the features. You probably need an internet speed of about five megabits to test all of the features.

What do I think about the scalability of the solution?

It is quite scalable and easily manageable.

How are customer service and technical support?

The support is not one of the features that Kaseya would be proud of. Whenever anything happens and you need support, they have a long process where you have to create a ticket that begins at level one with an email response. It moves to level two and if things don't get resolved there then you have to go to the engineering team.

We do have a Kaseya account manager that we can contact directly, and they usually help us.

Which solution did I use previously and why did I switch?

I have used SolarWinds and it has a very friendly user interface that is self-explanatory. By comparison, Kaseya is a little bit glitchy. SolarWinds is quite costly and you have to pay a lot to get features that Kaseya is offering at a much lower price.

How was the initial setup?

The initial setup is easy and you don't have to worry about a lot of things. You will get a link and just have to log in using your credentials. It is multiply authenticated in a two-stage process and then you are in. You just have to add your nodes to see all of the features.

If you are a technical person and are new to Kaseya then you will find it a little bit difficult to configure because of the GUI. This is unlike SolarWinds. However, if you just give it some time then you will get used to it and things will become quite easy to do.

What about the implementation team?

We implemented this solution ourselves. We are a managed service provider and onboard products for our clients from time to time. We are asked to create approximately 1,000 machines on a monthly basis.

We did have some help from Kaseya during the initial configuration, but after that, we worked on our own.

What's my experience with pricing, setup cost, and licensing?

The pricing is quite good and we are satisfied with it. It compares favorably to products like NinjaRMM and SolarWinds.

What other advice do I have?

This is a good solution and we like the group of people at Kaseya. The product is quite affordable compared to other RMM solutions on the market and we only have a few complaints.

On-call support, for example, would make for a very big improvement. Whenever someone has an issue, we can just directly call the number and speak with a technical person who can help us at that very moment. They would be able to take over your system on that very call, for example. Ideally, the reporting will also be improved.

The suitability of this solution depends on the need. For example, if you want to monitor your Linux environment and Linux services then the configuration is more difficult. That said, if you are using the PRTG Network Monitor or NinjaRMM then you cannot monitor Linux services. Ultimately, it depends on the use case.

I would rate this solution a seven out of ten.

Which deployment model are you using for this solution?

Public Cloud
**Disclosure: I am a real user, and this review is based on my own experience and opinions.
More Kaseya VSA reviews from users
...who compared it with SCCM
Find out what your peers are saying about Kaseya, ConnectWise, N-able and others in Remote Monitoring and Management Software. Updated: July 2021.
523,975 professionals have used our research since 2012.
Add a Comment
ITCS user