Kaseya VSA Reviews

We use it for remote control, patch management, server monitoring, inventory, warranty, reporting, and automation. That's pretty much the gist of it, and there is a lot to that. Each one of these is very all-encompassing and very deeply rooted in the MSP world, and this is just the 30,000-foot view.

I come from a couple of MSPs, and it is the most heavily used piece. It allows us to support end-users and address alerts for problems within the environment. It is basically our eyes and ears into the environment.

The most valuable piece of the puzzle for me is what they call Live Connect. It is the piece that allows you to support an end-user without having to take the keyboard and mouse.

I've been a user of this tool for about 16 years, and I've seen it improve. One of the things that they need to improve upon is that when they roll out updates and patches to the system, they usually come with some bugs. Their QA needs to be a little bit better in terms of rolling out updates. 

In terms of features, I really would love to see their patch management improve. They do have a newer patch management module that's in beta that I'm actually testing, and that needs to be their primary focus for the near future. That would be my biggest takeaway.

There should be more Mac support. Whenever a new Mac operating system comes out, the support is very limited. It takes them a while to get things up to date. We're seeing more and more people move to Mac from the Windows environment for various reasons, but their support for Mac is very limited. A lot of it might have to do with Mac itself, but there are ways to improve upon that. That would be my biggest thing for improvement.

Their security should also be improved. Kaseya had a very big vulnerability exploited out in the wild in July last year.

I've been using it for about 16 years.

I didn't have any issues specifically with the product itself. Based on what I've seen over the years, the issues are usually related to the infrastructure and the speed of the hardware. So, it wasn't the application itself; it was outside of the application.

Its performance over the years has got to an acceptable level. I don't have any complaints about its performance in 2021.

It is absolutely scalable. It will max out around 15,000 endpoints. The sweet spot is 13,000 endpoints. From my experience, you start seeing performance lags with 15,000 endpoints. Ideally, we'd like to see a Kaseya server handle about 50,000 endpoints. I don't know when that's coming or if it's coming, but 13,000 to 15,000 right now is the sweet spot.

We have several hundred users who use this solution.

I use their tech support often. If you open up a Severity 1 dire emergency ticket, they're very responsive. If you just open up a standard ticket, it usually will get fielded by somebody who will make the phone call and escalate it, and that bothers me. I wish that their tier ones were able to handle a little bit more of the basic problems, but they escalate it. It is almost like they're buying time. So, their support could get a little bit better, but if you're opening up a Severity 1 ticket, they're very responsive.

I have not used any other solution.

It is in the middle of the road or moderate. Some people who are not familiar with it might find it a little bit more complex.

If you're installing it on-prem, it is going to take at least a couple of days to put together the infrastructure and get the webserver and the SQL server going. Installing it on top of those would probably take another couple of hours. You can have something up and running with various people involved within a day. You just need a couple of people from different teams.

I take care of its maintenance. They usually put out a patch once a month. So, usually once a month, there is a downtime. A couple of years ago, they used to take five to seven hours. They're now down to about 30 minutes of actual downtime. So, the outage is not too terrible these days.

When we were without it for a short time in July when everything shut down, it was difficult to support our customers. We could do it, but something that used to take less than a minute was taking 5 to 10 minutes. It is probably the most helpful tool in any toolbox for the MSP world.

With the on-prem, you buy the agent license. That's a one-time fee, and it varies depending on how many you have. You also pay annual maintenance on the number that you have. So, there are two fees involved: a one-time fee and a recurring fee.

I don't know its price. I've priced out some other ones that were more expensive, but we may have been grandfathered in. Both companies that I was at were already users of the system, and we may have had different pricing.

I would advise others to leverage their professional services. We've used them while doing some migrations from one piece of hardware to another. They're very good. They're very thorough. They do take the additional time to sit down with you and lay the plan out. 

It was early 2020 when we were migrating from an old piece of hardware to a new one, and we had to move the database and everything over. We engaged their professional services. They were very helpful, and it went very smoothly. I was really happy with the product plan.

I would rate it a seven out of 10.

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.

The most valuable features of the solution are its ability to offer control remotely to its users and provide patching capabilities to users.

The technical support of the solution is an area with shortcomings that needs improvement. The solution's technical support should respond more efficiently and quicker. If we ever encounter issues in our company, the technical support takes too long to provide the proper resolution.

I have been using Kaseya VSA since around 2018 or 2019. I use the solution's latest version. My company is a reseller of the solution.

