Kaseya VSA Reviews

We primarily use the solution for remote support.

The remote support is the most valuable aspect of the solution.

The solution now supports Apple devices.

We were able to handle the implementation internally.

The technical support is quite good.

We actually upgraded the solution due to the fact that we needed the support for Apple devices. We haven't had a chance to test that part of the product just yet, however, that was our biggest criticism of the product prior to this most recent update.

We have had Kaseya for a while. That said, the VSA upgrade was just recently done last month. That's a rather new part for us.

Our technicians, level one and level two, and our help desk all use this product.

My experience with technical support is limited. Just in our recent upgrade, we dealt with the support team. We didn't face any issues with them. We're satisfied with their level of service. I don't have anything negative to say.

We didn't do the setup; our network team does that. Therefore, I wouldn't be able to speak on how easy or difficult the initial setup was. I cannot speak to the deployment process either. I don't know how long it takes.

Our network team handled the implementation in-house. We didn't use an integrator or consultant as far as I know.

We don't look at the product from an ROI perspective. We simply don't have a have remote support solution, or we didn't. SCCM may provide that to us. We needed a remote support solution, and therefore, Kaseya was what we chose at the time.

Right now, we're making an evaluation of whether to standardize with either this solution or the SCCM.

I'm a direct end-user of the solution. We're just customers.

We're using the latest version of the solution.

In general, I would rate the solution at an eight out of ten. Thus far, we are quite satisfied with the product's capabilities overall.

Certainly, our company is a Managed Service Provider (MSP) supporting multiple organizations in Australia. We use IT Glue for comprehensive documentation, including password storage and sharing. Additionally, we use RMM for remote support, job scheduling, and script execution on devices for effective patching.

I like the features of Kaseya VSA, including IT Glue, RMM, and DATTO backup tool. The backup tool is highly useful, offering a fast and efficient way to retrieve and restore data. The solution is also adaptable to various environments and is highly-customizable for client needs.

The stability of the solution is good but it can be improved.

I have been working with the solution for the past year.

The solution is stable. I rate it an eight out of ten.

The solution is scalable. We manage around eighty clients, each with a minimum of thirty to forty devices, for the solution.I rate the solution an eight out of ten.

My advice for those using it is to have a minimum understanding of what they need from the tool. Learning about the tool through training videos is essential. It's not just a remote support tool. It also includes IT and security aspects. Regularly going through updates and training videos is crucial for effective usage. Overall, I rate the solution a nine out of ten.

It would be impossible to do our job without the solution or a similar product. It helps us get to multiple endpoints in multiple sites in multiple counties.

There's a certain level of management above which we have to get permission to access the machines. Below that, we can just access them. The person using the machine does not have to allow us to access their machine. Otherwise, it would consume an awful lot of time to get permission. We cannot do that with senior management. The senior management gets a prompt on their screen, and they click on it to give us access. We can schedule the patching of the endpoints. It is brilliant.

Sometimes, the product misinterprets the functionality of a machine. Sometimes, the product would restart mission-critical machines after patching, which shouldn’t be done without the engineer’s permission.

I have been implementing the solution for five years. I am working with the latest version of the solution.

I rate the stability a five out of ten. We did not face any issues with the stability.

We have 200 to 300 endpoints. Our customers are medium-sized businesses.

It is a cloud-based solution that talks to an agent. I sign on to a portal, and the portal shows me all the endpoints, like the servers and workstations. The deployment takes weeks. However, we do not have to work on it continuously.

I rate the pricing an eight out of ten on a scale where one is cheap and ten is expensive.

If someone can afford the solution, I would recommend it to them. Overall, I rate the product a five out of ten.

I use VSA to create reporting, scheduling of agent procedures, remote control, and monitoring.

Kaseya is highly configurable. There's a new version, Kaseya X, coming out. There's a whole rewrite of the platform. The agent procedures are very configurable. Function-wise, you can run PowerShell scripts or deliver MSIs, and you can give a user access, such as admin rights, for ten minutes and then take it away. You can use a lot of different variables.

The patch management is also pretty good. The remote control is as good, though some of the other products are a little bit easier to get a remote control with.

I would like to see improved virtual infrastructure management. I would also like to see Azure plugins so that you can manage Azure from your Kaseya VSA and 365 management. And also automating things like password changes, email changes, and updating Azure accounts out of the box. There is something called PIA that does a lot of that and has a plugin with ConnectWise, so Kaseya should be adding those kinds of modules to manage. Another improvement is mobile device management. That's another hot topic. And also some type of SOC monitoring build.

I've used Kaseya for about 12 years. I used to work for Kaseya.

I rate Kaseya VSA's stability a seven out of ten.

VSA's scalability used to be pretty good. We've got quite a bit of performance issues at the moment, and I hope version ten is gonna fix that, but after the hack that happened about two years ago, our VSA has never performed the same. It's always been slower. The performance hasn't been the best in the last two years.

I've contacted support quite a few times since I joined my current company. Support for Kaseya has been a lot better than when I worked there. It was really good probably about a year ago, but recently, they're not as good. They've been a bit more standoffish with remote sessions.

I've used products like LabTech as well, now called ConnectWise Automate. I've got a lot of experience with that and also N-able. Kaseya VSA is definitely the most powerful out of the lot, but a lot of people don't know how to use it. VSA's functionality is an eight or nine out of ten, while ConnectWise Automate is about a five or six out of ten, and N-able is about a six or seven out of ten.

I've worked at Kaseya, so I understand the ins and outs of how the product works.

