Kaseya VSA Reviews

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.

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. 

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.

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.

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.

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.

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.

We use this solution for remote management.

The most valuable feature is remote management. It is quite robust.

The training that we received was quite good.

I am having an issue with patch deployment. With a lot of people working remotely right now, it is difficult to deploy patches because most of my clients are not on the office network. I have been looking for a way to deploy patches via the internet to selected equipment from Kaseya VSA, but it seems impossible. This is something that I would like to have support for in a future release.

Kaseya seems to download Windows patches, although I have not found a way to select those patches that I want to roll out, as it is done in the System Center. In SCCM, you can select the specific patches that you want to roll out. The only option I have seen is to approve or deny all of the patches that are available.

The workflow is not quite straightforward.

I have been working with Kaseya VSA for between seven and eight months.

I would say that because it does the job, it is stable. I don't use it every day, but so far, I haven't had any problems.

We have about 200 users that are a combination of administrators, developers, and end-users. They do not work on it directly, but we capture the information from the endpoints on the developer's system.

We had two training sessions with the support staff and they were good. The sessions were recorded and I quite enjoyed them. Personally, I don't like to contact technical support and would rather research the problem myself. If I hit an obstacle then I will contact support.

Overall, the support is good and I am happy with it.

I have experience with Microsoft System Center and there are some things that are easier to do with it.

I was not present for the initial setup, as it was in place before I joined the organization.

I have not tried automating any of the processes, although I have watched some videos and it seems to be straightforward.

My advice for anybody who is considering Kaseya VSA is to run a proof of concept first so that they have a fair idea of what they're going into.

Overall, I think that it is a good product and I may just have to better find my way around it.

I would rate this solution a seven out of ten.