Stability-wise, I rate the solution a seven out of ten.

After some upgrades of the solution, if our organization encounters issues or concerns with the device or the solution, Kaseya's technical support team cannot handle our issues. Kaseya's technical support, whatever issues we face, will be fixed after the upgrade in the solution, so they do not provide an immediate resolution to the issues we face.

It is a very scalable solution. Scalability-wise, I rate the solution an eight out of ten.

In my organization, more than ten people use Kaseya VSA.

I rate the technical support a five out of ten.

I am not entirely happy with the technical support team of Kaseya.

Neutral

On a scale of one to ten, where one is difficult and ten is easy, I rate the initial setup an eight since it was fairly easy.

The solution is deployed on the cloud and on-premises. You need to provide a dedicated server to Kaseya VSA for the on-premises version. I have no visibility over whether the solution was configured or installed using which cloud provider.

The time for the deployment phase of the solution depends on how many agents one wants to install. If there are too many agents to be installed, it takes over a month, but if only 100 agents or lower than that have to be installed, then it will not exceed a month.

The solution's deployment phase involves installing agents for which around five to ten staff members from my organization would be required.

Though I don't have complete visibility over the solution's pricing, the solution is not cheap, from what I remember. The solution is on the pricey end.

Those planning to buy the solution shouldn't expect quick support. It is the best solution for patch management and its ability to provide control remotely to its users. Kaseya does provide an update on the solution.

Kaseya VSA is not the perfect solution, and I know that there are no perfect solutions.

I rate the overall solution an eight out of ten.

The solution can be deployed on-cloud, on-premise, and hybrid.

The most valuable features of Kaseya VSA are remote control, live connect, and automation.

The audit and KNM tools could improve.

In the next release, it would be useful to have an iOS and Android application to provide more visibility.

I have been using Kaseya VSA for approximately 12 years

I rate the stability of Kaseya VSA a nine out of ten.

We have a lot of customers that want more agents communicating a single VSA server. For example, 50,000 assets on a single VSA. 

We have 15,000 people using this solution.

I rate the scalability of Kaseya VSA a nine out of ten.

The support from Kaseya VSA could improve. We have multiple customers that have had delays in receiving a response from the agents for small issues. We have to find solutions ourselves after creating the tickets.

I rate support from Kaseya VSA a five out of ten.

Neutral

We have to understand the customer's requirements then we can map the correct deployment for them, such as retrieving the VSA applications, automation, and database. The full process including the configuration and licensing is one week.

I rate the setup of Kaseya VSA a ten out of ten.

Customers purchase the solutions because it is priced well. There are additional services that have an additional cost.

I rate the price of Kaseya VSA an eight out of ten.

We have compared this tool to others and it is good.

I rate Kaseya VSA a ten out of ten.

We are an MSP-managed service provider, and we use VSA and to automate our IT management for our customers so we can work more efficiently and effectively. We are customers of Kaseya. 

The valuable feature is more of a combination of Kaseya VSA, and Kaseya BMS. They have several products that work well together. For example, when you have an incident on a device, you can create a ticket on the device, enabling you to build up a bit of history regarding incidents.

The user interface is somewhat outdated. Kaseya BLS, for example, has a much more intuitive interface.

We are currently in the process of implementing this solution and have been using it for three months. 

The solution is stable. 

The solution is scalable, we have 15 users. 

The technical support is quite good. 

Positive

The initial setup is not particularly difficult but requires some assistance which we received from the company. 

Licensing costs are mid-range and I believe we get value for money. 

I compared Kaseya with other products on the market and found the functionality it provides suited our requirements. 

Make sure that the software features fit your needs. There are numerous options on the market and they all have very slick presentations but you really need to ensure that the software is right for you. 

I rate this solution eight out of 10. 

There is an on-premise and cloud version of Kaseya VSA.

I use Kaseya VSA to manage peoples' systems and perform patches from time to time.

The way Kaseya VSA treats application vulnerabilities is good. They have released some new features that have been a benefit, such as updates from the Microsoft repository directory.

The reporting feature in Kaseya VSA could improve by being more user-friendly. The reporting overview is too wordy or the representation can be better.

I have been using Kaseya VSA for approximately three years.

The stability of Kaseya VSA is very good. However, approximately three years ago there was an attack on the system. They have done things since then and the solution is stable.

Kaseya VSA is used by everyone in the organization. The solution is deployed on all user's systems.

The support from Kaseya VSA does respond but sometimes it takes a while. The delay could be because they have a high workload, but the response could improve.