VSA is not difficult to install. One of VSA's good features is that it will build up the different modules or versions that you don't have, and it will apply all the fixes while building a VM. I've always found that feature to be good ever since I've used VSA. I've installed VSA at least 100 times.

The market's become more competitive. Kaseya's come down in pricing when I compare it to TeamViewer or other cheaper RMMs like LogMeIn. I don't know the pricing for N-able or ConnectWise Automate, but I think Kaseya's reasonable where it is at the moment. What you can charge customers these days for remote management and getting them managed is a balancing act. We still have a lot of ad-hoc clients. Kaseya's price point could come down some more to pick up more of TeamViewer's and LogMeIn's market.

Remote control used to see more functionality until Kaseya was hacked about two years ago. You could connect to the C: drive of a machine. It could open up an explorer window, which was quite handy.

I rate Kaseya's VSA a nine out of ten.

Being able to connect to client computers without them necessarily needing to be there and being able to put in the patches and manage different information systems is valuable.

Feature-wise, it is pretty robust. It is pretty easy to use. It is easy to set up schedules and connect to clients, and I'm pretty happy with it.

The way it is laid out can be improved. If it could be a little more intuitive, it might be a little bit easier. Sometimes, it is hard to find features because they're called something weird, or they're in an interesting location that you wouldn't have thought that they'd be in.

We have been using it for about a month or two since we opened our doors. Our techs will access it, and when we have customers, they'll get into the different computer systems and be able to get in there.

It has been really stable. I haven't had any issues with it.

There is really no setup. You just log in. There is also no maintenance.

I've been pretty impressed with it so far. It is a good system. It is fairly intuitive.  You just have to learn it. It has a pretty good learning curve, and you need to spend the time to really get to know the system well.

I would rate it a nine out of ten. It is pretty good.

We use Kaseya VSA for simulation for customers also using the service.

Kaseya VSA's best features are auditing and reporting.

Kaseya VSA could be improved with more features to support the latest operating systems. In the next release, Kaseya should include mobile device management.

I've been using Kaseya VSA for over a year.

Kaseya VSA is stable.

Kaseya VSA is scalable.

The initial setup was straightforward and took about a week.

We used Kaseya for the deployment.

Licensing is available on a yearly basis and is priced per node.

Before implementing Kaseya VSA, I'd recommend reviewing the white papers and data sheets that Kaseya has produced and requesting a demo so you can review and utilize what the solution has and can produce in your environment. I would give Kaseya VSA a rating of eight out of ten.

I used it in my previous company. I was on client support. We had about 300 clients, and each one of those clients had from 10 end-users to 300 end-users. We were using VSA in order to manage those end-user devices.

Patch management was very useful. Backdoor access to the clients was also very useful.

Its scripting language kind of sucked. They have their own version of PowerShell inside VSA. if you want to reach out and grab endpoint information, for instance, to know how many end devices have a program installed, you actually have to write a script for that. It wasn't like how it is in CrowdStrike where you can just do a search, and it just happened. In VSA, you have to write your own script to do it.

In terms of new features, an integrated MDM for mobile devices would be awesome.

I have been using this solution for two years. 

It is very stable.

VSA is unlimited in terms of scalability.

They are knowledgeable, but they are not so much responsive. They are definitely more responsive than IBM. The IBM cloud management support sucks.

VSA is not as complex as Intune, but it is still somewhat complex and not very user-friendly. CrowdStrike is friendlier in deployment than VSA.

It depends on what products you want. Kaseya loves packages, and if you are packaging, it is more affordable. If you're not packaging, it tends to be a little bit more expensive than others.

I would advise others to definitely do onsite or virtual demos, and make sure they are asking about everything. They should make sure to get a demo of the product doing what they are planning to use VSA for. This way they can see how much work is going to go into implementation.

I would rate Kaseya VSA an eight out of ten.

We are service providers. We use this solution to deploy our services to our customers.

The most valuable part of this solution is the security features that it offers.

I would like to see more features included that are related to security. We are a company that is selling solutions for security and our customers often ask for more security features.

If you compare with other products, Manage Engine has some features that we like but are not present in Kaseya.

Kaseya VSA is installed on the cloud.

The dollar exchange rate in Brazil is very high, so the price should be better for our country. 

More generally, the pricing could be better in the different regions.

I would rate this solution a seven out of ten.

We use Kaseya VSA for software and patch management.

I like the remote control, audit, inventory, patch management, software management, and monitoring features.

The agent-based monitoring solution can be improved. I think they need to be updated. The remote control feature could be better. It would also help if they had a mobile device management feature.

I've been working with Kaseya VSA for more than a year.

Sometimes patching is unreliable. I haven't encountered any other issues.

Technical support is good. If I have inquiries, issues, or a troubleshooting encounter, I can raise a ticket on their website and ask for support. 

On a scale from one to five, I will give technical support a four. 

I gave them a four because they don't always fix the issues that I encounter. For example, they suggest fixing the problem on the next version or the next enhancement.

The initial setup was difficult for me. It would help if you had the license and SQL driver for onboarding successfully.  

I think it costs more than ManageEngine.

I can still recommend this product. It'll help do technical tasks like remote control, patching, monitoring, audit, or inventory. You can also monitor devices in the production or the company's environment. But it's not a perfect solution.

On a scale from one to ten, I would give Kaseya VSA an eight.

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.

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.

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.

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

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.

It is quite scalable and easily manageable.

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.

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.

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.

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.

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

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.