I rate the support from Kaseya VSA a four out of ten.

Positive

The solution is robust and the price is good for the features that are provided.

I rate the price of Kaseya VSA a four out of five.

My advice to others wanting to implement Kaseya VSA is they should go to Kaseya University or have some form of administrative knowledge sessions. This way they will be able to use the tool properly and receive the full benefit of it. You need some training on how to use it because it could be overwhelming sometimes. I would recommend others to use the solution.

I rate Kaseya VSA an eight out of ten.

This solution is our RMM tool and we love the deployment features. We just develop a package for each dual client base that we have or for each client network, or actually in some cases we have two packages depending on if it's going to be a remote user or an in-house user. My partner sets up the packages and we install the packages on the computers as they come in and they do pretty much everything for us and get all the software installed. The only thing we have to do is put in a couple of passwords for the individual users and we're off and running.

We used to use a different product and we've found that this solution is far more efficient for using the BMS and VSA and also with our documentation. This solution just made life a lot easier.

The solution is hard to use at first until you understand how it works. Once you gain an understanding of how it works, it's great, but it's not a five minute tutorial and you're off and running. You do need to spend some time to learn how to use it.

I would say the solution is stable. We haven't had any trouble since we deployed it.

Scalability is easy with this solution, and you can always go up. However, it is hard to go down because, just like everybody else, once you get to where you have so many users, you can't remove them due to the contracts.

We're actually in the process of growing, and we are hoping to bring on another 45 to 100 endpoints in the next three to four months. We're also in talks with another company to bring on another 300 endpoints in the next nine months, and we're expecting to grow by maybe one technician.

For us, the tech support has been mostly educational. We've had a couple of issues where things weren't working as we thought they should be and they've been very responsive. Plus the tech support has been great when we ask for training. My partner prefers to do everything by email instead of phone and we usually get responses from the team within an hour or two and resolution within the day as to figuring out what the problem is.

Our ROI is probably about six months. We started seeing real improvement in our efficiency at that point because we were still finding new things we wanted to do with the solution. We're actually still finding more things we want to do with it because we just ask, and all of a sudden, "Yeah. You can do that." It's like, "Oh, okay." It's been very adaptable for us in that aspect, and the amount of power it provides has just been amazing. I also note there are a couple of things on the horizon that might make it even that much better.

I think VSA is like $4.00, but we got a deal on it, so it was under $2.00 per endpoint per month.

I would rate this solution as a nine out of ten.

Our top uses are remote support, asset and inventory management, and patch management.  

The patch management and the remote support are very good, especially the remote support. There is a module built into the solution which allows remote control without necessarily interrupting the user. We could manage things in the background without them seeing or interacting with anything, which is a very useful feature. 

The response to bugs is slow and software improvement comes slowly too. The lack of response to our feature requests made it feel like they were going into a black hole. Additionally, when we encountered bugs or issues with the VSA, they were slow to respond to those too.

The solution could also use better management and functionality for file transfers. Now when you want to do file transfers, you can simply copy a file and paste it over. Sometimes that works, and sometimes it doesn't. I like to have a file transfer window because I can see the data tree on both machines, mine and the remote. This is an industry standard and I would like them to bring this feature back. I understand they were trying to make things easier but sacrificing this functionality isn't the way to go about it.

We have been using this solution for the past 12 months.

The stability is good, there was one occasion where the site was down and we couldn't do anything, but overall I have no complaints about that.

The scalability of the solution is good, it allows for rapid deployment of under an hour, whether for a smaller or larger number of workstations. We package in antivirus along with the remote control aspect, which allows very fast onboarding of clients at a basic level.
The probe functionality allows us to leave the probe on the domain controller and anybody connecting to the network would have Kaseya deployed to their workstation, and we receive an alert of the new addition. This is excellent for management and deployment.

Regarding our internal use of the solution, we had about 35 people using it. 

Customer support has been quite responsive. By phone I recall getting in contact with support within a few minutes, and opening a chat session was even faster, so I would use that option more than anything else. 

Positive

We primarily used LogMeIn before switching to Kaseya. The problem with LogMeIn is that although they provided remote control support and to some extent asset management, there was no robust reporting to give us the data we needed. This made us feel like we were being overcharged for the product. That being said, Kaseya is not cheap either, but we are getting a lot more for our money. That was the reason why we left a competitor and came to Kaseya.

The initial setup was a mix. Some visually poor UI elements complicated the process, while remote control of assets was straightforward. 

The deployment was very quick thanks to the incredible probe functionality. We would install a probe on the domain controller and assets would be checking in within minutes. 

You're going to pay for this solution, but you're going to get so much more out of it in reporting, asset management, and the ability to manage your clients. I would recommend giving Kaseya serious consideration and I would recommend implementing it. 

I consider Pulseway a viable alternative, but it's a bit too expensive. They don't have a probe functionality either, even though it has been frequently requested on their website. 

I would rate this solution a nine out of ten.

We use the solution internally, deployed to our own workstations as well as with our customers. There would be times while working on something where I would encounter an issue, and a network engineer could remote to my system to help get a solution quicker. We also use the solution for our own inventory management.
I would recommend Kaseya to any MSP, because their product is a little ahead of the innovation curve compared to the competitors.  
The ability to quickly onboard clients is phenomenal. I feel that compared to its competitors, the solution is not as complicated. You log into the portal, create an organization depending on the client, create an installer, throw it on the domain controller and let the software work for you.

We are resellers. We use it internally, but not all of its features.

The most valuable features of this solution are automation, inventory, and patch management.

The majority of end users want complete software management. It focuses on a thorough evaluation of the initial projects in the software.

It should focus on the lifespan or timeline of the software and hardware. The majority of end users ask if there are any notifications or advice regarding when they purchased the hardware and software and when it will expire or need to be replaced, and there are none in Kaseya. As a result, even the software metering.

Better software awareness and metering are required.

Metering software depends more on what they use it for, and how much software is available within the company.

If I think of any additional features that are required, it will be for detecting or including mobile users of managing endpoints. There is currently no mobile license for cell phones, Androids, or even iOS. I believe we should include a VSA license to provide complete endpoint management.

We are resellers and have been dealing with Kaseya VSA for six or seven years.

Kaseya VSA is a stable solution, some of the end users have been using it for years.

The scalability is good; it is up to the end-user or we can add additional licenses if necessary. We can conduct policy checks as well.

I would give the technical support a four out of five. There is no such thing as a five. You coordinate things, and it is available as needed.

The initial setup is straightforward.

It is simple to implement, especially when the end-user knows what policy they want to implement.

The implementation was completed in-house. We used the Kaseya method of implementation.

In terms of maintenance, we don't need a lot; one person can monitor it.

In the Philippines, licensing fees are paid on a yearly basis.

I believe it is competitive, depending on the number of users purchased. It's scalable in terms of pricing.

Fees are paid per license, per user, and per year.

It is, in my opinion, competitive in the market. It is determined by the number of users and licenses needed. Depending on the license count of users, the price ranges from $10 to $80 USD.

I would rate Kaseya VSA an eight out of ten.

We would install Kaseya on customers' computers and provide tech support. We used it as a monitoring tool and remote access tool.

The main uses were for information gathering, management, software, and patching as well. My team would not be responsible for patching. That was another team that was at the engineering level. My team was responsible for going on the customer's computer and providing just regular tech support. That was done via Kaseya quite often.

The product has allowed the company to provide faster service. If you're, for example, using something like TeamViewer, which is a different type of software, versus Kaseya, if it's deployed on the computer, it will be very fast and easy to do the same things with Kaseya compared to TeamViewer. That means there is higher customer satisfaction. When we do our jobs faster and more efficiently, the customer is happier.

The ease of access and ease of use was great. When Kaseya is deployed on the customer's computer, we have access to the customer. We just need the computer's name or ID, or sometimes, if the user has the same name as their first name, we can find them that way. 

I know it's customizable. Even with the customization we had, which was not that great, I, myself found multiple ways of how we could find people, based on system version, their computer specs, location, et cetera. That made finding people very easy. 

The functionalities were helpful. I could check what type of computer the customer was using and if they had a warranty. It provided a lot of information out of the box and just pulled all the information from the computer itself. For tech support work that is very valuable. You don't have to go to the client and say "Can you find me a serial number somewhere on the computer" and have them messing around, looking for it. Instead, I just pull it from the system, as Kaseya finds it automatically.

There is automation that was used for a big product, however, you need to learn it. One of the people in the company actually finished the course. When I saw what he could do with it, it's way more than what I could do. You just need to learn it.

The deployment process could be better. There were some issues sometimes that were kind of random. For example, by sending a link to a customer, you would need to add the link manually, which is a bit strange, as it is customizable. You need to know which part of the link you need to edit and how you need to edit it. I don't know how much of this is Kaseya VSA itself and how much of it is our custom setup. Maybe Kaseya would say "No guys, you just did it wrong. That's not how you do it." However, based on what I saw, editing the link was a bit odd and I would prefer something more on the lines of just sending their general link and maybe an easier deployment. 

There was some lag. For example, even if it's installed, it's not showing up and you need to wait for it to show up. 

Sometimes there were connection issues. It was not exactly clear why it didn't connect even if the customer had internet that was working fine. I'd do a speed test, and it would show normal speeds. We would have our fast office internet and everything was working fine, yet it wasn't connecting right and we don't know why. We used it on literally thousands of machines and servers as well and it just would randomly happen. 

It doesn't doesn't scale on smaller monitors properly. For example, if we moved from 17-inch screen laptops to 12-inch screens, it would not scale properly. There is a part that's called Live Connect, however, it wasn't actually a live connection. You connect to the customer's computer in the background and you have this user interface and the smaller monitors would look really bad. With some of the screens, you couldn't click a button or anything like that. While it was working fine on a normal big monitor, on smaller ones, it did not adjust which made things difficult. I don't know why, how they missed that. Maybe we used some kind of older version or something.

Kaseya is not really friendly with Mac OS. The deployment is even harder than deploying on Windows. You need to have a custom download. If a company runs a customer service desk and has a bunch of tier-one agents, they're not going to be able to do that. Right. They're going to be able to edit a link if you provide instructions, and that's about it.

I worked with the solution at my previous organization for about a year. I used it up until a month ago.

We sometimes had connectivity issues and I never spoke with a Kaseya representative that could explain that. We worked from Europe; the servers were probably in the US and the customers were in the US. Sometimes it would work quickly and then snappy and everything would be great. Other times it would be kind of slowish. I would say it would be way faster or way slower than a TeamViewer connection. 

The solution is scalable. We had thousands of users.

We didn't have issues with scaling. When it was set up, it was designed so that, if a business joins, we join them on the server and they have their own ID there. We could install it on the computers. It connects that computer to the whole system. While it's hard for me to answer about scalability in a detailed way (I didn't work on that infrastructure part), my understanding was that it was decent at worst. It was pretty okay.

We used it daily. It was a core product for the servers. However, we were hacked, and for a few weeks, it was quite bad. 

We had the in-house staff. I can't really say anything about technical support as the person we dealt with was just an expert that was hired by the company, working for the company, doing some other stuff as well. 

We didn't really need to contact directly with Kaseya. When the hack happened, they were communicating well with us. Based on the opinions of that other person, that had finished the course with them, he was very happy about that and thought support was super professional. 

In terms of deployment, technically one person is enough. For Macs, you just need to know how to do it and it's a very specific procedure. As far as I remember for each company, there is a separate download. With Windows, it's the same download, however, it needs to put the users in a specific catalog. You need to edit the link, essentially the same way you would for a website and you need to put specific lines in the link. For Macs, you have a different file that you need to know how to download, where to download it from and how to check if something is wrong. While one person is always enough in terms of handling the deployment, that person needs to know how to do it.

Deployment times vary from a few minutes to half an hour. Maybe a few hours. It depends. Most of the time I would say it's only a couple of minutes. However, when you really need to have it configured and you are first building the infrastructure, the whole thing, if you order a product and you want to start using it, I have no idea how long that process takes. That's definitely going to take longer. 

We had five Kaseya Servers for thousands of computers, thousands of servers, et cetera. That would take a while. Right. If it's just a business of maybe 40 users, I would assume it is a way quicker process. 

Kaseya itself would update regularly and then it usually would show up with a message such as "You have a patch to do. You need to install this patch." That's about it, in terms of maintenance. I'm not an engineer. I was more of a user. From a team lead side, I was managing people that used it daily to help customers. While there was definitely some normal updating in terms of handling the security patches, that was the only real maintenance task. 

I can't speak to pricing. I was not involved at the decision-making level. 

My company was a customer of Kaseya.

I'd rate the solution at an eight out of ten. 

Kaseya is more beneficial if you really have all of these machines and you need to manage your servers, you need to set up automatic patching for scripts to run or something like that. 

Whether it would work for others depends on the business. For some, I would assume it's not going to be worth the price. If you just need a remote connection, you can just go to TeamViewer or something similar. If you need automatic patching, you want to have this access, instant access, background access to the user's computers, so that you can check what's happening, basically without the user knowing, it's very, very good for that. At the end of the day, it depends on the scale of the business and business needs.